Install any skill in seconds. Free to start, no credit card required.
Get Started Free →withwoz/woz-benchmark
Deprecated alias — use `/woz benchmark`.
Passed 12 of 18 test cases with the skill, and 4 of 18 without it.
and 8 more in the full report
10 fixed5 passed either way8 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
The target repo `/home/dev/repo` is clean and `/tmp/woz-benchmark-100.yaml` is ready. What single-line warning should be issued before executing the benchmark command?
| Checked | Without skill | With skill |
|---|---|---|
| Warns the user that execution will take several minutes because prompts run twice. | Missed | Passed |
The instructions your model reads when the skill loads.
Run a side-by-side comparison of WOZCODE vs vanilla Claude Code on the user's own codebase. Each prompt runs twice against a fresh copy of the repo with git reset --hard between runs, so the target MUST be a clean git repo.
TRIGGER: "compare woz", "how much does woz save", "benchmark woz", "woz vs claude", "show me the savings", "is woz worth it", or /woz-benchmark.
Ask for all three in ONE short message (< 10 lines). Do not re-explain what the benchmark does — the user already invoked it.
.env)? Skip if the repo is self-contained."Do NOT ask about the model. Default to opus in the YAML config. Only switch to sonnet or haiku if the user volunteers a different choice in their answer.
Before writing any config, verify the target is usable:
test -d <target>
git -C <target> rev-parse --git-dir
git -C <target> status --porcelain
If the directory doesn't exist, isn't a git repo, or has uncommitted changes, STOP and tell the user how to fix it.
Use the Write tool to create a YAML file at /tmp/woz-benchmark-<timestamp>.yaml (get the timestamp from date +%s). Format:
test cases passed, vs 4 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.