From prove-it-validation
Discipline skill: before claiming any task succeeded, VERIFY it programmatically and SHOW the evidence (real command output, test runs, diffs, queries — and for anything visual, a screenshot / preview / short screen recording, attached to the PR or surfaced to the user) — never assert "done" on faith. Use whenever you're about to report a change as working, finished, fixed, or passing, and whenever the user says "prove it", "verify this actually works", "show me proof", "don't just tell me it's done", "demuéstralo", "verifica que de verdad funciona", "muéstrame la evidencia", "no me digas que sí sin probar". Rigid skill — follow it exactly; do not rationalize skipping verification. Bilingual (EN/ES).
How this skill is triggered — by the user, by Claude, or both
Slash command
/prove-it-validation:prove-it-validationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The rule: **a claim of success is not done until it's verified with evidence the user can see and reproduce.** "It should work", "I've fixed it", "tests will pass" are not acceptable terminal statements.
The rule: a claim of success is not done until it's verified with evidence the user can see and reproduce. "It should work", "I've fixed it", "tests will pass" are not acceptable terminal statements.
Explain and report in the user's language (EN/ES). Command output stays verbatim.
curl showing the status code, a SQL count, a diff).If you can only offer the weakest level, say so explicitly: "Unverified — I could not run X because Y."
Text output proves logic; it can't prove "the page renders right" or "the flow works end to end". When the claim is visual or behavioral, capture something the user can look at — and put it where they'll see it.
When to capture what:
How (use whatever the project already has; these are defaults):
page.screenshot(), page.video) or Puppeteer. They run in CI too.screencapture, Windows Snipping/Win+Shift+S, Linux scrot/grim), or ffmpeg to record a region to mp4/gif.ffmpeg so it embeds anywhere.artifacts/ dir — don't commit large binaries into the repo unless asked.Where to surface it:
gh pr comment <pr> --body "Proof: <what it shows>" with the image embedded (drag-drop in the GitHub UI, or upload and reference the URL). Put before/after shots in the PR description so the reviewer sees the change working without checking out the branch.⚠ The artifact must be real — actually captured from the running thing, this run. Never mock up, edit, or describe a screenshot you didn't take.
When you report completion, include a short Evidence block:
Claim: <what should be true>
Check: <command / test you ran>
Result: <verbatim output, trimmed to the relevant lines>
Artifact: <path/link to screenshot · recording · preview — for visual/behavioral claims; else "n/a">
Verdict: VERIFIED ✅ | PARTIAL ⚠ (what's left) | UNVERIFIED ❌ (why)
Use VERIFIED only when the output (and, for visual claims, the artifact) genuinely demonstrates the claim.
| Thought | Reality |
|---|---|
| "This is too simple to need testing" | Simple changes break things too. Run the check. |
| "The tests would pass" | Then running them costs nothing — run them. |
| "I'll say it's done and they'll tell me if not" | Shipping an unverified claim is the failure. |
| "I can't run it, so I'll assume it works" | Then label it UNVERIFIED, don't claim success. |
| "The output is probably fine" | Read it. "Probably" is not evidence. |
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
npx claudepluginhub jachana/claude-marketplace --plugin prove-it-validation