Agent skill

Omk Verification

Evidence before claims — run verification commands before any completion/success statement.

Install Omk Verification

skills CLI

$ npx skills add KaimingWan/oh-my-kiro --skill omk-verification -a claude-code

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

GitHub CLI

$ gh skill install KaimingWan/oh-my-kiro omk-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/KaimingWan/oh-my-kiro.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/omk-verification .claude/skills/omk-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/

Paste into Claude Code

Install the "omk-verification" agent skill from https://github.com/KaimingWan/oh-my-kiro/tree/main/skills/omk-verification into .claude/skills/omk-verification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omk-verification", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/KaimingWan/oh-my-kiro/tree/main/skills/omk-verification

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add KaimingWan/oh-my-kiro --skill omk-verification -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install KaimingWan/oh-my-kiro omk-verification --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/KaimingWan/oh-my-kiro.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/omk-verification .agents/skills/omk-verification && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "omk-verification" agent skill from https://github.com/KaimingWan/oh-my-kiro/tree/main/skills/omk-verification into .agents/skills/omk-verification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omk-verification", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add KaimingWan/oh-my-kiro --skill omk-verification -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install KaimingWan/oh-my-kiro omk-verification --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/KaimingWan/oh-my-kiro.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/omk-verification .cursor/skills/omk-verification && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "omk-verification" agent skill from https://github.com/KaimingWan/oh-my-kiro/tree/main/skills/omk-verification into .cursor/skills/omk-verification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omk-verification", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/KaimingWan/oh-my-kiro.git --path skills/omk-verification

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add KaimingWan/oh-my-kiro --skill omk-verification -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install KaimingWan/oh-my-kiro omk-verification --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/KaimingWan/oh-my-kiro.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/omk-verification .gemini/skills/omk-verification && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "omk-verification" agent skill from https://github.com/KaimingWan/oh-my-kiro/tree/main/skills/omk-verification into .gemini/skills/omk-verification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omk-verification", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install KaimingWan/oh-my-kiro omk-verification

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add KaimingWan/oh-my-kiro --skill omk-verification -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/KaimingWan/oh-my-kiro.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/omk-verification .github/skills/omk-verification && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "omk-verification" agent skill from https://github.com/KaimingWan/oh-my-kiro/tree/main/skills/omk-verification into .github/skills/omk-verification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omk-verification", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add KaimingWan/oh-my-kiro --skill omk-verification -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install KaimingWan/oh-my-kiro omk-verification --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/KaimingWan/oh-my-kiro.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/omk-verification .opencode/skills/omk-verification && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "omk-verification" agent skill from https://github.com/KaimingWan/oh-my-kiro/tree/main/skills/omk-verification into .opencode/skills/omk-verification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omk-verification", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: omk-verification
GitHub stars: 107
Token cost: ~1.1k tokens
SKILL.md length: 367 words
Files: 1
Skills in repo: 15
Repo updated: Apr 2, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Evidence before claims — run verification commands before any completion/success statement.

About to claim done
SKILL.md covers Trigger Examples, Overview, The Iron Law and The Gate Function, plus 7 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
Before committing

What it does

Omk Verification is an agent skill from KaimingWan/oh-my-kiro. Evidence before claims — run verification commands before any completion/success statement. Trigger when about to claim 'done', 'fixed', 'passing', 'complete', 'works now', before committing, creating PRs, or moving to next task. Also trigger when expressing satisfaction like 'great', 'perfect', or any positive assessment of work state without fresh evidence.

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.

It sits in Agent Workflows, covering Verification before completion. The licence is MIT.

When your agent uses it

About to claim done
Before committing
Moving to next task
Expressing satisfaction like great

Example prompts

“passing”
“complete”
“works now”
“/omk-verification”

What it can do on your machine

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

Omk Verification loads about 1.1k tokens when it runs. Until then it costs about 95 tokens; SKILL.md has 367 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~95
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 KaimingWan/oh-my-kiro at commit ba228be, republished under its MIT licence (© KaimingWan). 367 words, ~1,109 tokens.

