← ClaudeAtlas

create-verify-skilllisted

Write a verify skill into a project, so that an agent can drive the real app, feature by feature, and keep the evidence. It adds a runner, a feature map and a short skill file under the project's .claude/skills/verify-<app>/, and proves them with one real run. The user starts it with /create-verify-skill in the project. This version drives command-line steps only.
SeanoChang/seanock · ★ 0 · AI & Automation · score 73
Install: claude install-skill SeanoChang/seanock
# create-verify-skill A project's tests show that its parts work. Nothing shows that the app works unless someone runs it. This skill gives the project a scripted way to do that: a feature map, a runner that follows it, and evidence that stays. You write the feature map. A script writes the rest. ## What the project gets ```text <project>/.claude/skills/verify-<app>/ SKILL.md when and how to run it, and how to read a result features.json the feature map verify the runner (a copy; the project does not need this skill to run it) <project>/.verify/runs/<run>/ the evidence of each run, ignored by git ``` ## Steps 1. **Read the app.** Find how it is built, how it starts, and what a user does with it: the README, the command list (`--help`), the routes, the end-to-end tests. List three to seven features in the user's words; each one becomes an entry of the map. This version runs commands only. If the app is a server or has a screen, cover what a command can reach, and say in your report what is not covered. 2. **Write the frame.** ```bash python3 ~/.claude/skills/create-verify-skill/scripts/scaffold.py --project <root> --app <name> ``` Exit 0 and a last line that starts `create-verify-skill: wrote` means that the folder is there. Exit 2 means that nothing was written; the line says why. The script never changes a folder that exists. 3. **Write the feature map** in `features.json`. The shape: ```json {