Setup

Set up the current repo for the powers workflow: generate CLAUDE.md and scripts/verify.sh from the plugin templates, detecting what's detectable and asking about the rest. Use when the user asks to set up / initialize powers in a repo. NOT for general project scaffolding.From its SKILL.md

Install

npx -y skills add craftycorvid/powers --skill setup

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.6 KB, as published. Nobody here has run it

Set Up a Repo for powers

Produce the two rollout files — CLAUDE.md and scripts/verify.sh — filled in for THIS repo, prove they work, and commit them.

Never clobber. If CLAUDE.md already exists, don't overwrite it: check what's missing (a VERIFY_LEVEL= line, Commands or Pointers sections) and offer to append only that. If scripts/verify.sh exists, leave it as-is and just run it (step 4). If both exist and nothing is missing, say the repo is already set up and stop.

1. Detect

Look before asking. From the repo, determine:

Name + one-liner — package.json / Cargo.toml / pyproject.toml, else the directory name.
Test command — package.json test script, cargo test, ./gradlew build, pytest (pytest.ini / tests/ + Python), Makefile test target, go test ./....
Build command, if distinct from test.
Entry point — main/bin from the manifest, or the obvious src root.
Whether any test infrastructure exists at all — this drives the recommendation in step 2.

2. Ask

One AskUserQuestion round, not an interrogation:

VERIFY_LEVEL — recommend tdd (strict: source changes require test changes); recommend build instead if step 1 found no test infrastructure.
Test command — only if detection was ambiguous (multiple candidates or none). Skip the question when detection was clear.

Do not ask about invariants — the template's commented prompts stay in place for the user to fill in later.

3. Generate

Fill the plugin templates with what steps 1–2 established and write them to the repo:

${CLAUDE_PLUGIN_ROOT}/templates/CLAUDE.md.template → CLAUDE.md (name, one-liner, VERIFY_LEVEL, commands, entry point; leave the Invariants comments untouched).
${CLAUDE_PLUGIN_ROOT}/templates/verify.sh.template → scripts/verify.sh with the real test command. chmod +x scripts/verify.sh.

4. Prove and Commit

Run scripts/verify.sh. Green → commit both files on the current branch: chore: set up powers workflow. Red → show the failure and ask whether to fix the command or commit anyway; never commit a broken verify.sh silently.

If this isn't a git repo, offer git init first — the verify gate is a no-op outside git, so setup without git buys nothing.