MCP Server Builder
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
A skill your agent uses when about to declare work complete, fixed, passing, or done
Install Skill Verification Gate
$ npx skills add nyldn/claude-octopus --skill skill-verification-gate -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install nyldn/claude-octopus skill-verification-gate --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/nyldn/claude-octopus.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/skill-verification-gate .claude/skills/skill-verification-gate && rm -rf skills-srcUse ~/.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/
Install the "skill-verification-gate" agent skill from https://github.com/nyldn/claude-octopus/tree/main/skills/skill-verification-gate into .claude/skills/skill-verification-gate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-verification-gate", 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 install https://github.com/nyldn/claude-octopus/tree/main/skills/skill-verification-gateType 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.
$ npx skills add nyldn/claude-octopus --skill skill-verification-gate -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install nyldn/claude-octopus skill-verification-gate --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nyldn/claude-octopus.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/skill-verification-gate .agents/skills/skill-verification-gate && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "skill-verification-gate" agent skill from https://github.com/nyldn/claude-octopus/tree/main/skills/skill-verification-gate into .agents/skills/skill-verification-gate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-verification-gate", 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.
$ npx skills add nyldn/claude-octopus --skill skill-verification-gate -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install nyldn/claude-octopus skill-verification-gate --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nyldn/claude-octopus.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/skill-verification-gate .cursor/skills/skill-verification-gate && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "skill-verification-gate" agent skill from https://github.com/nyldn/claude-octopus/tree/main/skills/skill-verification-gate into .cursor/skills/skill-verification-gate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-verification-gate", 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 https://github.com/nyldn/claude-octopus.git --path skills/skill-verification-gate--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add nyldn/claude-octopus --skill skill-verification-gate -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install nyldn/claude-octopus skill-verification-gate --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nyldn/claude-octopus.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/skill-verification-gate .gemini/skills/skill-verification-gate && rm -rf skills-srcUse ~/.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/
Install the "skill-verification-gate" agent skill from https://github.com/nyldn/claude-octopus/tree/main/skills/skill-verification-gate into .gemini/skills/skill-verification-gate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-verification-gate", 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.
$ gh skill install nyldn/claude-octopus skill-verification-gateInstalls 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).
$ npx skills add nyldn/claude-octopus --skill skill-verification-gate -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/nyldn/claude-octopus.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/skill-verification-gate .github/skills/skill-verification-gate && rm -rf skills-srcUse ~/.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/
Install the "skill-verification-gate" agent skill from https://github.com/nyldn/claude-octopus/tree/main/skills/skill-verification-gate into .github/skills/skill-verification-gate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-verification-gate", 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.
$ npx skills add nyldn/claude-octopus --skill skill-verification-gate -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install nyldn/claude-octopus skill-verification-gate --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nyldn/claude-octopus.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/skill-verification-gate .opencode/skills/skill-verification-gate && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "skill-verification-gate" agent skill from https://github.com/nyldn/claude-octopus/tree/main/skills/skill-verification-gate into .opencode/skills/skill-verification-gate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-verification-gate", 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
skill-verification-gate- GitHub stars
- 4.2k
- Used in
- 1 other repo
- Token cost
- ~1.4k tokens
- SKILL.md length
- 632 words
- Files
- 2
- Skills in repo
- 62
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when about to declare work complete, fixed, passing, or done
- Works in 5 steps: IDENTIFY — What command proves this claim? → RUN — Execute the full command (fresh,… → READ — Full output, check exit code,… → …
- About to declare work complete
- SKILL.md covers Portable feature evidence, The Iron Law, The Gate and Rationalization Table, plus 6 more sections
- Calls npm and git
What it does
Skill Verification Gate is an agent skill from nyldn/claude-octopus. Use when about to declare work complete, fixed, passing, or done
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: Run multiple AI models against the same research, design, or coding task. Surface disagreements before you ship. The licence is MIT.
When your agent uses it
- About to declare work complete
Example prompts
- “/skill-verification-gate”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- IDENTIFY — What command proves this claim?
- RUN — Execute the full command (fresh, not cached)
- READ — Full output, check exit code, count failures
- VERIFY — Does output actually confirm the claim?
- ONLY THEN — State the claim WITH evidence
What it can do on your machine
Read from SKILL.md and the folder at commit 4d152db. 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:
npmgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm and git, which can reach the network depending on how they are called.
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
Skill Verification Gate loads about 1.4k tokens when it runs. Until then it costs about 22 tokens; SKILL.md has 632 words of instructions outside code blocks.
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 nyldn/claude-octopus at commit 4d152db, republished under its MIT licence (© nyldn). 632 words, ~1,437 tokens.
Download SKILL.mdSave it as
.claude/skills/skill-verification-gate/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- skill-verification-gate
- description
- Use when about to declare work complete, fixed, passing, or done
- disable-model-invocation
- true
Host: Codex CLI — This skill was designed for Claude Code and adapted for Codex. Cross-reference commands use installed skill names in Codex rather than
/octo:*slash commands. Use the active Codex shell and subagent tools. Do not claim a provider, model, or host subagent is available until the current session exposes it. For host tool equivalents, seeskills/blocks/codex-host-adapter.md.
Verification Gate
Portable feature evidence
Load the selected feature's policy provenance and open-marker count through the existing boundary adapter. Cite the exact policy passage and conflicting plan action for any verified policy violation. Report unresolved decisions and which tasks depend on them. Stable task completion needs parent verification tied to the current task-contract digest; a checkbox, model claim or historical manifest alone cannot prove completion. Retain result-to-task mappings through correction, cancellation and resume.
The Iron Law
<HARD-GATE>
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
</HARD-GATE>If you haven't run the verification command in this turn, you cannot claim it passes.
The Gate
Before claiming any success or expressing satisfaction:
- IDENTIFY — What command proves this claim?
- RUN — Execute the full command (fresh, not cached)
- READ — Full output, check exit code, count failures
- VERIFY — Does output actually confirm the claim?
- ONLY THEN — State the claim WITH evidence
Skip any step = the claim is unverified.
Rationalization Table
| Excuse | Reality |
|---|---|
| "I ran the tests earlier this session" | Earlier is not fresh. Code changed since. Run again. |
| "The edit was trivial, it can't break anything" | Trivial edits break builds daily. The gate has no size exemption. |
| "The subagent reported success" | Agent reports are claims, not evidence. Verify independently. |
| "CI will catch it anyway" | CI is the safety net, not the verification. Verify before push. |
| "I'm confident this works" | Confidence is not evidence. Run the command. |
| "Running the full suite is slow" | Then run the targeted suite — but run something, fresh. |
What Counts as Evidence
| Claim | Requires | NOT Sufficient |
|---|---|---|
| Tests pass | Test command output showing 0 failures | Previous run, "should pass" |
| Build succeeds | Build command exit 0 | Linter passing |
| Bug fixed | Reproduce original symptom: now passes | "Code changed, should work" |
| Regression test works | Red (fail without fix) → Green (pass with fix) | Test passes once |
| Subagent completed task | git diff shows expected changes | Subagent says "done" |
| Requirements met | Line-by-line checklist against spec | Tests passing |
| Provider dispatch worked | Output contains expected content | No error ≠ success |
Show full SKILL.md (242 more words)Show less
Red Flags — STOP and Verify
If you catch yourself thinking any of these, STOP:
| Thought | What to do instead |
|---|---|
| "Should work now" | Run the verification |
| "I'm confident" | Confidence ≠ evidence |
| "Just this once" | No exceptions |
| "The linter passed" | Linter ≠ tests ≠ build |
| "The agent said it worked" | Verify independently |
| "It's a small change" | Small changes cause big bugs |
Multi-Provider Context
In Claude Octopus workflows, verification is especially critical because:
- Provider outputs can be hallucinated — Codex, Antigravity, Copilot, and other providers may claim success without evidence
- Consensus ≠ correctness — three models agreeing doesn't mean they're right
- Synthesis files may be stale — check timestamps, don't assume freshness
- orchestrate.sh exit code 0 ≠ quality — the script ran, but did it produce good output?
After any multi-provider workflow:
# Verify synthesis file exists and is recent
ls -la ~/.claude-octopus/results/*-synthesis-*.md | tail -1
# Verify it has content (not just headers)
wc -l ~/.claude-octopus/results/*-synthesis-*.md | tail -1When to Apply
ALWAYS before:
- Committing code
- Creating PRs
- Marking tasks complete
- Moving to next workflow phase
- Reporting results to user
- Claiming a bug is fixed
In orchestrate.sh workflows:
- After
probe(discover) — verify synthesis file exists - After
grasp(define) — verify consensus score meets threshold - After
tangle(develop) — verify tests pass, not just that code was written - After
ink(deliver) — verify review actually ran, not just that it was dispatched
Examples
Correct: Evidence-Based Claim
$ npm test
✓ user.create() saves to database (45ms)
✓ user.create() validates email (12ms)
Tests: 2 passed, 2 total
All 2 tests pass. ← Claim backed by output.Incorrect: Claim Without Evidence
I've implemented the feature. It should work now. The tests should pass.
← No test was run. "Should" is not evidence.Correct: Regression Test Red-Green
1. Write test → run → FAIL (expected, proves test detects the bug)
2. Implement fix → run → PASS (proves fix works)
3. Revert fix → run → FAIL (proves test isn't false-positive)
4. Restore fix → run → PASS (final confirmation)Integration with Other Skills
This skill is referenced by:
flow-develop.md— verification gate after implementationflow-deliver.md— verification gate before deliveryskill-code-review.md— verify review findings before reportingskill-tdd.md— red-green cycle requires evidence at each stepskill-factory.md— autonomous pipeline must verify at every phase
© nyldn, 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/skill-verification-gate of nyldn/claude-octopus.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 4d152db
Used in 1 other repository
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in nyldn/claude-octopus, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Skill Verification Gate 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Skill Verification Gate this skillnyldn/claude-octopus | 4.2k | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| MCP Server Builderanthropics/skills | 180k | 64 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Hook Development for Claude Code Pluginsanthropics/claude-plugins-official | 38k | 11 repos | ~4.1k | Automated safety check: Notes | Apache-2.0 | |
| Using Superpowersfarm-fe/farm | 5.6k | 35 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Executing Plans Inlineobra/superpowers | 296k | 2 repos | ~5.1k | Automated safety check: Pass | MIT | |
| Claude Code Agent Developmentanthropics/claude-plugins-official | 38k | 8 repos | ~2.8k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
- Official
Hook Development for Claude Code Plugins
anthropics/claude-plugins-official
Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.
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
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.
- Official
Claude Code Agent Development
anthropics/claude-plugins-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.
- Official
Skill Creator
Azure/azqr
Create new skills, modify and improve existing skills, and measure skill performance.
More from nyldn/claude-octopus
All 62 skills in this repoOctopus Quick
nyldn/claude-octopus
Quick execution for ad-hoc tasks without full workflow overhead — use for small, self-contained requests
Octopus Research
nyldn/claude-octopus
Thorough research across multiple sources — use for complex topics needing broad synthesis
Octopus Security Audit
nyldn/claude-octopus
OWASP compliance, vulnerability scanning, and adversarial red team testing — use for security reviews
Skill Audit
nyldn/claude-octopus
Audit codebases for quality, consistency, and broken patterns — use for pre-release or tech debt review
Skill Content Pipeline
nyldn/claude-octopus
Extract patterns and anatomy from URLs — use to reverse-engineer content strategies from live pages
Skill Context Detection
nyldn/claude-octopus
Auto-detect work context (Dev vs Knowledge) — use to tailor workflows based on current task type
Related
Categories
Questions about Skill Verification Gate
What does Skill Verification Gate do?
A skill your agent uses when about to declare work complete, fixed, passing, or done. Skill Verification Gate is an agent skill from nyldn/claude-octopus.
When should I use Skill Verification Gate?
Skill Verification Gate fits situations like: about to declare work complete.
How do I install Skill Verification Gate in Claude Code?
Run `npx skills add nyldn/claude-octopus --skill skill-verification-gate -a claude-code`. Or copy the skill folder (skills/skill-verification-gate in nyldn/claude-octopus) into .claude/skills/skill-verification-gate in your project. Claude Code loads it when a task matches its description.
How do I install Skill Verification Gate in Codex?
Run `npx skills add nyldn/claude-octopus --skill skill-verification-gate -a codex`. Or copy the skill folder (skills/skill-verification-gate in nyldn/claude-octopus) into .agents/skills/skill-verification-gate in your project. Codex loads it when a task matches its description.
Can I use Skill Verification Gate 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 nyldn/claude-octopus --skill skill-verification-gate -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/skill-verification-gate, .gemini/skills/skill-verification-gate, .github/skills/skill-verification-gate and .opencode/skills/skill-verification-gate in your project.
What does Skill Verification Gate need to run?
Going by SKILL.md and its folder, Skill Verification Gate needs the command-line tools its instructions call (npm and git).
Does Skill Verification Gate access the network?
SKILL.md contains no URLs. Its commands use npm and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Skill Verification Gate 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 Skill Verification Gate use?
Skill Verification Gate 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 Skill Verification Gate use?
About 1.4k tokens (SKILL.md is roughly 5.7k 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 Skill Verification Gate?
Skills that share tags, products or a category with Skill Verification Gate: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k 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 Skill Verification Gate?
nyldn (a GitHub user) maintains it in nyldn/claude-octopus, which has 4,182 GitHub stars. The repository holds 62 skills in this directory. The repository was last updated on October 7, 2026.
Source: nyldn/claude-octopus on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.