Assess community issues, validate technical claims, request missing evidence, and prepare valid work for human disposition.
80%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./.agents/skills/triage-issue/SKILL.mdTriage establishes whether a reported OpenShell problem is technically valid and sufficiently evidenced. A maintainer decides whether the project accepts valid work and where it belongs on the roadmap. Inspect current GitHub label names and descriptions; the general issue lifecycle uses state:* labels, but their exact names may change.
For a specific issue, assess it when requested. For batch triage, first show the issue count and a sample of titles and obtain explicit authorization before posting comments or changing labels on multiple issues. Do not infer that a label alone authorizes bulk changes.
Do not apply an acceptance state, place issues on the roadmap, or make a product investment decision. Do not introduce agent:* workflow labels. Follow SECURITY.md if the report may disclose a vulnerability; do not copy sensitive details into a public comment.
Follow Labeling and Notifications: defer area/topic classification labels until the work is accepted. They drive subscriber notifications, so technical classification alone must not send unaccepted intake to those streams. Continue to record appropriate triage state.
gh issue view <id> --json number,title,body,state,labels,author,comments. Follow Label Discovery in CONTRIBUTING.md to retrieve every page of current state:* label definitions and resolve unclear meanings. Check for previous triage, new human evidence, an existing owner, and duplicate issues.> **📋 triage-agent**. Explain the evidence, any exact missing information, and the next human decision. Keep this assessment judgment and comment in triage./label-issue to reconcile labels. Pass the assessment outcome and reviewed label subset through its assessment-only path. For accepted work, request classification when needed.If substantial technical uncertainty remains, recommend create-spike with specific questions to answer. A direct user request can separately authorize planning or implementation through build-from-issue; it does not change the issue's recorded disposition.
NVIDIA/OpenShell
2e5589b
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.