Is Systematic Debugging safe and trustworthy?

tashan scores Systematic Debugging on public evidence — it is currently active. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Systematic Debugging?

Drop the skill folder into ~/.claude/skills/ (user scope) or .claude/skills/ (project scope).

Who maintains Systematic Debugging?

30 GitHub contributors, source: obra/superpowers.

‹ The Index

Systematic Debugging

skill

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Works with: Claude Code (native) · Cursor, Codex CLI (manual)
native: this artifact type is that client's own format

Category: Dev Tools & CI — see all ranked ›

Work: Debugging

Who it is for: Software engineer

Install (Claude Code):

cp -r systematic-debugging ~/.claude/skills/

Not graded: shares its documentation with 13 other capabilities. A grade read off another project’s document would borrow its credit, or its blame.

Adoption: 5 repos
Upkeep: 92.0
Freshness: 83.0
Evidence coverage: 84% of the inputs this score can use — the rest are unknown, and the score is discounted for it
Health: active
Contributors: 30
License: MIT

Security audit

Not scanned yet. We audit npm-published capabilities for known advisories, install-time scripts and permission surface; this one has no npm package we can resolve, or has not reached the queue.

Its own instructions

Its SKILL.md says when to use it, shows worked examples, covers setup and states a limitation.

Read from the capability’s own SKILL.md. This is not a grade and does not compare to the instruction-depth verdict on an MCP server — a skill has no tools to document, so that rubric does not apply to it.

What changed recently

2026-08-19 the tashan score for systematic-debugging rose to 53.0, from 48.0 Upkeep, freshness or adoption moved enough to change how this measures.
2026-08-20 the tashan score for systematic-debugging rose to 58.0, from 53.0 Upkeep, freshness or adoption moved enough to change how this measures.
2026-08-21 the tashan score for systematic-debugging fell to 53.0, from 58.0 Upkeep, freshness or adoption moved enough to change how this measures.

You are reading this because you came looking. tashan Pro gives tashan doctor the history behind it, so a run over your own config says which of YOURS moved.

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

We recorded 4 changes to Systematic Debugging in the last 45 days. Pro tells you on the day — for the servers in your own config, not the ones you thought to look up.

The whole series behind any row, back to the first day we measured it
The replacement, named — not just the news that something died
tashan doctor over your own config, on your own machine

Start a 7-day trial › Everything measured on this page stays free.

source ↗ · skill:obra/systematic-debugging

Already running this? Check your whole config — free, in your browser, nothing installed. Or npx tashan-cli doctor locally, which sends nothing at all.

Measured 2026-09-13 · scorer s5 · how · something wrong here?