Vd run the real path
Always-on skill pack that stops AI coding agents from claiming work is done when only the code path (not the real behavior) was verified. Portable SKILL.md for Claude Code, Codex, Cursor, and any agent.
npx -y skills add jpoindexter/verified-done --skill vd-run-the-real-pathAssembled 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.
What its author says it does
Copied from the file, not written here
When you can run it, run it. Prefer executing the real path — the one-shot command, the actual agent loop, the failing test now passing, the app in front of you — over inspecting the code that would run. "Looks right" and "the code clearly does X" are smells to verify, not conclusions. Use whenever you're about to conclude from reading rather than from running, especially when execution is cheap and available.
SKILL.md
2.2 KB, as published. Nobody here has run it
Run the Real Path
Reading code tells you what should happen. Running it tells you what does. When both are available, running wins — and it's usually cheaper than the paragraph you'd write justifying the inspection.
The smell
These thoughts mean stop and run it:
- "The code clearly does X."
- "This is wired correctly."
- "It should work now."
- "Looks right."
Your 100% certainty in unfamiliar territory is a cue to check, not a green light. The "looks right" signal is exactly where inspection fails and execution catches it.
How to apply
- Find the realest entry point you can run. The one-shot that exercises the whole user path beats any proxy: the agent loop over a mock, the CLI over a unit test, the deployed URL over localhost-only.
- Example:
vanta run "audit stripe.com"runs the real persona + tools + provider in one shot — that's the Done test, so run that, not the direct tool call.
- Example:
- Run it. Read the actual output. Not the exit code alone — the content. Did it return the graded report, or just not crash?
- If you genuinely cannot run it (no env, no creds, destructive), say so explicitly and mark the claim ◐ code-path in the ledger ([[vd-claim-ledger]]) — never silently upgrade it to ✅.
- Re-run after the last edit. A green from before your final change proves nothing about the code that ships.
Don't fake the run
A mock that returns success, a test that asserts nothing, a happy-path stub — these look like execution and prove less than honest inspection. If you stub it, the claim is ○ assumed, not ✅.
Governed by [[vd-done-is-executed]]. Pairs with [[vd-plumbing-vs-behavior]].