What do I need to use Issue Triage (Live)?

The repo / project; The label & priority scheme; Autonomy.

Is Issue Triage (Live) free to use?

Yes — run it free in the browser playground (no API key needed for the sponsored trial, or bring any provider key), or install it into Claude Code, Cursor, ChatGPT and more via npx pm-claude-skills. MIT-licensed and open source.

Issue Triage (Live)

Q: How do I know the Issue Triage (Live) output is good?

The skill verifies itself against its own quality checks: No issue was auto-closed; Labels/priorities use the project's real scheme; Duplicate clusters name a canonical issue and link the rest; Priority reflects severity × reach, not gut feel.

🔵 Stable🕐 updated 2026-07-20 🔷 SkillSpec L3 ⚙ ships an executable helper pm-cowork-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.

▶ Run it free — no key needed 📝 Grade your existing draft View SKILL.md ↗

🗣 Say this to your agent

“Triage my open GitHub issues in Cowork.”“Label and prioritise the backlog, and cluster the duplicates.”“Sort my Linear issues — types, severity, priority.”“Clean up the issue tracker and flag what needs me.”

What to give it

▸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)

✅ The bar it holds itself to

Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.

✓No issue was auto-closed

✓Labels/priorities use the project's real scheme

✓Duplicate clusters name a canonical issue and link the rest

✓Priority reflects severity × reach, not gut feel

✓Ambiguous/strategic issues were escalated, not force-labelled

⚠️ What it refuses to do

**Auto-closing** issues — propose, don't close.

**Inventing labels** the project doesn't use.

**Exact-match dedupe** that misses reworded duplicates.

**Labelling a thin issue P2** instead of asking for repro/info.

Install

npx pm-claude-skills add --agent claude   # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcp

Related skills

🔌 Embed this skill

Drop this on your blog, docs, or site — it renders a "Run this skill" card:

<div data-pm-skill="issue-triage-live"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>

💬 Discussion

Issue Triage (Live) is one of 750 open-source professional AI agent skills — all SkillSpec L3. Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog