Is systematic-debugging-ed8874 safe to install?

SaferSkills independently audited systematic-debugging-ed8874 (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

library/methodologies/superpowers/skills/systematic-debugging/SKILL.md · 1 file

library/methodologies/superpowers/skills/systematic-debugging/SKILL.md1.3 KB · Markdown

name: systematic-debugging

description: Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Requires root cause investigation first.

Systematic Debugging

Overview

Random fixes waste time and create new bugs. ALWAYS find root cause before attempting fixes.

Core principle: No fixes without root cause investigation first.

The Four Phases

Root Cause Investigation - Read errors, reproduce, check changes, gather evidence at component boundaries
Pattern Analysis - Find working examples, compare against references, identify differences
Hypothesis and Testing - Form single hypothesis, test minimally, one variable at a time
Implementation - Create failing test case, implement single fix, verify

When 3+ Fixes Fail

Stop and question the architecture. Pattern of repeated failures indicates architectural problems, not implementation bugs.

Red Flags (STOP and Follow Process)

"Quick fix for now"
"Just try changing X"
Proposing solutions before tracing data flow
"One more fix attempt" (when already tried 2+)

Agents Used

Process agents defined in systematic-debugging.js

Tool Use

Invoke via babysitter process: methodologies/superpowers/systematic-debugging

systematic-debugging-ed8874— agent skill

Is systematic-debugging-ed8874 safe to install?

Systematic Debugging

Overview

The Four Phases

When 3+ Fixes Fail

Red Flags (STOP and Follow Process)

Agents Used

Tool Use

Audit the pieces. Scan the whole. Decide.