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

Completion Verification

by cbrock84 in cbrock84/headcount

Verifies that work is actually complete before it is claimed to be — running the checks, reading the output, and confirming the original request was satisfied rather than approximated.

MITAuto-check passedDevelopment

Install Completion Verification

skills CLI
$ npx skills add cbrock84/headcount --skill completion-verification -a claude-code

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

GitHub CLI
$ gh skill install cbrock84/headcount completion-verification --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/cbrock84/headcount.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/technology/skills/completion-verification .claude/skills/completion-verification && 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
completion-verification
GitHub stars
2k
Token cost
~479 tokens
SKILL.md length
252 words
Files
1
Skills in repo
175
Repo updated
First seen
Licence
MIT

At a glance

Verifies that work is actually complete before it is claimed to be — running the checks, reading the output, and confirming the original request was satisfied rather than approximated.

  • Works in 5 steps: Run the real check, not a subset. The… → Read the output. An exit code of zero… → Re-read the original request. Not your… → …
  • Tasks that involve Pull requests
  • SKILL.md covers Before claiming done, What a claim must carry, Honest incompleteness and Never
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Completion Verification is an agent skill from cbrock84/headcount. Verifies that work is actually complete before it is claimed to be — running the checks, reading the output, and confirming the original request was satisfied rather than approximated. Use this before saying something is done, fixed, or passing; before committing or opening a pull request; and whenever a claim of success has not been backed by command output.

Its SKILL.md is about 480 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 Development, covering Pull requests. The repository describes itself as: An agent organization structured as a company — 15+ departments, 125+ skills, each independently installable, citing the standards and regulators that settle the question. Runs… The licence is MIT.

When your agent uses it

  • Tasks that involve Pull requests

Example prompts

  • “Use the completion-verification skill to verify that work is actually complete before it is claimed to be — running the checks, reading the output…”
  • “/completion-verification”

Workflow steps

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

  1. Run the real check, not a subset. The command the project gates on, on the current state of
  2. Read the output. An exit code of zero with skipped tests, or a build with new warnings, is
  3. Re-read the original request. Not your interpretation of it several steps ago — the actual
  4. Check for collateral damage. What else consumes what you changed? Did anything else move?
  5. Confirm nothing was left behind — debug statements, a skipped test, a TODO standing in for

What it can do on your machine

Read from SKILL.md and the folder at commit 98d1c17. 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

Completion Verification loads about 479 tokens when it runs. Until then it costs about 96 tokens; SKILL.md has 252 words of instructions outside code blocks.

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

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 cbrock84/headcount at commit 98d1c17, republished under its MIT licence (© cbrock84). 252 words, ~479 tokens.

Download SKILL.mdSave it as .claude/skills/completion-verification/SKILL.md (or your agent's skills folder).
name
completion-verification
description
Verifies that work is actually complete before it is claimed to be — running the checks, reading the output, and confirming the original request was satisfied rather than approximated. Use this before saying something is done, fixed, or passing; before committing or opening a pull request; and whenever a claim of success has not been backed by command output.

Completion verification

The gap between "should work" and "does work" is where most wasted cycles live. This closes it.

Before claiming done

  1. Run the real check, not a subset. The command the project gates on, on the current state of the tree.
  2. Read the output. An exit code of zero with skipped tests, or a build with new warnings, is not what it looks like at a glance.
  3. Re-read the original request. Not your interpretation of it several steps ago — the actual words. Confirm each part was addressed, and name any part that was not.
  4. Check for collateral damage. What else consumes what you changed? Did anything else move?
  5. Confirm nothing was left behind — debug statements, a skipped test, a TODO standing in for the hard case.

What a claim must carry

Say what you ran and what it said. "Tests pass" is an assertion; the command and its output is evidence. If you could not run something, say that explicitly rather than omitting it — an unstated gap reads as a covered one.

Honest incompleteness

Partial work reported accurately is useful. Partial work reported as complete costs someone else the time to discover otherwise, plus the trust. If a part is blocked, unverified, or deliberately skipped, name it in the same breath as the parts that are done.

Never

  • Claim a fix works without having reproduced the failure first.
  • Report success from a stale run.
  • Weaken, skip, or delete a failing test in order to claim green.

© cbrock84, 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 plugins/technology/skills/completion-verification of cbrock84/headcount.

Open the folder on GitHubat commit 98d1c17

Compare with similar skills

Completion Verification 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.

Completion Verification compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Completion Verification this skillcbrock84/headcount2k—~479Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Understand Diff AnalysisEgonex-AI/Understand-Anything86k1 repos~1.4kAutomated safety check: PassMIT
PR Design DocOpenHands/OpenHands90k—~2.4kAutomated safety check: PassMIT

Similar skills

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed

  • Understand Diff Analysis

    Egonex-AI/Understand-Anything

    Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.

    86k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed

  • PR Design Doc

    OpenHands/OpenHands

    For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…

    90k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed

  • WooCommerce Code Review

    woocommerce/woocommerce

    Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.

    11k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed

More from cbrock84/headcount

All 175 skills in this repo

  • Agent Hierarchy

    cbrock84/headcount

    Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a…

    2k GitHub stars~1.2k tokensUpdated 20 days ago
    Auto-check passed

  • Access And Identity

    cbrock84/headcount

    Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process.

    2k GitHub stars~1.1k tokensUpdated 20 days ago
    Auto-check passed

  • Account Based Marketing

    cbrock84/headcount

    Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group…

    2k GitHub stars~1.2k tokensUpdated 20 days ago
    Auto-check passed

  • Activation

    cbrock84/headcount

    Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account.

    2k GitHub stars~865 tokensUpdated 20 days ago
    Auto-check passed

  • AI Research Analyst

    cbrock84/headcount

    Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit.

    2k GitHub stars~916 tokensUpdated 20 days ago
    Auto-check passed

  • AI Search Optimization

    cbrock84/headcount

    Optimizes for AI assistants and AI-generated answers — being retrievable, being cited, and being represented accurately when a model answers on your behalf.

    2k GitHub stars~829 tokensUpdated 20 days ago
    Auto-check passed

Categories

Questions about Completion Verification

What does Completion Verification do?

Verifies that work is actually complete before it is claimed to be — running the checks, reading the output, and confirming the original request was satisfied rather than approximated. Completion Verification is an agent skill from cbrock84/headcount. Verifies that work is actually complete before it is claimed to be — running the checks, reading the output, and confirming the original request was satisfied rather than approximated.

When should I use Completion Verification?

Completion Verification fits situations like: tasks that involve Pull requests.

How do I install Completion Verification in Claude Code?

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

How do I install Completion Verification in Codex?

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

Can I use Completion Verification 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 cbrock84/headcount --skill completion-verification -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/completion-verification, .gemini/skills/completion-verification, .github/skills/completion-verification and .opencode/skills/completion-verification in your project.

What does Completion Verification need to run?

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

Does Completion Verification 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 Completion Verification 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 Completion Verification use?

Completion Verification 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 Completion Verification use?

About 479 tokens (SKILL.md is roughly 1.9k 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 Completion Verification?

Skills that share tags, products or a category with Completion Verification: Finishing a Development Branch (obra/superpowers, 296k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and Understand Diff Analysis (Egonex-AI/Understand-Anything, 86k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Completion Verification?

cbrock84 (a GitHub user) maintains it in cbrock84/headcount, which has 2,007 GitHub stars. The repository holds 175 skills in this directory. The repository was last updated on September 17, 2026.

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