Report · marked 25 Aug 2026

obra/superpowers

An agent can work here, but it will waste turns finding its footing.

Shell · 277,481 stars · 195 files · branch main

68 /100 B

Instructions 15/27Whether the repo tells an agent how to behave before it starts guessing. Losing marks on instruction quality.Setup 8/18Whether an agent can install the project and get it running without a human. Losing marks on deterministic install and environment config.Verification loop 15/25Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy. Losing marks on continuous integration and lint and format rules.Context economy 20/20Whether the repo fits in a context window, or fights it. Full marks.Navigability 10/10How quickly anything new can orient itself. Full marks.

Higher is better. Accent marks what is costing you most.

Fix these first

Instruction quality

Worth fixing: it's under 200 characters, which is closer to a placeholder than instructions; it never states a build, test, or run command; has no headings to structure it; has no code blocks.

Deterministic install

Commit the lockfile your package manager generates. Without it, an agent's install and your install are different builds, and 'works on my machine' becomes unfalsifiable.

Continuous integration

A CI workflow doubles as machine-readable documentation: it's the one file that states, unambiguously, the exact commands that must succeed.

The full marking

Every deduction below names the file or setting it came from.

Instructions 15/27 B-

Whether the repo tells an agent how to behave before it starts guessing.

✓Agent instruction file 12/12

AGENTS.md is present, which is the format the most tools read.

Also found: CLAUDE.md

✗Instruction quality 0/12

Present but too thin to change an agent's behavior.

Worth fixing: it's under 200 characters, which is closer to a placeholder than instructions; it never states a build, test, or run command; has no headings to structure it; has no code blocks.

✓README as an entry point 3/3

README has a clear getting-started section.

Setup 8/18 C

Whether an agent can install the project and get it running without a human.

✗Deterministic install 0/6

No lockfile. An agent installing dependencies may not get what CI got.

Commit the lockfile your package manager generates. Without it, an agent's install and your install are different builds, and 'works on my machine' becomes unfalsifiable.

✓Discoverable commands 6/6

Commands are declared where an agent will look for them.

scripts/ directory

✗Environment config 2/4

Env vars are mentioned in the README but there's no example file to copy.

Add a .env.example listing every variable with a safe placeholder value. It's the cheapest possible fix and it unblocks the whole first run.

✗Pinned runtime version 0/2

No pinned runtime version.

Add a .nvmrc, .python-version, or equivalent so the agent's toolchain matches yours.

–Reproducible environment n/a

Not applicable — a library doesn't need a container to be worked on.

Verification loop 15/25 B-

Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy.

✓Tests exist 8/8

79 test files against 62 source files.

e.g. docs/superpowers/specs/2026-01-22-document-review-system-design.md, docs/superpowers/specs/2026-02-19-visual-brainstorming-refactor-design.md, docs/superpowers/specs/2026-03-11-zero-dep-brainstorm-server-design.md

✓Test command is discoverable 7/7

An agent can find and run `pytest`.

✗Continuous integration 0/4

No CI config. Nothing outside a developer's laptop enforces correctness.

A CI workflow doubles as machine-readable documentation: it's the one file that states, unambiguously, the exact commands that must succeed.

✗Lint and format rules 0/3

No linter or formatter config. Style is tribal knowledge, so agent output will drift from yours.

A formatter config is the cheapest way to stop reviewing whitespace in agent diffs. It moves style from opinion to a command.

✗Static type checking 0/3

No static type checking.

A type checker gives an agent an error message instead of a runtime surprise. It's the second-fastest feedback loop after the compiler.

Context economy 20/20 A+

Whether the repo fits in a context window, or fights it.

✓No committed build output 6/6

No generated directories committed.

✓.gitignore hygiene 3/3

.gitignore covers 13 patterns.

✓File sizes fit in context 6/6

No source file is large enough to crowd out a context window.

✓Repository weight 5/5

About 4.4MB checked out, which is comfortable.

Here is your AGENTS.md

Drafted from what is actually in this repository: the install command from your lockfile, the commands you already declare, your real directory layout. Anything marked TODO needs a person. Save it at the root as AGENTS.md.

AGENTS.md — drafted for obra/superpowers

undefined

Open the raw markdown or curl -o AGENTS.md agentreadme.com/draft/obra/superpowers.md

Show the mark

The badge re-checks daily, so it keeps up as the repository changes. Use mark again to force it now.

[![agent ready](https://agentreadme.com/badge/obra/superpowers.svg)](https://agentreadme.com/obra/superpowers)

Other Shell repositories, marked

mattpocock/skills 68 B ohmyzsh/ohmyzsh 46 C msitarzewski/agency-agents 42 C d3/d3 68 B nvm-sh/nvm 77 B+ tw93/Mole 85 A

All Shell repositories