systematic-debugging agent skill by obra
Guides a systematic approach to any bug, test failure, or unexpected behavior, before proposing fixes.
At a glance
| Publisher | obra |
|---|---|
| Repository | obra/superpowers (15 listed skills) |
| Category | Testing and QA |
| License | MIT |
| Last commit | October 9, 2026 (repository) |
| SKILL.md | 278 lines, 1,436 words |
| Bundled files | 11 files |
| Quality score | 80/100 · B Passes all seven graded checks |
| Security scan | Not scanned |
| README badge | Get the badges for this listing |
Before you install
Read from the skill's files at the directory's October 19, 2026 snapshot: what ships with it, what its code reads, and the terms it is published under.
- Bundled scripts: 2 script files (1 TypeScript, 1 Shell). Your agent may run them, so read them first.
- License: MIT, an open-source or open-content license.
Install systematic-debugging
The skills CLI works with Claude Code, Codex, Cursor and other agents; the other routes copy the folder by hand.
npx skills add https://github.com/obra/superpowers/tree/main/skills/systematic-debuggingtmp="$(mktemp -d)"
git clone --depth 1 https://github.com/obra/superpowers.git "$tmp/repo"
mkdir -p .claude/skills
cp -R "$tmp/repo/"skills/systematic-debugging .claude/skills/
rm -rf "$tmp"python3 ~/.codex/skills/.system/skill-installer/scripts/install-skill-from-github.py \
--repo obra/superpowers \
--path skills/systematic-debuggingobra/superpowers is third-party code. Read SKILL.md and any bundled scripts before you install it.
How the author describes it
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
From the description field of SKILL.md. Agents read this line to decide when to load the skill.
Sections in SKILL.md
- Overview
- The Iron Law
- When to Use
- The Four Phases
- Phase 1: Root Cause Investigation
- Phase 2: Pattern Analysis
- Phase 3: Hypothesis and Testing
- Phase 4: Implementation
- Red Flags - STOP and Follow Process
- your human partner's Signals You're Doing It Wrong
- Common Rationalizations
- Quick Reference
- When Process Reveals "No Root Cause"
- Supporting Techniques
Files in the skill folder
CREATION-LOG.mdSKILL.mdcondition-based-waiting-example.tscondition-based-waiting.mddefense-in-depth.mdfind-polluter.shroot-cause-tracing.mdtest-academic.mdtest-pressure-1.mdtest-pressure-2.mdtest-pressure-3.md
Suede Skill Check: 80/100 · B
Report snapshot · · graded-v2
The rubric totals 100 points; published scores are capped at 99. Security scan: not scanned.
Source revision: bb92a7774141. Report version 473aa695df0c. Badge URLs follow the latest listing; save the report to keep this version.
Download report · Request a fresh review
What to review next
- Description length: 1 of 5 points. 5 for 150–600 characters; 3 for 100–900; 1 for 50–1,024.
- Boundary clause: 0 of 4 points. 4 when the description says when not to use the skill (“Not for …”, “Do not use …”, “Use … instead”).
- Example request: 0 of 3 points. 3 when the description quotes an example request (3–60 characters in quotation marks).
Add declarations and bundled files when they describe the skill’s actual needs. Update the source, then request a fresh review with the changed commit or PR.
systematic-debugging passes the required frontmatter check and all seven graded checks, which cover the SKILL.md format, a declared license and a commit in the last year. Those checks earn 56 of the score’s points; the rest come from description quality, instruction depth, bundled files, maintenance and curated-list citations. How the score works.
See the checks and points
| Check | Result |
|---|---|
| Frontmatter parses and declares a name and a description | Pass |
| Name uses lowercase letters, digits and hyphens, 64 characters or fewer | Pass |
| Name matches the skill's folder name | Pass |
| Description is between 50 and 1,024 characters | Pass |
| Description says when an agent should use the skill | Pass |
| SKILL.md body is 500 lines or fewer | Pass |
| A license is declared in the frontmatter or the repository | Pass |
| Repository has a commit in the last 12 months | Pass |
| Score component | Points |
|---|---|
| Structural checks | 56 of 56 |
| Description length | 1 of 5 |
| Boundary clause | 0 of 4 |
| Example request | 0 of 3 |
| Instruction depth | 7 of 7 |
| Reference files | 0 of 3 |
| Bundled scripts | 0 of 2 |
| Recent maintenance | 9 of 9 |
| Curated-list citations | 7 of 7 |
| Tool permissions declared | 0 of 2 |
| Compatibility declared | 0 of 2 |
Two badges for systematic-debugging
Choose the numeric badge, the letter badge, or both. Each links to this skill’s Suede listing; either valid linked badge can qualify for the feature offer.
[](https://skills.suedeai.ai/directory/obra/superpowers/systematic-debugging/)
[](https://skills.suedeai.ai/directory/obra/superpowers/systematic-debugging/)<a href="https://skills.suedeai.ai/directory/obra/superpowers/systematic-debugging/"><img src="https://skills.suedeai.ai/directory/obra/superpowers/systematic-debugging/score.svg" alt="Suede Skill Check: 80/100" width="160" height="175"></a>
<a href="https://skills.suedeai.ai/directory/obra/superpowers/systematic-debugging/"><img src="https://skills.suedeai.ai/directory/obra/superpowers/systematic-debugging/badge.svg" alt="Suede Skill Check: Grade B" width="160" height="175"></a>Suede Certified on the shield refers to this published structural quality check. Security scan: not scanned. Read the methodology.
Limited-time feature offer: display either the numeric or letter badge in your repository or skill README (both also qualify), then request badge verification. Eligible skills scoring 80–99 can receive a featured placement after Suede verifies at least one valid badge linked to the skill’s listing. Suede has not announced an end date.
Where this skill is cited
obra/superpowers appears in 6 curated lists: BehiSecc/awesome-claude-skills, ComposioHQ/awesome-claude-skills, VoltAgent/awesome-agent-skills, hesreallyhim/awesome-claude-code, karanb192/awesome-claude-skills, travisvn/awesome-claude-skills.