Troubleshooting
Curated, sanitized export of 21 agent-skill packages for Claude Code and Codex, gated by an automated publication audit (no secrets, no local paths).
npx -y skills add mj-deving/pai-skills --skill TroubleshootingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Debugging and incident management — 6-step triage, Stop-the-Line, competing hypotheses for dev-time bugs plus incident detection, response, and blameless postmortems for production issues. USE WHEN debugging, fix bug, error recovery, troubleshooting, reproduce bug, root cause, stack trace, test failing, build broken, incident, outage, SEV1, SEV2, postmortem, blameless review, incident response, 5 whys.
SKILL.md
1.4 KB, as published. Nobody here has run it
Troubleshooting
Unified skill for when things break — in development or in production.
Workflow Routing
| Request Pattern | Route To |
|---|---|
| Debugging, fix bug, error recovery, troubleshooting, reproduce bug, root cause, stack trace, test failing, build broken | Debugging/SKILL.md |
| Incident, outage, SEV1, SEV2, postmortem, blameless review, incident response, war room, 5 whys, incident timeline | Incident/SKILL.md |
Examples
Example 1: Debug a failing test
User: "This test is failing intermittently"
→ Routes to Debugging
→ Non-reproducible bug playbook: isolate, instrument, competing hypotheses
Example 2: Production incident
User: "The API is returning 500s in production"
→ Routes to Incident
→ New incident workflow: triage, mitigate, communicate, resolve
Example 3: Post-incident review
User: "Write a postmortem for yesterday's outage"
→ Routes to Incident/Postmortem
→ Blameless review: timeline, contributing factors, action items