Skip to content
SkillCheatSheet Sign in

diagnosing-superpowers

An AI agent skill from obra/superpowers, scored 65 out of 100 by code.

65/ 100C

Code score by group

  • Spec20/20
  • Description13/20
  • Procedure10/15
  • Done criteria0/15
  • Resources7/10
  • Scripts5/8
  • Safety7/7
  • Upkeep3/5

It loses the most points in Done criteria (15), the group that checks whether there is a checklist and a step that verifies the work.

What the author says it does

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.

This is the description in the skill's own SKILL.md, written by its author, not by SkillCheatSheet.

Repository
obra/superpowers
Folder
skills/diagnosing-superpowers
License
MIT
GitHub stars
316,479
SKILL.md lines
121
Other files
19

Add diagnosing-superpowers to your agent

npx skills add obra/superpowers --skill diagnosing-superpowers

The command uses the open skills CLI. A skill is instructions and scripts your agent will follow, so read it first: open the folder on GitHub at the commit that was scored.

More skills from obra/superpowers

  1. dispatching-parallel-agents

    Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

    78B
  2. writing-skills

    Use when creating new skills, editing existing skills, or verifying skills work before deployment

    71B
  3. using-git-worktrees

    Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git…

    70B
  4. finishing-a-development-branch

    Use when implementation is complete, all tests pass, and you need to decide how to integrate the work

    69C
  5. test-driven-development

    Use when implementing any feature or bugfix, before writing implementation code

    69C
  6. verification-before-completion

    Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any suc…

    66C
  7. systematic-debugging

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

    64C
  8. using-superpowers

    Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

    62C

All skills in obra/superpowers

Scores come from a snapshot of 300 public GitHub repositories taken on 12 November 2026. Every score is the result of fixed checks run by code; no AI is involved. How scoring works.