maintainer-triage
Get an open-source repo's issue backlog from 400-and-drowning to triaged-and-honest in one pass — a label taxonomy that encodes decisions, batch triage rules you can apply in seconds per issue, saved replies that stay kind at scale, and stale-bot policy set with a conscience. Use when a maintainer says 'my issues are out of control', 'triage my backlog', 'set up labels for my repo', or dreads opening GitHub. Produces the taxonomy, the triage pass rules, saved replies, and a sustainable weekly routine.
Profile →npx skills add mohitagw15856/pm-claude-skills --skill maintainer-triage --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Maintainer Triage Skill An untriaged backlog isn't a to-do list — it's 400 open loops charging interest on a volunteer's conscience. The fix isn't heroic issue-closing weekends (they don't repeat); it's a system where every issue gets a *decision* in under a minute — reproduce/needs-info/accepted/wontfix/ someday — encoded in labels, communicated by saved replies that stay human, and maintained by a 30-minute weekly routine. Honest triage closes issues politely that will never be done, because "open forever" is the cruelest answer of all. ## What This Skill Produces - A **label taxonomy** that encodes decisions, not just topics: status (needs-repro, needs-info, accepted, help-wanted, wontfix, someday) × type (bug, feature, docs, question) × effort (good-first-issue, deep-water) - **Batch triage rules**: the 30-second decision tree per issue, and the order to eat the backlog (newest-first, oldest closed honestly in bulk) - **Saved replies** for the eight recurring moments — needs-repro, duplicate, wontfix-with-respect, stale-close, "PR welcome" (said only when meant), the excited-first-contributor welcome - A **sustainable routine**: the 30-minute weekly triage block + the stale-p
- What This Skill Produces
- Required Inputs
- Framework
- Output Format
- Quality Checks
- Anti-Patterns
- Related
What does the maintainer-triage skill do?
Get an open-source repo's issue backlog from 400-and-drowning to triaged-and-honest in one pass — a label taxonomy that encodes decisions, batch triage rules you can apply in seconds per issue, saved replies that stay kind at scale, and stale-bot policy set with a conscience. Use when a maintainer says 'my issues are out of control', 'triage my backlog', 'set up labels for my repo', or dreads opening GitHub. Produces the taxonomy, the triage pass rules, saved replies, and a sustainable weekly routine.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill maintainer-triage --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.