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

by TechDufus in TechDufus/oh-my-claude

Evidence-based verification methodology before claiming work is complete.

MITAuto-check passed

Install Verification

skills CLI
$ npx skills add TechDufus/oh-my-claude --skill verification -a claude-code

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

GitHub CLI
$ gh skill install TechDufus/oh-my-claude 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/TechDufus/oh-my-claude.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/oh-my-claude/skills/verification .claude/skills/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
verification
GitHub stars
174
Token cost
~1.1k tokens
SKILL.md length
556 words
Files
1
Skills in repo
12
Repo updated
First seen
Licence
MIT

At a glance

Evidence-based verification methodology before claiming work is complete.

  • About to claim work is done
  • SKILL.md covers The Iron Law, When to Apply, Gate Function and Common Failures, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Before committing

What it does

Verification is an agent skill from TechDufus/oh-my-claude. Evidence-based verification methodology before claiming work is complete. Use when about to claim work is done, before committing, before creating PRs, or when verification-reminder hook fires. Triggers on: 'verify', 'verification', 'is it done', 'complete', 'ready to merge'.

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

The repository describes itself as: Add ultrawork to any prompt for maximum parallel execution. The licence is MIT.

When your agent uses it

  • About to claim work is done
  • Before committing
  • Before creating PRs
  • Verification-reminder hook fires

Example prompts

  • “verify”
  • “verification”
  • “is it done”
  • “/verification”

What it can do on your machine

Read from SKILL.md and the folder at commit ede75db. 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 loads about 1.1k tokens when it runs. Until then it costs about 72 tokens; SKILL.md has 556 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~72
When it runs · the whole SKILL.md, loaded when a task matches
~1.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 TechDufus/oh-my-claude at commit ede75db, republished under its MIT licence (© TechDufus). 556 words, ~1,085 tokens.

