Agent skill

issue-triage-live

Triage the user's REAL issue tracker — read open issues via the GitHub/Linear connector, label / prioritise / dedupe / flag them, and apply the safe changes — not advice on triage. Use when asked to triage my issues, clean up the backlog, label and prioritise open issues, or sort my GitHub issues in Cowork. Reads open issues via the connector, classifies by type / severity / duplicate, applies labels and priorities, and produces a triage-report artifact with the applied changes and the ones needing a human call.

mohitagw158561,255★ · 1 repos on radarProfile →
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill issue-triage-live --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 4 KB
Bundled scripts: none
Path: skills/issue-triage-live/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Issue Triage (Live) An untriaged backlog is a pile no one trusts. In Claude Cowork this skill reads the *real* open issues, classifies each, applies the safe labels and priorities in place, and hands back a report — turning a heap into a queue, while leaving the judgement calls to a human. ## What This Skill Produces - **The triaged backlog** — each open issue typed (bug / feature / question / duplicate), severity-tagged, and prioritised - **Applied changes** — labels and priority set via the connector; duplicates linked to their canonical issue - **A triage-report artifact** — what was applied, the duplicate clusters, and the issues that need a human decision ## Required Inputs Ask for these if not provided: - **The repo/project** — which GitHub repo or Linear team, and the filter (all open, untriaged only) - **The label & priority scheme** — existing labels and what P0–P3 mean here - **Autonomy** — apply labels/priority automatically, or preview first (default: apply labels, preview closes/merges) ## Framework: The Triage Pass 1. **Type it** — bug / feature / question / duplicate / needs-info. 2. **Severity for bugs** — blocking / major / minor, from impact and reproducibility.

What's inside
Steps it walks through
  1. What This Skill Produces
  2. Required Inputs
  3. Framework: The Triage Pass
  4. Execution (Cowork)
  5. Output Format
  6. Summary
  7. Applied
  8. Duplicate clusters
  9. Needs a human
  10. Quality Checks
  11. Anti-Patterns
  12. Example Trigger Phrases
More from pm-claude-skills
All skills →
About this skill
What does the issue-triage-live skill do?

Triage the user's REAL issue tracker — read open issues via the GitHub/Linear connector, label / prioritise / dedupe / flag them, and apply the safe changes — not advice on triage. Use when asked to triage my issues, clean up the backlog, label and prioritise open issues, or sort my GitHub issues in Cowork. Reads open issues via the connector, classifies by type / severity / duplicate, applies labels and priorities, and produces a triage-report artifact with the applied changes and the ones needing a human call.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill issue-triage-live --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.

Keep going