15 skills · sorted by relevance
Design error recovery for gh-aw workflows, including failed installations and API calls. Define retry limits, increasing wait times, error categories, and debug logs to handle temporary failures and prevent endless retries.
5-level error recovery escalation: retry, nudge, replan, fallback, force-done — each with entry criteria and timeout before escalating
The English summary is being prepared. Showing the original description.
Investigate failing tests, broken builds, and unexpected behavior through a structured debugging process. Reproduce the failure, narrow down its source, fix the root cause, and add a regression test that catches the same problem.
Design recovery paths for AI agents that loop, lose streamed responses, or hit service limits. Classify failures, choose retries or backup models, and set stopping rules to keep recovery attempts from causing further failures.
Handle failed tool calls with a clear recovery process. The skill distinguishes temporary problems from input or setup issues, chooses whether to retry or change approach, and records failures so unsuccessful tasks are not silently lost.
Troubleshoot unclear errors when converting documents to PDF with pandoc. Check installation, capture error logs, identify missing fonts or packages, and try alternative PDF engines, the tools that render the final document.
Guide agents through failures with timed retries, alternative methods, targeted fixes, and clear handoffs. It also explains when to continue with partial results, helping teams choose a recovery approach that fits the problem.
Standard recovery patterns for all squad agents. When something fails, adapt — don't just report the failure.
The English summary is being prepared. Showing the original description.
Guides systematic root-cause debugging. Use when tests fail, builds break, something that worked yesterday broke, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need to figure out what broke and why — a systematic approach to finding and fixing the root cause rather than guessing.
The English summary is being prepared. Showing the original description.
Standard recovery patterns for all squad agents. When something fails, adapt — don't just report the failure.
The English summary is being prepared. Showing the original description.
Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.
The English summary is being prepared. Showing the original description.
Diagnoses and fixes bugs, type errors, lint failures, CI/CD issues, and runtime errors via root-cause-first investigation. Use for defect remediation. NOT for investigation without a fix (see mk:investigate); NOT for build-only compilation errors (see mk:build-fix).
The English summary is being prepared. Showing the original description.
Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.
The English summary is being prepared. Showing the original description.
Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.
The English summary is being prepared. Showing the original description.
Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.
The English summary is being prepared. Showing the original description.