Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.
The author's original description, preserved in English. It describes intent, not verified performance.
Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.
diagnosing-superpowers is a Claude Code Skill packaged as a fixed source snapshot. This editorial preview summarizes its declared purpose, on-disk structure and reviewable risk surface; it is not a controlled task evaluation.
Review scope
Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.
Observable capabilities
Source-declared purpose: Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is
Collected 20 file(s), including 0 script(s) and 15 reference(s).
Source-described workflow candidates are linked to exact source lines.
Limitations & scope
No controlled task evaluation was performed.
Exact token counts are unavailable and are not estimated.
Static findings are review prompts, not safety guarantees.
Relevant for
Technical readers evaluating this Skill
Reviewers studying how the Skill is constructed
02 / STRUCTURE
What ships with the skill
The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.
{
"name": "diagnosing-superpowers",
"description": "Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, \"it took too long\", \"why is it so expensive\", \"what is it doing\" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness."
}
03 / WORKFLOW
A reading of the operating sequence
This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.
01
Input
Confirm scope
Read the trigger conditions and decide whether this skill matches the current task.
Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.
Items warrant review
101 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.
Network accessObserved
File writesObserved
Credential useNot observed
Note
File modification is described or implemented
96 occurrences
This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 96 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.
A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 5 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.
Review source evidence and runtime permissions before installing.
05 / CONTEXT
Where context can be spent
Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.
Exact token counts unavailable
All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.
No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.
06 / EVALUATION
Controlled evaluation
No controlled evaluation
This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.
Not tested
07 / USAGE
Use with the source in view
Install command
git clone https://github.com/obra/superpowers.git
cd superpowers
# Copy this skill directory into one of:
# ~/.claude/skills/diagnosing-superpowers
# .claude/skills/diagnosing-superpowers
Open the immutable source at https://github.com/obra/superpowers/tree/22f0b463e7a5e579904dd6211a520321035526f7/skills/diagnosing-superpowers/SKILL.md.
Review the license, prerequisites and all bundled resources.
Install the skill into a personal or project-level Claude Code skills directory.
Restart or refresh Claude Code so the skill can be discovered.
Verify installation
Check that SKILL.md is discoverable at the destination, then ask Claude Code to use the named skill on a test task.
Prerequisites
No controlled task evaluation was performed.
Exact token counts are unavailable and are not estimated.
Static findings are review prompts, not safety guarantees.
Example prompts
Representative task
Use the diagnosing-superpowers skill to help with this task. First summarize what the skill will do, then execute its documented workflow and show the source-linked evidence for each major decision.
Inspect before use
Read the diagnosing-superpowers skill files at https://github.com/obra/superpowers/tree/22f0b463e7a5e579904dd6211a520321035526f7/skills/diagnosing-superpowers/SKILL.md. Explain its workflow, required tools, permissions and the main risks before I decide whether to install it.
08 / VERDICT
A decision, with its limits attached
Strengths
Source is pinned to an immutable commit.
Instructions and resource inventory are available for inspection.
Considerations
Effectiveness has not been measured.
Review the source and runtime requirements before installation.
Research conclusion
Editorial preview: this dossier has a complete research layout; controlled evaluation is deferred until after deployment.
09 / PROVENANCE
Traceable by construction
The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.
Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.