How do I install the Oss Maintainer skill?

Run npx skillmds@latest add garphengate/oss-maintainer in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Oss Maintainer safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Oss Maintainer?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Oss Maintainer free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Oss Maintainer?

GarphenGate (@garphengate) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Oss Maintainer by garphengate — Agent Skill

Name: Oss Maintainer
Author: GarphenGate

File contents

Issue Templates

Free gateway skill from the OSS Maintainer bundle by GarphenGate.

Half of triage pain is self-inflicted by a blank issue box. These two templates make good reports the default and unusable ones visibly incomplete.

Procedure

Ask three calibration questions: what the project is, what one piece of information reporters most often omit (version, config, platform), and whether reporters are mostly developers or end users. Tune field wording to that audience.
Generate the bug template below, adapting the environment fields to the project's stack.
Generate the feature request template, which asks for the problem before the proposal, because proposals without problems are scope creep in disguise.
Deliver both as ready-to-commit files for the repository's issue-template directory, with a one-line description of where to put them for the user's forge (GitHub, GitLab, or other).

BUG REPORT TEMPLATE (fields)
- What happened: <one or two sentences>
- What you expected instead:
- Minimal reproduction: <smallest steps or snippet that shows it>
- Version: <project version> | Environment: <OS / runtime / relevant config>
- Started when: <first noticed / after upgrading from>

FEATURE REQUEST TEMPLATE (fields)
- The problem: <what you cannot do today, and the cost of that>
- Your current workaround:
- Proposed solution (optional):
- Would this change existing behavior: <yes/no/unsure>

Rules

Never add more than six fields to either template; long templates get skipped and the blank box returns by the side door.
Never make the reproduction field optional in the bug template; it is the one field that pays for triage.
The feature template must ask for the problem before the proposal, in that order, always.

Degradation

If the user cannot say what reporters typically omit, ship the general-purpose versions above unchanged and suggest revisiting after the next ten issues reveal the pattern.

Like this? This is the free gateway skill for OSS Maintainer by Moltline Studio. The paid listing: https://www.agensi.io/skills/oss-maintainer-persona

---name: oss-maintainerdescription: Bug and feature templates that produce reports maintainers can act on. Use when the user's issue queue is full of unusable reports or they are setting up a new repository.---# Issue Templates*Free gateway skill from the OSS Maintainer bundle by GarphenGate.*Half of triage pain is self-inflicted by a blank issue box. These two templates make good reports the default and unusable ones visibly incomplete.## Procedure1. **Ask three calibration questions:** what the project is, what one piece of information reporters most often omit (version, config, platform), and whether reporters are mostly developers or end users. Tune field wording to that audience.2. **Generate the bug template** below, adapting the environment fields to the project's stack.3. **Generate the feature request template,** which asks for the problem before the proposal, because proposals without problems are scope creep in disguise.4. **Deliver both as ready-to-commit files** for the repository's issue-template directory, with a one-line description of where to put them for the user's forge (GitHub, GitLab, or other).```BUG REPORT TEMPLATE (fields)- What happened: <one or two sentences>- What you expected instead:- Minimal reproduction: <smallest steps or snippet that shows it>- Version: <project version> | Environment: <OS / runtime / relevant config>- Started when: <first noticed / after upgrading from>FEATURE REQUEST TEMPLATE (fields)- The problem: <what you cannot do today, and the cost of that>- Your current workaround:- Proposed solution (optional):- Would this change existing behavior: <yes/no/unsure>```## Rules- Never add more than six fields to either template; long templates get skipped and the blank box returns by the side door.- Never make the reproduction field optional in the bug template; it is the one field that pays for triage.- The feature template must ask for the problem before the proposal, in that order, always.## DegradationIf the user cannot say what reporters typically omit, ship the general-purpose versions above unchanged and suggest revisiting after the next ten issues reveal the pattern.---*Like this? This is the free gateway skill for **OSS Maintainer** by Moltline Studio. The paid listing: https://www.agensi.io/skills/oss-maintainer-persona*

Frequently asked questions

Oss Maintainer