Issue Triage logo

Issue Triage

OrganizationPopular
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).

Overview

Publisherpaperclipai
Repositorypaperclip
Skill nameissue-triage
Stars
95.4K
Forks
16.2K
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by paperclipai on GitHub. Read the source before you install it.

Installation

Install the Issue Triage AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/paperclipai/paperclip/tree/master/packages/skills-catalog/catalog/bundled/paperclip-operations/issue-triage
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/paperclipai/paperclip.git /tmp/paperclip
mkdir -p .claude/skills
cp -r /tmp/paperclip/packages/skills-catalog/catalog/bundled/paperclip-operations/issue-triage .claude/skills/issue-triage
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Issue Triage in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Issue Triage on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Issue Triage is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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 in_progress, in_review, 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 request_confirmation or ask_user_questions. 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 in_progress or move to todo so the assignee picks it up.
  3. Reassign — the assignee is not the right specialty. Reassign and set in_review only if the new assignee is human, otherwise leave in_progress.
  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 request_confirmation, ask_user_questions, or request_board_approval and set the issue to in_review.
  6. Close — work is complete, duplicate, or no longer relevant. Set done or cancelled with a one-line reason.

If you cannot classify in under a minute of reading, escalate rather than guess.

Stuck-state heuristics

  • in_progress with no comments or document updates in the last 24h and no monitor or queued continuation → wake-needed.
  • in_review with no reviewer participant, no pending interaction, no approval — invalid review path → reassign to a real reviewer or move to todo.
  • blocked with no blockedByIssueIds, only free-text "blocked by X" → convert to first-class blockers or move to todo with a named action.
  • blocked with all blockers done → unblock the issue by setting status back; the assignee will wake.
  • Child issues all complete but parent still in_progress → confirm parent acceptance, then close.

Don't-do list

  • Do not @-mention agents during triage; mentions cost budget. Use direct reassignment instead.
  • Do not re-comment on a blocked issue if your most recent comment was also a blocked update with no reply since.
  • Do not cancel cross-team issues. Reassign to the responsible manager with a comment.
  • Do not change status without a comment that explains the change.

Output of a triage pass

A short comment chain or summary message that lists, per issue touched:

  • Issue id and title.
  • Verdict (resume / wake-needed / reassign / unblock / escalate / close).
  • The one action you took or asked for.

This is the bar for "the triage is done."

Frequently asked questions

What does the Issue Triage AI skill do?

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 use Issue Triage on TypingMind?

Because you install it once and use it with any model. Issue Triage is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Issue Triage in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/paperclipai/paperclip/tree/master/packages/skills-catalog/catalog/bundled/paperclip-operations/issue-triage. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Issue Triage?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Issue Triage?

As many as you like. As long as a model supports skills, you can use Issue Triage with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Issue Triage AI skill free?

Yes. It is published on GitHub by paperclipai under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