Download SKILL.mdSave it as .claude/skills/omk-verification/SKILL.md (or your agent's skills folder).

name: omk-verification
description: Evidence before claims — run verification commands before any completion/success statement. Trigger when about to claim 'done', 'fixed', 'passing', 'complete', 'works now', before committing, creating PRs, or moving to next task. Also trigger when expressing satisfaction like 'great', 'perfect', or any positive assessment of work state without fresh evidence.

Trigger Examples

"我觉得改好了" → 先跑验证
"tests should pass now" → 先跑验证
"准备提 PR 了" → 先跑验证
"this fix looks correct" → 先跑验证
"done, moving to next task" → 先跑验证

Verification Before Completion

Overview

Claiming work is complete without verification is dishonesty, not efficiency.

Core principle: Evidence before claims, always.

Violating the letter of this rule is violating the spirit of this rule.

The Iron Law

NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE

If you haven't run the verification command in this message, you cannot claim it passes.

The Gate Function

BEFORE claiming any status or expressing satisfaction:

1. IDENTIFY: What command proves this claim?
2. RUN: Execute the FULL command (fresh, complete)
3. READ: Full output, check exit code, count failures
4. VERIFY: Does output confirm the claim?
   - If NO: State actual status with evidence
   - If YES: State claim WITH evidence
5. ONLY THEN: Make the claim

Skip any step = lying, not verifying

Common Failures

Claim	Requires	Not Sufficient
Tests pass	Test command output: 0 failures	Previous run, "should pass"
Linter clean	Linter output: 0 errors	Partial check, extrapolation
Build succeeds	Build command: exit 0	Linter passing, logs look good
Bug fixed	Test original symptom: passes	Code changed, assumed fixed
Regression test works	Red-green cycle verified	Test passes once
Agent completed	VCS diff shows changes	Agent reports "success"
Requirements met	Line-by-line checklist	Tests passing

Red Flags - STOP

Using "should", "probably", "seems to"
Expressing satisfaction before verification ("Great!", "Perfect!", "Done!", etc.)
About to commit/push/PR without verification
Trusting agent success reports
Relying on partial verification
Thinking "just this once"
Tired and wanting work over
ANY wording implying success without having run verification

Rationalization Prevention

Excuse	Reality
"Should work now"	RUN the verification
"I'm confident"	Confidence ≠ evidence
"Just this once"	No exceptions
"Linter passed"	Linter ≠ compiler
"Agent said success"	Verify independently
"I'm tired"	Exhaustion ≠ excuse
"Partial check is enough"	Partial proves nothing
"Different words so rule doesn't apply"	Spirit over letter

Show full SKILL.md (124 more words)Show less

Key Patterns

Tests:

✅ [Run test command] [See: 34/34 pass] "All tests pass"
❌ "Should pass now" / "Looks correct"

Regression tests (TDD Red-Green):

✅ Write → Run (pass) → Revert fix → Run (MUST FAIL) → Restore → Run (pass)
❌ "I've written a regression test" (without red-green verification)

Build:

✅ [Run build] [See: exit 0] "Build passes"
❌ "Linter passed" (linter doesn't check compilation)

Requirements:

✅ Re-read plan → Create checklist → Verify each → Report gaps or completion
❌ "Tests pass, phase complete"

Agent delegation:

✅ Agent reports success → Check VCS diff → Verify changes → Report actual state
❌ Trust agent report

Why This Matters

From 24 failure memories:

your human partner said "I don't believe you" - trust broken
Undefined functions shipped - would crash
Missing requirements shipped - incomplete features
Time wasted on false completion → redirect → rework
Violates: "Honesty is a core value. If you lie, you'll be replaced."

When To Apply

ALWAYS before:

ANY variation of success/completion claims
ANY expression of satisfaction
ANY positive statement about work state
Committing, PR creation, task completion
Moving to next task
Delegating to agents

Rule applies to:

Exact phrases
Paraphrases and synonyms
Implications of success
ANY communication suggesting completion/correctness

The Bottom Line

No shortcuts for verification.

Run the command. Read the output. THEN claim the result.

This is non-negotiable.

Files

Just SKILL.md in skills/omk-verification of KaimingWan/oh-my-kiro.

Open the folder on GitHubat commit ba228be

Compare with similar skills

Omk 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.

Omk Verification compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Omk Verification this skillKaimingWan/oh-my-kiro	107	—	~1.1k	Automated safety check: Pass	MIT	6 mo ago
Show Me Your Work Decision Logcursor/plugins	10k	8 repos	~1.6k	Automated safety check: Pass	None	yesterday
Scope Creep Guardlennney/stop-that-shit	2.5k	1 repos	~2k	Automated safety check: Pass	MIT	2 days ago
Verification Before Completionfarm-fe/farm	5.6k	46 repos	~1k	Automated safety check: Pass	MIT	17 days ago
PUA High-Agency Governancetanweai/pua	20k	—	~502	Automated safety check: Pass	MIT	1 mo ago
Incremental Implementationaddyosmani/agent-skills	103k	1 repos	~2.3k	Automated safety check: Pass	MIT	6 days ago

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 8 repos~1.6k 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
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 1 mo ago
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 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 stars~1.1k tokensUpdated 1 mo ago
Agent WorkflowsAuto-check passed

Questions about Omk Verification

What does Omk Verification do?

Evidence before claims — run verification commands before any completion/success statement. Omk Verification is an agent skill from KaimingWan/oh-my-kiro. Evidence before claims — run verification commands before any completion/success statement.

When should I use Omk Verification?

Omk Verification fits situations like: about to claim done; before committing; moving to next task; expressing satisfaction like great.

How do I install Omk Verification in Claude Code?

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

How do I install Omk Verification in Codex?

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

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

What does Omk Verification need to run?

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

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

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

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

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

Who maintains Omk Verification?

KaimingWan (a GitHub user) maintains it in KaimingWan/oh-my-kiro, which has 107 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on April 2, 2026.

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

Install Omk Verification

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Trigger Examples

Verification Before Completion

Overview

The Iron Law

The Gate Function

Common Failures

Red Flags - STOP

Rationalization Prevention

Key Patterns

Why This Matters

When To Apply

The Bottom Line

Files

Compare with similar skills

Similar skills

More from KaimingWan/oh-my-kiro

Related

Questions about Omk Verification