Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →mkurman/triage-issue
Triage a bug or issue by exploring the codebase to find root cause, then create a GitHub issue with a TDD-based fix plan.
2 of 23 test cases passed with the skill.
Tokens, turns and time describe resource use, not a dollar price.
Lift withheld: 3 comparable cases; this report requires 8.
A test case the skill fixed. Same model, same prompt, with and without the skill.
Can you triage a problem for me?
| Checked | Without skill | With skill |
|---|---|---|
| Asks only one question to clarify the problem before taking any other action. | Missed | Passed |
The instructions your model reads when the skill loads.
Investigate a reported problem, find its root cause, and create a GitHub issue with a TDD fix plan. This is a mostly hands-off workflow - minimize questions to the user.
Get a brief description of the issue from the user. If they haven't provided one, ask ONE question: "What's the problem you're seeing?"
Do NOT ask follow-up questions yet. Start investigating immediately.
Use the Agent tool with subagent_type=Explore to deeply investigate the codebase. Your goal is to find:
Look at:
git log on relevant files)Based on your investigation, determine:
Create a concrete, ordered list of RED-GREEN cycles. Each cycle is one vertical slice:
test cases passed with the skill
More skills from the same source and nearby in the registry, with their headline benchmark lift.