Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ai-builder-club/verifier-setup
Set a repo up to prove engineering-task work actually works before it ships. Investigates the repo, ensures a one-command dev stack (`dev-local`) exists, asks whether verification runs locally or in a sandbox (crabbox), confirms/installs the driver (the `playwright-cli` skill for web by default). Outputs three artifacts: a committed `/verify` skill (per-task verification SOP — spawn a verifier sub-agent → drive the app → screenshot/video proof → open a PR with the proof embedded), the `/dev-loca
Passed 11 of 16 test cases with the skill, and 5 of 16 without it.
and 5 more in the full report
8 fixed7 passed either way7 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
When generating a fresh .claude/skills/verify/SKILL.md file, where is the base template markdown file retrieved from?
| Checked | Without skill | With skill |
|---|---|---|
| Reads assets/verify.template.md as the source template | Missed | Passed |
The instructions your model reads when the skill loads.
/verify skillGoal: leave the repo able to prove an engineering task works before it ships —
run once, and it wires up everything the per-task /verify loop needs.
You are setting up — not verifying anything yourself right now. The /verify
template lives at assets/verify.template.md (next to this skill). Parallels
dev-local-setup (which generates a script + its skill doc): a setup skill that
leaves behind reusable, repo-specific artifacts.
Running verifier-setup end-to-end leaves the repo with:
/verify skill — .claude/skills/verify/SKILL.md, the repo-tailored
per-task verification SOP (spawn a verifier sub-agent → drive the app →
screenshot/video proof → open a PR with the proof embedded). Generated in Step 5./dev-local skill + its script — scripts/dev-local.sh and
.claude/skills/dev-local/SKILL.md, via dev-local-setup (Step 2) if not
already present. The one-command stack /verify depends on.playwright-cli skill for web apps (Step 2);
for non-web, the concrete exercise tool confirmed present.Before creating anything, take stock — the repo may already have some of this, under whatever name or layout its team chose. Look for the capability, not a specific filename; the paths below are only examples. For each, decide reuse as-is / adapt-extend / create fresh — never blindly overwrite working setup:
Makefile/Procfile
target, docker-compose, package scripts (e.g. scripts/dev-local.sh, but any
form counts).playwright-cli skill), or the relevant API/CLI client.Every later step is conditional on this inventory: if a capability exists and works,
test cases passed, vs 5 / 16 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.