New: 97,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

Verify

by automagik-dev in automagik-dev/genie

Prove a completion claim with fresh evidence before making it — the gate's exit code, the real diff, the remote's checks, the reviewer's verdict.

MITAuto-check passedAgent Workflows

Install Verify

skills CLI
$ npx skills add automagik-dev/genie --skill verify -a claude-code

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

GitHub CLI
$ gh skill install automagik-dev/genie verify --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/automagik-dev/genie.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/verify .claude/skills/verify && 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
verify
GitHub stars
345
Token cost
~1.4k tokens
SKILL.md length
869 words
Files
2
Skills in repo
19
Repo updated
First seen
Licence
MIT

At a glance

Prove a completion claim with fresh evidence before making it — the gate's exit code, the real diff, the remote's checks, the reviewer's verdict.

  • Works in 4 steps: Identify the one command whose output… → Run it fresh and in full. A narrowed… → Read the whole output and the exit code,… → …
  • Agent Workflows work in your project
  • SKILL.md covers The rule, The gate function, What proves what and Before a check counts, plus 3 more sections
  • Calls git

What it does

Verify is an agent skill from automagik-dev/genie. Prove a completion claim with fresh evidence before making it — the gate's exit code, the real diff, the remote's checks, the reviewer's verdict.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Agent Workflows. The repository describes itself as: Wishes in, PRs out. CLI agent that interviews you, plans the work, dispatches parallel agents in isolated worktrees, and reviews code before you see it. The licence is MIT.

When your agent uses it

  • Agent Workflows work in your project

Example prompts

  • “s exit code, the real diff, the remote”
  • “/verify”

Workflow steps

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

  1. Identify the one command whose output proves this exact claim.
  2. Run it fresh and in full. A narrowed re-run proves only the narrowed scope.
  3. Read the whole output and the exit code, and count the failures rather than scanning for the word "pass".
  4. Decide. If the output confirms the claim, state the claim with the evidence beside it. If it does not, state the actual status with the…

What it can do on your machine

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

    Shell commands in SKILL.md call:

    • git

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

  • Network

    Links to these hosts (documentation or services it may open):

    • github.com

    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

Verify loads about 1.4k tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 869 words of instructions outside code blocks.

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

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 automagik-dev/genie at commit c4f8788, republished under its MIT licence (© automagik-dev). 869 words, ~1,391 tokens.

Download SKILL.mdSave it as .claude/skills/verify/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
verify
description
Prove a completion claim with fresh evidence before making it — the gate's exit code, the real diff, the remote's checks, the reviewer's verdict.
category
verification
mutates
none

Verify

Evidence before claims, always. This skill runs commands and reads their output; it changes nothing, so a failure it finds routes to fix, never to a quiet repair here. Reading a write back is still reading: the write belonged to whoever was authorized to make it, and this skill never originates one.

The rule

A claim you have not verified in this turn is not a claim, it is a hope. If the command that would prove it has not run since the last change, the honest report is the actual state plus what is still unproven.

Violating the letter of the rule violates its spirit: a paraphrase, an implication, or an expression of satisfaction is a completion claim too.

The gate function

Before any statement that work is done, correct, or passing:

  1. Identify the one command whose output proves this exact claim.
  2. Run it fresh and in full. A narrowed re-run proves only the narrowed scope.
  3. Read the whole output and the exit code, and count the failures rather than scanning for the word "pass".
  4. Decide. If the output confirms the claim, state the claim with the evidence beside it. If it does not, state the actual status with the same evidence.

Skipping a step is not a faster verification, it is a different activity.

What proves what

ClaimProofNot proof
The repository is greenthe repository's own aggregate gate, its current stage chain read from the manifest rather than recalled, run whole and exiting zero in this turna previous run, a passing subset, "should pass"
Types are cleanthe typecheck stage inside that gatethe linter passing
A test suite passesthe suite's own output with a failure count of zeroone file re-run, a cached result
A bug is fixedthe original symptom re-exercised and now passingthe code changed and the reasoning looks right
A mutation landedthe stored state read back afterwards through a different path than the write tookthe writing call's own success return, or a response that echoes what was sent
Text sent through a CLI arrived intactthe stored body read back from the system that received it and compared against the source textthe exit code, or a receipt that counts bytes accepted
A regression test worksit fails with the fix reverted and passes with it restoredit passes once
A worker did the workgit status and git diff over the owned scopethe worker's success report
A branch is mergeablethe remote's checks read back from the pull requesta local gate alone
A group is shippablea reviewer's returned verdict of SHIPFIX-FIRST treated as "close enough", or your own read of your own work
Requirements are meteach wish criterion walked one by one against evidencethe gate being green
Show full SKILL.md (407 more words)Show less

Before a check counts

A check nobody has watched fail is machinery, not evidence. Look for the record of it failing — the implementor's red run from before the change, or a run against a throwaway copy with the guarded condition broken, never the candidate itself — and confirm the failure message names that condition rather than a typo, an unresolved import, or a selection that matched nothing. With no such record, the check is cited as unproven. Ask the same question of every check you cite: what would it say against a target that never existed, or one it could not reach? A check that passes when the thing it guards is absent or unreachable is fail-open — an empty read-back treated as clean, a suite that skipped, a probe that reads "not found" as success — and it proves nothing about the claim it was offered for.

On a gate that was already failing before the change, a raw failure count decides nothing. Take the failing set on the base you started from, take the failing set now, and claim only what the comparison supports: which failures are new and yours, and which were already there and are still there. The claim of no regression needs an empty new-failure set, stated beside the pre-existing ones by name.

Delegated work

A report from another agent is a pointer to evidence, not the evidence. Read the diff it claims to have produced and re-run the gate on the merged result. An agent that reports success having written nothing is the failure this row exists to catch.

