failure-signal-audit
starsforks
How to install failure-signal-audit?
rlaope/oh-my-hermes/failure-signal-audit
$npx -y skills add rlaope/oh-my-hermes --skill failure-signal-audit[omh] Failure Signal Audit workflow: find swallowed errors, unsafe fallbacks, hidden UI/runtime failures, and missing propagation before they become false green status.
SKILL.md
| 1 | # Failure Signal Audit |
| 2 | |
| 3 | This is a Hermes-native `failure-signal-audit` workflow skill. |
| 4 | |
| 5 | ## Why This Exists |
| 6 | |
| 7 | `failure-signal-audit` exists so Hermes users can ask for this workflow in chat and receive a structured, evidence-bounded OMH operating surface instead of ad hoc narration. |
| 8 | |
| 9 | ## Do Not Use When |
| 10 | |
| 11 | - The request is already handled by a narrower explicit skill with stronger evidence. |
| 12 | - The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents. |
| 13 | - The only safe answer is to ask for missing authority, credentials, target, or observed evidence first. |
| 14 | |
| 15 | ## Examples |
| 16 | |
| 17 | Good example: |
| 18 | |
| 19 | - Prompt: failure-signal-audit check this frontend and agent trace for swallowed errors, false green status, and dangerous fallbacks. |
| 20 | - Expected behavior: Produce `prepare_failure_signal_audit` with required context, wrapper actions, and not-evidence boundaries. |
| 21 | - Why: The prompt names a real workflow surface that Hermes can orchestrate without hiding execution. |
| 22 | |
| 23 | Bad example: |
| 24 | |
| 25 | - Prompt: failure-signal-audit silently patch every catch block and claim the system is reliable now. |
| 26 | - Expected behavior: Report the missing observed evidence or authority instead of claiming the external step happened. |
| 27 | - Why: Prepared OMH guidance is not platform, runtime, connector, file, memory, or delivery evidence. |
| 28 | |
| 29 | ## Completion Checklist |
| 30 | |
| 31 | - Audit scope, source surfaces, and evidence types are named. |
| 32 | - Swallowed errors, dangerous fallbacks, propagation gaps, and false-green claims are reported as separate finding types. |
| 33 | - Each finding names location or evidence ref, severity, user/operator impact, and a smallest safe remediation route. |
| 34 | - No remediation, runtime repair, verification, CI, merge, or future reliability claim is made without observed follow-up evidence. |
| 35 | |
| 36 | ## Recovery Notes |
| 37 | |
| 38 | - If no code/trace/runtime evidence is supplied, prepare the audit plan and request the smallest source surface to inspect. |
| 39 | - If the user wants live service SLO or incident review, route to reliability-review. |
| 40 | - If the user wants rendered browser proof, route frontend visual evidence to visual-qa before PASS. |
| 41 | |
| 42 | ## OMH Context Rail |
| 43 | |
| 44 | - This skill is part of OMH's Hermes workflow layer, not a standalone executor. |
| 45 | - Product context: OMH is a Hermes-native workflow pack: choose skills, shape work, prepare artifacts, show status, and hand off with evidence boundaries. |
| 46 | - Current lane: **Automation and status** (`achievements`, `workspace-audit`, `production-audit`, `automation-blueprint`, `github-event-ops`, `agent-board`, `gateway-intent-card`, `voice-operator`, `+26 more`) - schedules, status, health, and ops review. |
| 47 | - If the user intent belongs to another OMH lane, hand back to `oh-my-hermes` or name the adjacent workflow instead of force-fitting this skill. |
| 48 | - Cross-skill context: every OMH skill: match lane; generic tool can render or execute. |
| 49 | - Generic-tool checkpoint: image->img-summary; frontend->frontend/a11y/visual-qa; paper->paper-learning; content->content-operator; media->media-input-operator; file->materials-package; search->web-research; live->live-info-operator; audit->workspace/production/security; failures->build-failure; verify->verification-gate; code->codegraph/onboarding/ultraprocess. |
| 50 | - Coverage: Every generated workflow skill carries this rail. |
| 51 | - Normal users talk to Hermes; OMH CLI is infra. |
| 52 | - Boundary: Prepared OMH routing, cards, handoffs, or artifacts are not observed execution, image generation, delivery, review, CI, merge-readiness, or merge evidence. |
| 53 | |
| 54 | ## Use When |
| 55 | |
| 56 | Use when Hermes should audit code, frontend/browser behavior, agent traces, or runtime reports for failures that were swallowed, downgraded, hidden by fallbacks, or reported as green without enough evidence. |
| 57 | |
| 58 | Strong routing signals: `failure-signal-audit`, `failure signal audit`, `silent failure`, `silent failures`, `silent failure hunter`, `swallowed error`, `swallowed errors`, `empty catch`, `ignored exception`, `hidden failure`, `hidden failures`, `dangerous fallback`, `bad fallback`, `fallback hides errors`, `missing error propagation`, `error propagation`, `console errors ignored`, `network failures ignored`, `false green`, `false pass`, `무음 실패`, `조용한 실패`, `숨은 실패`, `삼킨 에러`, `에러 삼킴`, `위험한 fallback`, `위험한 폴백`, `폴백이 에러 숨김`, `실패 신호 감사`, `실패 신호` |
| 59 | |
| 60 | ## Catalog Metadata |
| 61 | |
| 62 | Category: `review` |
| 63 | Phase: `failure-signal-audit` |
| 64 | Hermes role: `reviewer` |
| 65 | Quality tier: `workflow-surface-gated` |
| 66 | |
| 67 | Quality bar: |
| 68 | |
| 69 | - Name the user-facing workflow objective, required context, next action, and stop condition. |
| 70 | - Separate prepared guidance from observed platform, runtime, connecto |
People who liked this also viewed
6 picksType
- find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 2026
- grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026
- vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026
- setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026
- triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026
