Triage Issue Skill
Analyze a GitHub issue, verify claims against the codebase, and close invalid issues with a technical response.
Multi-Agent Harness for Production AI
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add aden-hive/hive --skill triage-issue -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add aden-hive/hive --skill triage-issue -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add aden-hive/hive --skill triage-issue -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add aden-hive/hive --skill triage-issue -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/aden-hive/hive/tree/HEAD/.claude/skills/triage-issueFrom the publisher
Analyze a GitHub issue, verify claims against the codebase, and close invalid issues with a technical response.
User provides a GitHub issue URL or number, e.g.:
/triage-issue 1970/triage-issue https://github.com/adenhq/hive/issues/1970gh issue view <number> --repo adenhq/hive --json title,body,state,labels,author
Extract:
If issue is already closed, inform user and stop.
Read the issue body and identify:
For each technical claim:
Categorize the issue as one of:
For issues to be closed, draft a response that:
Use this template:
## Analysis
[Brief summary of what was investigated]
## Technical Details
[Explanation with code references]
## Why This Is Working As Designed
[Rationale]
## Recommendation
[What the user should do instead, if applicable]
---
*This issue was reviewed and closed by the maintainers.*
Present the draft to the user with:
## Issue #<number>: <title>
**Claim:** <summary of claim>
**Finding:** <valid/invalid/misunderstanding/etc>
**Draft Response:**
<the markdown response>
---
Do you want me to post this comment and close the issue?
Use AskUserQuestion with options:
If user approves:
# Post comment
gh issue comment <number> --repo adenhq/hive --body "<response>"
# Close issue
gh issue close <number> --repo adenhq/hive --reason "not planned"
Report success with link to the issue.
"The claim that secrets are exposed in plaintext misunderstands the encryption architecture. While
SecretStris used for logging protection, actual encryption is provided by Fernet (AES-128-CBC) at the storage layer. The code path is: serialize → encrypt → write. Only encrypted bytes touch disk."
"The requested feature would require [X] which violates [fundamental constraint]. This is not a limitation of our implementation but a fundamental property of [technology/protocol]."
"This scenario is already handled by [code reference]. The reporter may be using an older version or misconfigured environment."
© 2026 Skills Rack.
---name: hivedescription: Multi-Agent Harness for Production AI---# .claude/skills/triage-issue/SKILL.mdFAQ
Download .claude/skills/triage-issue/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/aden-hive/hive.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.