triage

Route GitHub issues to triage states using predefined labels.

779|80|Updated Jun 20, 2025
One-click install
npx skills add https://github.com/Haohao-end/openagent --skill triage-haohao-end
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/Haohao-end/openagent/tree/main/api/internal/core/skills/catalog/triage
Command: npx skills add https://github.com/Haohao-end/openagent --skill triage-haohao-end

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly triage incoming GitHub issues by deciding whether they need more information, should be handled by an agent, should be handled by a human, or should be closed as won't fix.

Core Features & Use Cases

  • Issue state routing: Moves issues into the correct triage state using the repository’s established vocabulary (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix).
  • Information sufficiency checks: Detects missing details and routes the issue to a “waiting for more info” state.
  • Correct ownership assignment: Routes fully specified issues to agent or human handling, or documents a reason for wontfix closure.

Quick Start

Use the triage skill to evaluate the attached issue and set it to the appropriate state (needs-info, ready-for-agent, ready-for-human, or wontfix) based on the repository’s triage terms.

Frequently Asked Questions about triage

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

FAQPage Schema
How do I automatically triage GitHub issues into workflow states?

To triage GitHub issues, this skill evaluates each incoming item and routes it to predefined workflow states like needs-info, ready-for-agent, ready-for-human, or wontfix based on information sufficiency and routing requirements.

How does issue triage identify missing information in a bug report?

Issue triage detects missing details by checking information sufficiency, moving incomplete reports to a needs-info state to wait for the reporter to provide further clarification before execution.

What is the workflow routing process for deciding between agent vs human issue handling?

Workflow routing assigns fully specified GitHub issues to either ready-for-agent or ready-for-human states, ensuring correct ownership by matching the work item requirements with the appropriate execution path.

When should I close an incoming GitHub issue as wontfix during triage?

You should close an issue as wontfix during triage when it falls outside project scope, requiring a clear rationale to be produced and documented to explain the closure decision.

Can I use this issue triage skill with custom GitHub workflow labels?

This skill applies to issue intake by moving items into the correct triage state using the repository’s established vocabulary, relying on predefined labels like needs-triage and wontfix.

Do I need additional dependencies to route issues to the right next step?

No additional dependencies are required to route issues, as this prompt-only skill evaluates attached GitHub issues and sets the appropriate state directly based on triage terms.