Is Verification Before Completion free to use?

Yes — run it free in the browser playground (no API key needed for the sponsored trial, or bring any provider key), or install it into Claude Code, Cursor, ChatGPT and more via npx pm-claude-skills. MIT-licensed and open source.

Verification Before Completion

Q: How do I know the Verification Before Completion output is good?

The skill verifies itself against its own quality checks: The original request was re-read verbatim, and every requirement (incl. implicit format/tone/length) was audited; Everything runnable was actually run — no "should work" in the record; At least one adversarial read happened, from the recipient's perspective; Cross-section consistency was checked (summary↔body, numbers↔numbers).

🔵 Stable🕐 updated 2026-10-11 ✅ 4.8/5 🔷 SkillSpec L3 pm-method

Verify work actually meets its brief BEFORE declaring it done — a structured self-review pass that catches the gaps, unmet requirements, and untested claims that 'looks finished' hides. Use when about to hand over any deliverable (document, code, analysis, plan), when past work kept coming back with 'you missed…', or as the standing final step of any multi-step task. Produces the verified deliverable plus a short verification record: what was checked, what was found and fixed, what remains open.

▶ Run it free — no key needed 📝 Grade your existing draft 📱 Use as an app View SKILL.md ↗ What changed

🗣 Say this to your agent

“Check this is really done.”“Verify this meets the brief before I send it.”“Review my deliverable against the requirements.”“What's missing before we call this finished?”

✅ The bar it holds itself to

Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.

✓The original request was re-read verbatim, and every requirement (incl. implicit format/tone/length) was audited

✓Everything runnable was actually run — no "should work" in the record

✓At least one adversarial read happened, from the recipient's perspective

✓Cross-section consistency was checked (summary↔body, numbers↔numbers)

✓The record states residuals honestly rather than implying total coverage

⚠️ What it refuses to do

Do not verify against your memory of the ask — memory is where the third requirement went to die

Do not treat a clean-looking output as evidence — polish and correctness are uncorrelated at exactly the worst moments

Do not skip the pass under time pressure — the pass is minutes; the rework it prevents is hours

Do not produce a zero-findings record on complex work — that's theatre; look harder or say what you couldn't check

Do not hide residuals to seem finished — an honest "untested under X" builds more trust than the failure it predicts

Install

npx pm-claude-skills add --agent claude   # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y -p pm-claude-skills pm-claude-skills-mcp

Related skills

🔌 Embed this skill

Drop this on your blog, docs, or site — it renders a "Run this skill" card:

<div data-pm-skill="verification-before-completion"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>

💬 Discussion

Verification Before Completion is one of 1307 open-source professional AI agent skills — all SkillSpec L3. Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog