CtrlK
BlogDocsLog inGet started
Tessl Logo

diagnosing-superpowers

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.

76

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

96%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exceptionally well-structured instruction skill: concise, concrete, and sequenced with validation checkpoints and feedback loops. The only weakness is progressive disclosure — the body references templates/ and prompts/ files that are not present in the bundle.

Suggestions

Ship the referenced templates/ files (case.md, report.md, issue.md, bundle-README.md) and prompts/ files (analyst-common.md, the seven analyst dimension files, scrub.md, scrub-audit.md, similar-session.md) so every inline reference resolves.

Alternatively, if any prompt/template is intentionally omitted from this bundle, note that explicitly at first reference so navigation expectations are clear.

DimensionReasoningScore

Conciseness

Lean and efficient throughout — no padded explanation of concepts Claude already knows, and dense high-value artifacts like the Quick reference and Red Flags tables where every token earns its place.

5 / 5

Actionability

Highly concrete guidance: exact paths ('~/.superpowers/diagnosing-superpowers/<session-id>/'), enumerated dispatch files, copy-ready commands ('zip -r', 'tar -czf', 'gh'), and named redaction levels (skeleton/evidence/full) with no vague direction.

5 / 5

Workflow Clarity

Seven clearly numbered steps with explicit run conditions, approval gates, and a real feedback loop (scrub then scrub-audit, 'repeating both until the audit returns CLEAN') appropriate for sharing/exporting session data.

5 / 5

Progressive Disclosure

SKILL.md is a well-structured overview with one-level-deep, clearly signaled references, but a large share of referenced bundle paths (templates/* and prompts/*) do not exist in the bundle, which is more than a minor navigation gap.

4 / 5

Total

19

/

20

Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, highly specific description with comprehensive natural trigger terms and an explicit 'Use when' clause. The only deduction is the second-person voice ('your human partner'), which the rubric penalizes on specificity.

DimensionReasoningScore

Specificity

Names the domain and lists multiple concrete actions/observables — 'repeated work, ignored plans, stumbles, poor results, a skill that didn't fire' and 'build a bug report' — which is comprehensive coverage; reduced from 5 to 4 because the second-person framing ('your human partner wants to know') triggers the voice penalty.

4 / 5

Completeness

Explicitly answers both 'what' (diagnose why a session went wrong / build a bug report for maintainers) and 'when' via a concrete 'Use when...' clause with specific trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive coverage of natural terms users would actually say, including the literal complaint strings 'it took too long', 'why is it so expensive', and 'what is it doing' alongside synonyms like 'stumbles' and 'ignored plans'.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — diagnosing superpowers sessions and building bug reports for superpowers maintainers — with domain-specific triggers ('a skill that didn't fire', 'superpowers session') that minimize conflict with other skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
obra/superpowers
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.