New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Verification Before Completion

by Archive228 in Archive228/loopkit

Use before claiming work is complete, fixed, or passing — before committing, opening a PR, or handing off.

MITAuto-check passedAgent Workflows

Install Verification Before Completion

skills CLI
$ npx skills add Archive228/loopkit --skill verification-before-completion -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Archive228/loopkit verification-before-completion --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Archive228/loopkit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/verification-before-completion .claude/skills/verification-before-completion && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
verification-before-completion
GitHub stars
756
Token cost
~1k tokens
SKILL.md length
528 words
Files
1
Skills in repo
43
Repo updated
First seen
Licence
MIT

At a glance

Use before claiming work is complete, fixed, or passing — before committing, opening a PR, or handing off.

  • Works in 5 steps: Identify — what exact command proves… → Run — execute it fresh, complete, in… → Read — full output, check exit code,… → …
  • Tasks that involve Verification before completion
  • SKILL.md covers The Iron Law, The gate function, Common false claims → what… and Red flags — you are about to…, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Verification Before Completion is an agent skill from Archive228/loopkit. Use before claiming work is complete, fixed, or passing — before committing, opening a PR, or handing off. Requires running the verification command in THIS turn and reading its output before any success claim.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Verification before completion. The repository describes itself as: 33 battle-tested skills + minimal .claude harness for any coding agent (Claude Code, Cursor, Codex, Gemini CLI). The licence is MIT.

When your agent uses it

  • Tasks that involve Verification before completion

Example prompts

  • “/verification-before-completion”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Identify — what exact command proves this claim?
  2. Run — execute it fresh, complete, in this turn.
  3. Read — full output, check exit code, count failures.
  4. Verify — does the output actually confirm the claim?
  5. Only then — make the claim, with the evidence attached.

What it can do on your machine

Read from SKILL.md and the folder at commit 5ae033e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Verification Before Completion loads about 1k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 528 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~60
When it runs · the whole SKILL.md, loaded when a task matches
~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Archive228/loopkit at commit 5ae033e, republished under its MIT licence (© Archive228). 528 words, ~1,023 tokens.

