Agent skill · operations · paperclipai
issue-triage
Triage Paperclip inbox issues that are stale, blocked, in-review, or assigned-but-not-progressing, and decide a single next action per issue (resume, reassign, unblock, escalate, or close).
Why this skill is useful
Provides a structured workflow for issue triage that includes specific decision-making criteria and actions not commonly found in general knowledge.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 75,771 stars on the source repository.
What this skill does
Issue Triage Convert a noisy inbox into a small set of clear next actions. Each pass through this skill should leave every touched issue with a defined owner, status, and the single concrete action that will move it forward. When to use Daily or shift-start review of inprogress, inreview, and blocked assignments. An inbox has many open assignments and no clear priority. A manager wants a status read on their reports without asking each agent. You are woken by a comment that suggests an old issue stalled. When not to use You are checked out on one specific issue and the wake context names it. Work that issue, do not triage the whole inbox. An issue thread already has an open requestconfirmation or askuserquestions. Wait for the response — re-triage is noise. Inputs GET /api/agents/me/inbox-lite for the compact assignment list. For each candidate issue, GET /api/issues/{issueId}/heartbeat-context for compact state including blockerAttention, executionState, ancestors, and commentCursor. Only fall back to the full thread when the heartbeat context is not enough. Per-issue triage decision For each issue, classify into exactly one of: 1. Resume — execution path is alive. Confirm the assignee is set and let the heartbeat continue. Do not comment. 2. Wake-needed — assignee is stalled with no live continuation. Post one comment that names the blocker resolution or the exact next action, then leave inprogress or move to todo so the assignee picks it up. 3. Reassign — the assignee is not the right specialty. Reassign and set inreview only if the new assignee is human, otherwise leave inprogress. 4. Unblock — a first-class blockedByIssueIds entry is now done or cancelled. If cancelled, replace or remove it from blockedByIssueIds. The blockers-resolved wake will fire automatically when all are done. 5. Escalate — the issue needs board, CTO, or user input. Create a requestconfirmation, askuserquestions, or requestboardapproval and set the issue to inreview. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills paperclipai/issue-triage