Borrowing it
Nothing to install: this file belongs to phuoctrung-ppt/ai-sdlc-workflow. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/phuoctrung-ppt/ai-sdlc-workflow/master/.cursor/skills/error-recovery/SKILL.mdgit clone --depth 1 https://github.com/phuoctrung-ppt/ai-sdlc-workflowWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/phuoctrung-ppt/ai-sdlc-workflow/error-recovery)<a href="https://agentmods.dev/skills/phuoctrung-ppt/ai-sdlc-workflow/error-recovery"><img src="https://agentmods.dev/badge/skills/phuoctrung-ppt/ai-sdlc-workflow/error-recovery.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00036 | $0.00534 |
| Opus 5 | $0.00018 | $0.00267 |
| Sonnet 5 | $0.00007 | $0.00107 |
| Haiku 4.5 | $0.00004 | $0.00053 |
Grade A, and why
error-recovery scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Error Recovery
Fix the root cause. Do not hide failures.
Classify first
| Class | Typical signals | Approach |
|---|---|---|
| Build error | bundler/compiler exit ≠ 0, missing module, bad config | Fix import/path/config; re-run the same build command |
| Type error | tsc / typechecker diagnostics |
Narrow types with guards; never as any to silence |
| Test fail | assertion mismatch, timeout, mock drift | Fix code or update test to match intended contract; never comment out the test |
| Runtime error | stack trace in logs, unhandled rejection | Reproduce → null/edge path → minimal guard or correct invariant |
| Integration error | HTTP 4xx/5xx to dependency, queue/DB connection | Check env, contract, mocks; fix call site or test double |
Root-cause checklist (answer all four before editing)
- What is the exact error message (full text, not a paraphrase)?
- Which file:line does it point to (or nearest caller if in deps)?
- Is this a symptom of an earlier failure (wrong assumption, stale mock, missing migrate)?
- What is the smallest change that restores the invariant without masking the error?
If you cannot answer 1–2, gather more evidence before changing code.
Fix pattern
- Read the full error message (and preceding context in the log).
- Identify file:line.
- Read ~10 lines of surrounding context (and callers if needed).
- Propose a minimal fix that addresses the root cause.
- Verify: re-run the failing command; confirm adjacent behavior still passes (related tests / typecheck).
Anti-patterns (forbidden)
- ❌ Add
try/catch(or swallow) only to hide an error without fixing the cause - ❌ Cast
as any/ disable the typechecker to bypass a type error - ❌ Comment out or skip a failing test to go green
- ❌ Change unrelated files “while here” without evidence they cause the failure
Agent
Use during phases fix, implement-backend, implement-frontend with workers that own the failing files.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 47 lines · 36 tokens per session scan A b86be121ec49
error-recovery is a skill published in the GitHub repository phuoctrung-ppt/ai-sdlc-workflow (2 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 534 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.