← ClaudeAtlas

verify-skill-builderlisted

Use only when the user asks to create, audit, or refresh a project-local verify skill that drives the real app - "make a verify skill for this repo", "script how to prove this app works", "audit the verify skill", "the feature map is stale". Runs only when the user asks. Not for a one-off check (use superpowers:verification-before-completion). (formerly test-kitchen)
escoffier-labs/skillet · ★ 4 · AI & Automation · score 76
Install: claude install-skill escoffier-labs/skillet
# verify-skill-builder This skill builds and maintains verification instructions for a repository: a project-local skill that launches the actual app, drives it the way a user would, and captures evidence, so any later agent can prove a change works in the real thing instead of only in unit tests. **Core principle:** a verify skill that was never run is a draft. Every claim it makes about launching, driving, or cleaning up was observed once. Two modes. Say which you are in. Never edit product code in either. ## Create mode You write for an agent that reads this cold, mid-task, having never seen the app. 1. **Interview the repo, not the user.** Answer from the codebase and ask only what you cannot observe: the surface a user touches (web UI, CLI or TUI, desktop, API, library), how it starts locally (the repo's documented dev command, ports, env, seed data, auth), how an agent can drive it (existing harnesses first, then browser/CDP, a PTY or tmux session, or plain HTTP), what evidence can be captured, and whether two instances can run side by side. If the checkout does not build or start, report that and stop; do not edit product code to make it run. 2. **Write the verify skill** in the repository's project-local skills directory (for example `.claude/skills/verify-<app>/` or `.agents/skills/verify-<app>/`, whichever the harness and repo already use) with frontmatter that names the app, surface, and when to reach for it. Follow [references/verify-skill-template.md](refer