Download SKILL.mdSave it as .claude/skills/verification-before-completion/SKILL.md (or your agent's skills folder).
name
verification-before-completion
description
Use before claiming work is complete, fixed, or passing — before committing, opening a PR, or handing off. Requires running the verification command in THIS turn and reading its output before any success claim.

Verification Before Completion

Claiming work done without fresh verification is dishonesty, not efficiency. adversarial-verify is the what; this skill is the when — the gate you pass through right before any completion claim.

The Iron Law

NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE

If you have not run the verification command in this message, you cannot claim it passes. Not "should", not "probably", not "based on the diff".

The gate function

Before writing "done" / "fixed" / "green" / "ready to merge" — even in your own head:

  1. Identify — what exact command proves this claim?
  2. Run — execute it fresh, complete, in this turn.
  3. Read — full output, check exit code, count failures.
  4. Verify — does the output actually confirm the claim?
  5. Only then — make the claim, with the evidence attached.

Skip any step = you are lying to the user, not verifying.

Common false claims → what they actually need

ClaimRequiresNot sufficient
Tests passFresh test run, exit 0, 0 failures"should pass", previous run, "logic looks right"
Linter cleanLinter output, 0 errorsPartial check, extrapolating from unrelated files
Build succeedsBuild command, exit 0Linter passing, editor squiggles gone
Bug fixedReproduce original symptom, watch it not happenCode changed, "assumed" fixed
Regression test worksRed → green cycle verified (revert fix, watch test fail, restore, watch pass)Test passes once
Agent/subagent completedRead the VCS diff, verify claimed changes existAgent's own "success" report
Spec satisfiedLine-by-line checklist against the plan"Tests pass, phase complete"

Red flags — you are about to claim without verifying

  • Words like "should", "probably", "seems to", "looks good"
  • Satisfaction language ("Great!", "Perfect!", "Done!") before running the command
  • About to commit / push / open PR without a verification block in this turn
  • Trusting a subagent's own success report
  • "Just this once" thinking, or "I'm tired, close enough"
  • Partial verification (linter passed, so build must)
Show full SKILL.md (229 more words)Show less

Rationalization prevention

ExcuseReality
"Should work now"RUN it.
"I'm confident"Confidence ≠ evidence.
"Linter passed"Linter ≠ compiler ≠ tests.
"The agent said success"Read the diff yourself.
"Partial check is enough"Partial proves nothing about the whole.
"Different words, so rule doesn't apply"Spirit over letter.

Patterns

Tests

  • Run the test command. See 34/34 pass. Then say "all tests pass".
  • Never: "should pass now".

Regression tests (real red-green)

  • Write test → run (pass) → revert fix → run (MUST FAIL) → restore fix → run (pass).
  • Never: "I've added a regression test" without the red-green cycle.

Build

  • Run the build. See exit 0. Then say "build passes".
  • Never: "linter passed, build should too".

Agent delegation

  • Subagent reports success → check the VCS diff → verify the claimed change is actually there → report actual state.
  • Never: paste the agent's report and treat it as truth.

When this fires

Always, before:

  • Any variation of success / completion / fixed / passing / green
  • Committing, opening a PR, marking a task done, handing off
  • Moving to the next task
  • Any positive statement about the work's state

Pair with

  • adversarial-verify — the 11 shortcuts agents take to fake "done"; run through the list, then run through this gate.
  • clean-commits — clean commits require verified content.
  • The verifier subagent — dispatch it; then verify its report against the diff (per the "Agent delegation" pattern above).

The bottom line

Run the command. Read the output. THEN claim the result. Non-negotiable.

© Archive228, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/verification-before-completion of Archive228/loopkit.

Open the folder on GitHubat commit 5ae033e

Compare with similar skills

Verification Before Completion next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Verification Before Completion compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Verification Before Completion this skillArchive228/loopkit756—~1kAutomated safety check: PassMIT
Show Me Your Work Decision Logcursor/plugins10k9 repos~1.6kAutomated safety check: PassNone
PUA Looptanweai/pua20k1 repos~1.1kAutomated safety check: PassMIT
Scope Creep Guardlennney/stop-that-shit2.5k1 repos~2kAutomated safety check: PassMIT
Verification Before Completionfarm-fe/farm5.6k46 repos~1kAutomated safety check: PassMIT
Incremental Implementationaddyosmani/agent-skills103k1 repos~2.3kAutomated safety check: PassMIT

Similar skills

  • Show Me Your Work Decision Log

    cursor/plugins

    Official

    Keeps a TSV decision log for long or unattended agent runs, one row per decision with what, why, evidence and result, so a reviewer can check the work later.

    10k GitHub starsUsed in 9 repos~1.6k tokens
    Agent WorkflowsAuto-check passed

  • PUA Loop

    tanweai/pua

    Runs an unattended iterate-until-verified loop in which a user-set verify command, not the agent's own claim, decides when the task is finished.

    20k GitHub starsUsed in 1 repo~1.1k tokens
    Agent WorkflowsAuto-check passed

  • Scope Creep Guard

    lennney/stop-that-shit

    Keeps an agent focused on the requested work by applying a five-step ladder that checks for direct solutions, real gaps and speculative defenses before adding anything.

    2.5k GitHub starsUsed in 1 repo~2k tokens
    Agent WorkflowsAuto-check passed

  • Verification Before Completion

    farm-fe/farm

    A skill your agent uses when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any…

    5.6k GitHub starsUsed in 46 repos~1k tokens
    Agent WorkflowsAuto-check passed

  • Incremental Implementation

    addyosmani/agent-skills

    Delivers a change in thin vertical slices, each implemented, tested, verified and committed before the next, using vertical, contract-first or risk-first slicing.

    103k GitHub starsUsed in 1 repo~2.3k tokens
    Agent WorkflowsAuto-check passed

  • PUA High-Agency Governance

    tanweai/pua

    Pushes an agent to keep verifying and changing approach after repeated failures, using a diagnosis line, evidence-based completion and confirmation before risky edits.

    20k GitHub stars~502 tokensUpdated 28 days ago
    Agent WorkflowsAuto-check passed

More from Archive228/loopkit

All 43 skills in this repo

  • Hitl Escalate

    Archive228/loopkit

    Escalate blocked runs to a human via configured channel or fallback to BLOCKED.md and exit the loop.

    756 GitHub stars~1.2k tokensUpdated 2 mo ago
    Auto-check passed

  • Structured Output

    Archive228/loopkit

    Get JSON out of the model reliably. An agent skill from Archive228/loopkit.

    756 GitHub stars~830 tokensUpdated 2 mo ago
    Auto-check passed

  • Using Loopkit

    Archive228/loopkit

    A skill your agent uses when starting any conversation in a loopkit-enabled project - establishes how to find and use loopkit's 49 skills, requiring skill invocation before ANY response including…

    756 GitHub stars~1.4k tokensUpdated 2 mo ago
    Auto-check passed

  • Active Memory Reminder

    Archive228/loopkit

    Before compaction Loopkit extracts decisions into claude-decisions.json (machine-readable).

    756 GitHub stars~1.2k tokensUpdated 2 mo ago
    Auto-check passed

  • Eval Harness

    Archive228/loopkit

    Build a repeatable eval loop that grades agent output with an LLM judge, so prompt/skill changes get scored against a baseline instead of eyeballed.

    756 GitHub stars~876 tokensUpdated 2 mo ago
    Auto-check passed

  • Feature List JSON

    Archive228/loopkit

    Enumerate every end-to-end feature as strict JSON entries with passes:false, editable-passes-only discipline, and priority order.

    756 GitHub stars~1.2k tokensUpdated 2 mo ago
    Auto-check passed

Categories

Questions about Verification Before Completion

What does Verification Before Completion do?

Use before claiming work is complete, fixed, or passing — before committing, opening a PR, or handing off. Verification Before Completion is an agent skill from Archive228/loopkit. Use before claiming work is complete, fixed, or passing — before committing, opening a PR, or handing off.

When should I use Verification Before Completion?

Verification Before Completion fits situations like: tasks that involve Verification before completion.

How do I install Verification Before Completion in Claude Code?

Run `npx skills add Archive228/loopkit --skill verification-before-completion -a claude-code`. Or copy the skill folder (skills/verification-before-completion in Archive228/loopkit) into .claude/skills/verification-before-completion in your project. Claude Code loads it when a task matches its description.

How do I install Verification Before Completion in Codex?

Run `npx skills add Archive228/loopkit --skill verification-before-completion -a codex`. Or copy the skill folder (skills/verification-before-completion in Archive228/loopkit) into .agents/skills/verification-before-completion in your project. Codex loads it when a task matches its description.

Can I use Verification Before Completion in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Archive228/loopkit --skill verification-before-completion -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verification-before-completion, .gemini/skills/verification-before-completion, .github/skills/verification-before-completion and .opencode/skills/verification-before-completion in your project.

What does Verification Before Completion need to run?

SKILL.md names no scripts, command-line tools or credentials: Verification Before Completion is instructions for the agent only.

Does Verification Before Completion access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Verification Before Completion safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Verification Before Completion use?

Verification Before Completion is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Verification Before Completion use?

About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Verification Before Completion?

Skills that share tags, products or a category with Verification Before Completion: Show Me Your Work Decision Log (cursor/plugins, 10k stars), PUA Loop (tanweai/pua, 20k stars), Scope Creep Guard (lennney/stop-that-shit, 2.5k stars) and Verification Before Completion (farm-fe/farm, 5.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Verification Before Completion?

Archive228 (a GitHub user) maintains it in Archive228/loopkit, which has 756 GitHub stars. The repository holds 43 skills in this directory. The repository was last updated on July 14, 2026.

Source: Archive228/loopkit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.