diagnosing-superpowers

An agent skill by obra, from obra/superpowers. Tags: api, debugging, developer-tools, mcp.

What 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.

Install

With the skills CLI, which installs into Claude Code, Codex, Cursor and other agents:

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

Or copy the skill folder into Claude Code's skills directory by hand (~/.claude/skills for every project, or .claude/skills inside one):

git clone --depth 1 https://github.com/obra/superpowers
cp -r superpowers/skills/diagnosing-superpowers ~/.claude/skills/diagnosing-superpowers

Safety box score

Not rated yet. A safety box score grades what a skill and its scripts can reach on the machine of whoever installs it, across eight categories from shell execution to secrets access. Anyone can request one from this page; it is saved for everyone. How the score works.

Source

Repository

obra/superpowers (all skills from this repository)

Path

skills/diagnosing-superpowers/SKILL.md

Branch

main

Updated

2026-09-19

Related skills

• claude-api — Reference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration.
• mcp-builder — Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools.
• mcp-developer — Use when building, debugging, or extending MCP servers or clients that connect AI systems with external tools and data sources.
• dispatching-parallel-agents — Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
• subagent-driven-development — Use when executing implementation plans with independent tasks in the current session
• systematic-debugging — Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes