[omh] Hermes Feedback Triage workflow: cluster customer signals and choose the next workflow.
SkillScore100Maintained
Automatic
◆Product Management pack
Last verified 8/18/2026
What it changes
Passed 22 of 22 test cases with the skill, and 11 of 22 without it.
Without skill50%
With skill100%
Checks it passed that the model alone missed
Recommend strategy workflow handoff.
Name the recommended follow-up workflow lane.
Refrain from generating an implementation plan.
and 12 more in the full report
11 fixed11 passed either way0 still failing0 broke
Pass-rate lift
+50 pp
Tokens
+42%
Agent turns
0%
Response time
-22%
Model gemini-3.6-flashMeasured 8/18/2026v322 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 11
Prompt
Triage these feedback tickets gathered specifically from the Enterprise Discord channel regarding API rate limits.
What was checked, without and with the skill
Checked
Without skill
With skill
Identify Enterprise Discord as the source boundary in the triage summary.
Missed
Passed
case-14 · gemini-3.6-flash · 8/18/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md109 linessingle file
Feedback Triage
This is a Hermes-native feedback-triage workflow skill.
Why This Exists
feedback-triage exists to keep customer and community signals from jumping straight into roadmap or coding; it clusters evidence, ranks signals, and chooses the next workflow.
Do Not Use When
The request already contains an accepted product decision and asks for implementation.
There are no feedback items, source boundary, or product area to classify.
The user wants current market research rather than triage of supplied signals.
Examples
Good example:
Prompt: Cluster these customer payment failure reports and feature requests before we plan fixes.
Expected behavior: Cluster bug signals and feature asks, rank severity or opportunity, and recommend research, planning, or coding as a next workflow.
Why: The input is mixed feedback that needs classification before delivery decisions.
Bad example:
Prompt: feedback-triage implement the accepted billing fix now.
Expected behavior: Route to planning or coding handoff instead of re-triaging.
Why: The decision is already accepted, so triage would add delay without improving evidence.
Completion Checklist
The source boundary, signal clusters, severity, and follow-up lane are named.
Bug, feature, research, strategy, and coding handoff outcomes stay separate.
The next workflow is recommended before any implementation claim.
Recovery Notes
If feedback lacks source or severity, ask for the missing signal before coding handoff.
If the item is actually a plan or research request, route to that workflow instead of triage.