Jev Failure Triage
SkillDev toolsLets your agent analyze a failed run and decide whether to retry, fix a dependency, request access, or change approach.
Use Jev Failure Triage in Claude, ChatGPT or Ahel Desktop
Free. Sign in, add Jev Failure Triage and connect your AI. About a minute.
Also: Claude Code · Cursor · Codex
Then ask your AI: use the Jev Failure Triage skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; Ahel provides instructions and does not run this skill.
No other account needed.
Add Ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
About this skill
[omh] Failing run handed to Jev for a next move: Jev failure triage: retry, fix a dependency, ask for access, or change approach on a failing run. Use when the user says: jev-failure-triage, jev failure triage, ask jev if this failure is transient.
What this skill tells your AI
The instructions your AI receives, as published by rlaope/oh-my-hermes in skills/omh-jev-failure-triage/SKILL.md and read by Ahel’s review.
Required: the failing command, an error excerpt, and the retry count. Output: failure_triage/v1 next move with its rule.
Read omh-routing/references/jev-rail.md before the first ask: consent, what leaves the machine, limits, and non-answer statuses. Prepared OMH routing is not execution or approval. Shared product, routing, compatibility, and evidence rules: omh-routing/references/skill-common-rail.md.
Contract: references/full-contract.md. Preset: references/preset.md.
Procedure
- Name what leaves the machine: the command and an error excerpt (plus earlier attempt excerpts when repeating).
- Call
omh_jev_askwithpreset: failure_triage/v1,state{error_excerpt, last_command, earlier_attempts}, andattempts_so_far. - Report
policy_result.outcomeand its rule beside the raw answers. - Hand the fix to
build-failure-triageoragent-debug; a rerun still needs the host's approval.
Completion Checklist
- Preserve workflow intent and stop conditions; load the full contract before claiming completion.
- Reply in the user's own words and the host's own voice: its SOUL.md persona owns reply language, tone, speech level, and sentence endings, progress updates included (where it sets no language, use the one the user wrote in), and OMH shapes structure and content only; OMH's record terms (surface, lane, wrapper, handoff, evidence boundary, not_observed) stay in records and tool calls, never in the sentence the user reads unless they ask about one; and when a stop condition or a decision the user owns ends the turn, offer the next action as a question rather than declaring what will not be done.
- Report the tool's status, ask_id, served model, and cost source; a non-answer is
not_observedwithrule: not_answered:<status>, never Jev's answer. - Record observed delegation results; use Hermes-native subagent/delegation features when available: native subagents -> Hermes delegation when available, otherwise sequential lanes.
Recovery Notes
- Tool missing,
consent_not_observed, or refused: follow the rail's recovery section; never simulate an answer.
Workflow Lane
advisory local context
Signals
- GitHub stars
- 3k
- Forks
- 237
- Last commit
- Oct 2026
Advanced
- Item type
- skill
- Key
omh-jev-failure-triage- Source
- github.com/rlaope/oh-my-hermes
github.com/rlaope/oh-my-hermes