issue-triage

Triage stale, blocked, and stalled Todero inbox issues into one next action each.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/nabitllc/todero --skill issue-triage-nabitllc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-triage
Source: https://github.com/nabitllc/todero/tree/main/packages/skills-catalog/catalog/bundled/todero-operations/issue-triage
Command: npx skills add https://github.com/nabitllc/todero --skill issue-triage-nabitllc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agent inboxes accumulate stale, blocked, and stalled issues with no clear priority, forcing managers to manually inspect every thread to know what needs attention. ## Core Features & Use Cases - Per-issue verdicts: Classify each issue as resume, wake-needed, reassign, unblock, escalate, or close, with exactly one concrete next action. - Stuck-state heuristics: Detect stalled in_progress issues, invalid review paths, free-text blockers, and completed parents using heartbeat-context data. - Budget-safe triage: Avoid @-mentions and redundant comments, and escalate instead of guessing when classification is unclear. - Use Case: At the start of a shift, a manager runs a triage pass over all in_progress, in_review, and blocked assignments and ends with a summary listing each issue's verdict and the action taken. ## Quick Start Triage my Todero inbox and give each stale, blocked, or in-review issue a verdict and one next action.

Frequently Asked Questions about issue-triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I triage a backlog of stalled agent issues?

Fetch the compact assignment list from the inbox-lite endpoint, then pull heartbeat-context for each candidate issue. Classify each into exactly one verdict—resume, wake-needed, reassign, unblock, escalate, or close—and record the single action taken per issue.

How to detect stalled in_progress issues automatically?

An issue is stalled when it is in_progress with no comments or document updates in the last 24 hours and no monitor or queued continuation. These are classified as wake-needed and get one comment naming the exact next action.

When should I not run an inbox triage pass?

Skip triage when you are checked out on one specific named issue, or when a thread already has an open request_confirmation or ask_user_questions pending. Re-triaging while waiting for a response only adds noise.

What should I do with blocked issues that have no blockers listed?

Convert free-text blocked-by notes into first-class blockedByIssueIds entries, or move the issue to todo with a named action. If all blockers are done, unblock the issue and the assignee will wake automatically.

Why avoid @-mentioning agents during triage?

Mentions cost budget each time they fire. Use direct reassignment instead, and never re-comment on a blocked issue if your last comment was already a blocked update with no reply.