Triage a raw, vague issue or bug report into a structured document that names what is known, what is missing, and what to do next.
NewMaintained
Automatic
◆Project Management pack
Last verified 9/26/2026
What it changes
1 of 25 test cases passed with the skill.
Pass-rate lift
—
Tokens
+371%
Agent turns
0%
Response time
+191%
Model gemini-3.6-flashMeasured 9/26/2026v21 of 25 cases passed with skill · 2 comparable
Tokens, turns and time describe resource use, not a dollar price.
Lift withheld: 2 comparable cases; this report requires 8.
See it in action
A test case the skill fixed. Same model, same prompt, with and without the skill.
Prompt
Triage this submission: 'Managers need to export monthly audit logs to CSV so compliance audits take under 5 minutes. They should be able to filter by date range.' Provide the triage evaluation and recommended next step.
What was checked, without and with the skill
Checked
Without skill
With skill
classifies the issue as Feature Request
Passed
Passed
recommends /plan-a-feature as the next step
Missed
Passed
case-15 · gemini-3.6-flash · 9/26/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md155 lines2 files
Project Context
CLAUDE.md: !find . -maxdepth 1 -name "CLAUDE.md" -type f
project-discovery.md: !find . -maxdepth 3 -name "project-discovery.md" -type f
personal config directory: !bash "${CLAUDE_PLUGIN_ROOT}/scripts/han-config-dir.sh" 2>/dev/null || echo "$HOME/.claude"
As your first action, use the Read tool on .han/config.md inside the personal config directory path above. A read
that returns no file is no personal configuration: continue silently. When that file or the project .han/config.md
probe supplies content, apply it per config-rule.md, which governs precedence
between the two files, relative-path resolution, and what to do with a file that reads but cannot be used.
Triage Approach
Work only from what the reporter wrote. Do not infer facts that are not stated. This is the single most important
constraint in this skill.
Classify the issue type before doing anything else. The type drives what counts as missing information.
Severity and reproducibility are estimates based on what is known. For a Bug, Regression, Performance, or Security
issue, mark them Unknown when not inferable. For a Feature Request, Question, or Other issue, omit them entirely when
they are not inferable (see Step 4) rather than rendering Unknown.
The recommended next step is the single most appropriate han skill (or "clarify with reporter") to run after triage
completes.
Project context (CLAUDE.md, project-discovery.md) is read only to identify Suspected Areas. Never use it to supply
information the reporter omitted.
Source the standard by invoking han-communication:readability-guidance and apply it as you write the triage
document. Hold its default audience frame: a capable reader who did not do this work and lacks the author's context.
Issue Triage
Step 0: Resolve the Issue Text
Determine the issue text from the argument:
If the argument is a path to an existing file, read that file; its contents are the issue text.
Otherwise the argument text itself is the issue text.
If no argument was given and no issue text is present in the conversation, ask the reporter to paste the issue or bug
report, then stop until they provide it.