Download SKILL.mdSave it as .claude/skills/verification/SKILL.md (or your agent's skills folder).
name
verification
description
Evidence-based verification methodology before claiming work is complete. Use when about to claim work is done, before committing, before creating PRs, or when verification-reminder hook fires. Triggers on: 'verify', 'verification', 'is it done', 'complete', 'ready to merge'.

Verification Skill

No evidence, no completion claim. Period.

The Iron Law

NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE

"I think it works" is not evidence. "Tests passed 5 minutes ago" is not fresh. Run the checks NOW, read the output NOW, then claim completion.

When to Apply

  • About to say "done", "complete", or "ready"
  • Before committing or creating a PR
  • After agent teammates claim work is finished
  • When the verification_reminder hook fires
  • Before any handoff to another person or system

Gate Function

IDENTIFY

What needs verification? List every claim you're about to make.

  • Tests pass? Which test suite?
  • Build succeeds? Which build command?
  • Feature works? What specific behavior?
  • No regressions? What could have broken?
RUN

Execute the actual checks. Not "I think they pass" - run them NOW.

  • Run the test suite. Capture output.
  • Run the build. Capture output.
  • Run linters if applicable. Capture output.
READ

Read the output. Actually read it. Don't assume.

  • Check exit codes (0 = success, anything else = failure)
  • Look for warnings that might indicate issues
  • Count passing vs failing tests
  • Verify the output matches expectations
VERIFY

Does the output confirm success? Cross-reference against requirements.

  • Every requirement has corresponding evidence
  • No skipped tests that cover changed behavior
  • No warnings that indicate degraded functionality
CLAIM

Only now can you claim completion. Include the evidence.

Common Failures

ClaimRequiresNot Sufficient
"Tests pass"Fresh test run output"They passed before"
"Build succeeds"Actual build output"It should build"
"Feature works"Demonstrated behavior"I implemented it correctly"
"No regressions"Full test suite run"I only changed one file"
"PR is ready"All checks green"I think it's good"
"Bug is fixed"Reproduction test passes"I addressed the cause"

Anti-Rationalization Table

ExcuseCounter
"The agent said it works"Agents hallucinate. Read the actual output
"I'm confident it works"Confidence is not evidence. Run the check
"I just ran tests a minute ago"You changed code since then. Run again
"It's a trivial change"Trivial changes cause production incidents. Verify
"Tests take too long"Debugging takes longer. Run them
"I trust the subagent"Trust but verify. Verification is cheap, debugging is expensive
"The types check out"Types don't catch logic errors. Run the tests
"I'll verify after committing"Commits without verification = tech debt
Show full SKILL.md (186 more words)Show less

Red Flags

Thoughts that signal you're about to skip verification:

  • "This obviously works, I don't need to check"
  • "The agent already verified this"
  • "I'll just commit and fix anything CI catches"
  • "It's the same as last time, it'll be fine"
  • "I only changed one line"
  • "Running tests again would be redundant"

If you catch yourself thinking any of these: STOP. Run the verification.

Hook Integration

The verification_reminder hook reminds you to verify after agent tasks complete. This skill enforces the methodology. The hook fires, you see the reminder, invoke this skill for the systematic verification process.

Flow: Agent completes work -> Hook reminds you -> IDENTIFY what to check -> RUN the checks -> READ output -> VERIFY against requirements -> CLAIM only with evidence.

Verification Checklist

Use this before any completion claim:

  • All changed files saved
  • Test suite run AFTER last code change
  • Test output actually read (not assumed)
  • Build passes (if applicable)
  • Linting passes (if applicable)
  • Requirements cross-referenced against implementation
  • Edge cases from requirements are covered
  • No TODO/FIXME left in changed code (unless intentional)

The Bottom Line

Evidence or it didn't happen. Run the check, read the output, then speak.

© TechDufus, 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/oh-my-claude/skills/verification of TechDufus/oh-my-claude.

Open the folder on GitHubat commit ede75db

Compare with similar skills

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.

Verification compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Verification this skillTechDufus/oh-my-claude174—~1.1kAutomated safety check: PassMIT
Claimsruvnet/ruflo74k2 repos~1.1kAutomated safety check: PassMIT
Benchmark Methodologyaffaan-m/ECC275k1 repos~2.5kAutomated safety check: PassMIT
Evaluation Methodologywshobson/agents40k—~2kAutomated safety check: PassMIT
Sparc Methodologyruvnet/ruflo74k—~262Automated safety check: PassMIT
Bb Methodologysickn33/agentic-awesome-skills47k1 repos~5.4kAutomated safety check: PassMIT

Similar skills

  • Claims

    ruvnet/ruflo

    Claims-based authorization for agents and operations. An agent skill from ruvnet/ruflo.

    74k GitHub starsUsed in 2 repos~1.1k tokens
    Backend & APIsAuto-check passed

  • Benchmark Methodology

    affaan-m/ECC

    Score a scoped competitor set into comparable profile cards: nine weighted dimensions (positioning, voice, visual craft, offer packaging, evidence, enterprise-readiness, thought leadership, pricing…

    275k GitHub starsUsed in 1 repo~2.5k tokens
    EducationAuto-check passed

  • Evaluation Methodology

    wshobson/agents

    PluginEval quality methodology, covering dimensions, rubrics, and scoring formulas.

    40k GitHub stars~2k tokensUpdated 3 days ago
    EducationAuto-check passed

  • Sparc Methodology

    ruvnet/ruflo

    SPARC development workflow (Specification, Pseudocode, Architecture, Refinement, Completion).

    74k GitHub stars~262 tokensUpdated today
    Auto-check passed

  • Bb Methodology

    sickn33/agentic-awesome-skills

    Use at the START of any bug bounty hunting session, when switching targets, or when feeling lost about what to do next.

    47k GitHub starsUsed in 1 repo~5.4k tokens
    SecurityAuto-check passed

  • Methodology

    hashgraph-online/awesome-codex-plugins

    Core Cavekit methodology — the master skill that teaches the Hunt lifecycle and routes to all sub-skills.

    1.2k GitHub stars~3.4k tokensUpdated today
    DevOps & CloudAuto-check passed

More from TechDufus/oh-my-claude

All 12 skills in this repo

  • Debugger

    TechDufus/oh-my-claude

    Systematic debugging methodology for diagnosing failures and root cause analysis.

    174 GitHub stars~1k tokensUpdated 2 mo ago
    Auto-check passed

  • Oh My Claude Runtime

    TechDufus/oh-my-claude

    A skill your agent uses when applying oh-my-claude workflow guidance, ultrawork modes, agent orchestration, plan execution, or plugin configuration.

    174 GitHub stars~4.3k tokensUpdated 2 mo ago
    Auto-check passed

  • PR Creation

    TechDufus/oh-my-claude

    MUST be used when creating pull requests. An agent skill from TechDufus/oh-my-claude.

    174 GitHub stars~1.8k tokensUpdated 2 mo ago
    Auto-check passed

  • Ralph Loop Init

    TechDufus/oh-my-claude

    Transform approved plans into ralph loop infrastructure. An agent skill from TechDufus/oh-my-claude.

    174 GitHub stars~4.6k tokensUpdated 2 mo ago
    Auto-check: notes

  • Ralph Plan

    TechDufus/oh-my-claude

    Structured PRD generation with interview, research, and approval workflow.

    174 GitHub stars~2.4k tokensUpdated 2 mo ago
    Auto-check: notes

  • Writing Skills

    TechDufus/oh-my-claude

    Methodology for creating effective skills using TDD principles.

    174 GitHub stars~1.3k tokensUpdated 2 mo ago
    Auto-check passed

Questions about Verification

What does Verification do?

Evidence-based verification methodology before claiming work is complete. Verification is an agent skill from TechDufus/oh-my-claude. Evidence-based verification methodology before claiming work is complete.

When should I use Verification?

Verification fits situations like: about to claim work is done; before committing; before creating PRs; verification-reminder hook fires.

How do I install Verification in Claude Code?

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

How do I install Verification in Codex?

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

Can I use 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 TechDufus/oh-my-claude --skill 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/verification, .gemini/skills/verification, .github/skills/verification and .opencode/skills/verification in your project.

What does Verification need to run?

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

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

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

About 1.1k tokens (SKILL.md is roughly 4.3k 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?

Skills that share tags, products or a category with Verification: Claims (ruvnet/ruflo, 74k stars), Benchmark Methodology (affaan-m/ECC, 275k stars), Evaluation Methodology (wshobson/agents, 40k stars) and Sparc Methodology (ruvnet/ruflo, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Verification?

TechDufus (a GitHub user) maintains it in TechDufus/oh-my-claude, which has 174 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on July 13, 2026.

Source: TechDufus/oh-my-claude on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.