Review verdicts are the same shape. SHIP is the only verdict that permits a completion claim. FIX-FIRST names gaps that must close and be re-reviewed; BLOCKED means the route changed and the claim is not available at all. Relay the verdict you received, never a softened version of it.

Red flags

Reach for this skill the moment you notice "should", "probably", or "seems to"; satisfaction arriving before output; a commit, push, or pull request forming without a fresh gate; exhaustion arguing that the remaining check is a formality. Each of those is the same event: the claim is running ahead of the proof.

Report

State the command, its exit status, and the claim it supports, in that order. Where expected evidence could not be captured, say which and why rather than leaving the gap silent.

<!-- adapted from https://github.com/obra/superpowers/tree/main/skills/verification-before-completion (MIT, commit b36e0829c6d0140e93cfef2ca599b1b07d4a7797 via dennisrongo/dsh-plugins vendor snapshot) -->

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

Files

SKILL.md and 1 other file in skills/verify of automagik-dev/genie.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit c4f8788

Compare with similar skills

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

Verify compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Verify this skillautomagik-dev/genie345—~1.4kAutomated safety check: PassMIT
MCP Server Builderanthropics/skills180k62 repos~2.3kAutomated safety check: PassApache-2.0
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official37k11 repos~4.1kAutomated safety check: NotesApache-2.0
Using Superpowersfarm-fe/farm5.6k34 repos~1.4kAutomated safety check: PassMIT
Executing Plans Inlineobra/superpowers296k2 repos~5.1kAutomated safety check: PassMIT
Claude Code Agent Developmentanthropics/claude-plugins-official37k8 repos~2.8kAutomated safety check: PassApache-2.0

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 62 repos~2.3k tokens
    Agent WorkflowsAuto-check passed

  • Hook Development for Claude Code Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.

    37k GitHub starsUsed in 11 repos~4.1k tokens
    Agent WorkflowsAuto-check: notes

  • Using Superpowers

    farm-fe/farm

    A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

    5.6k GitHub starsUsed in 34 repos~1.4k tokens
    Agent WorkflowsAuto-check passed

  • Executing Plans Inline

    obra/superpowers

    Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.

    296k GitHub starsUsed in 2 repos~5.1k tokens
    Agent WorkflowsAuto-check passed

  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    37k GitHub starsUsed in 8 repos~2.8k tokens
    Agent WorkflowsAuto-check passed

  • Skill Creator

    Azure/azqr

    Official

    Create new skills, modify and improve existing skills, and measure skill performance.

    794 GitHub starsUsed in 89 repos~8.2k tokens
    Agent WorkflowsAuto-check passed

More from automagik-dev/genie

All 19 skills in this repo

  • Learn

    automagik-dev/genie

    Diagnose and fix agent behavioral surfaces when the user corrects a mistake — connects to Claude native memory.

    345 GitHub stars~720 tokensUpdated today
    Auto-check passed

  • Brainstorm

    automagik-dev/genie

    Explore an ambiguous idea with the user, settle scope and success criteria, and produce an independently reviewed design for wish.

    345 GitHub stars~2k tokensUpdated today
    Auto-check passed

  • Report

    automagik-dev/genie

    Investigate a failure to its root cause with grounded evidence, hand the diagnosis to fix, and create a GitHub issue only when asked.

    345 GitHub stars~2k tokensUpdated today
    Auto-check passed

  • Wish

    automagik-dev/genie

    Deliver one decided task end to end — admit it, work it in one worktree, gate, independent review, bounded repair, a merge-ready PR — or plan a multi-group wish when it is bigger than one task.

    345 GitHub stars~3.7k tokensUpdated today
    Auto-check passed

  • Work

    automagik-dev/genie

    Execute an approved wish in dependency order with scoped workers, independent review, bounded repairs, and verified completion.

    345 GitHub stars~2.5k tokensUpdated today
    Auto-check passed

  • Authoring

    automagik-dev/genie

    Write or revise a Genie skill so it survives the shipped contract — frontmatter, house size, starter card, and runtime-neutral voice.

    345 GitHub stars~1k tokensUpdated today
    Auto-check passed

Categories

Questions about Verify

What does Verify do?

Prove a completion claim with fresh evidence before making it — the gate's exit code, the real diff, the remote's checks, the reviewer's verdict. Verify is an agent skill from automagik-dev/genie. Prove a completion claim with fresh evidence before making it — the gate's exit code, the real diff, the remote's checks, the reviewer's verdict.

When should I use Verify?

Verify fits situations like: agent Workflows work in your project.

How do I install Verify in Claude Code?

Run `npx skills add automagik-dev/genie --skill verify -a claude-code`. Or copy the skill folder (skills/verify in automagik-dev/genie) into .claude/skills/verify in your project. Claude Code loads it when a task matches its description.

How do I install Verify in Codex?

Run `npx skills add automagik-dev/genie --skill verify -a codex`. Or copy the skill folder (skills/verify in automagik-dev/genie) into .agents/skills/verify in your project. Codex loads it when a task matches its description.

Can I use Verify 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 automagik-dev/genie --skill verify -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verify, .gemini/skills/verify, .github/skills/verify and .opencode/skills/verify in your project.

What does Verify need to run?

Going by SKILL.md and its folder, Verify needs the command-line tools its instructions call (git).

Does Verify access the network?

SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.

Is Verify 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 Verify use?

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

About 1.4k tokens (SKILL.md is roughly 5.6k 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 Verify?

Skills that share tags, products or a category with Verify: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 37k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 296k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Verify?

automagik-dev (a GitHub organization) maintains it in automagik-dev/genie, which has 345 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 7, 2026.

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