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.
Thorough verification of completed work before declaring done
Install Verification Strategy
$ npx skills add vstorm-co/pydantic-deepagents --skill verification-strategy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install vstorm-co/pydantic-deepagents verification-strategy --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/vstorm-co/pydantic-deepagents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/apps/cli/skills/verification-strategy .claude/skills/verification-strategy && 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 "verification-strategy" agent skill from https://github.com/vstorm-co/pydantic-deepagents/tree/main/apps/cli/skills/verification-strategy into .claude/skills/verification-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verification-strategy", 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/vstorm-co/pydantic-deepagents/tree/main/apps/cli/skills/verification-strategyType 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 vstorm-co/pydantic-deepagents --skill verification-strategy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install vstorm-co/pydantic-deepagents verification-strategy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vstorm-co/pydantic-deepagents.git skills-src && mkdir -p .agents/skills && cp -r skills-src/apps/cli/skills/verification-strategy .agents/skills/verification-strategy && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "verification-strategy" agent skill from https://github.com/vstorm-co/pydantic-deepagents/tree/main/apps/cli/skills/verification-strategy into .agents/skills/verification-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verification-strategy", 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 vstorm-co/pydantic-deepagents --skill verification-strategy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install vstorm-co/pydantic-deepagents verification-strategy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vstorm-co/pydantic-deepagents.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/apps/cli/skills/verification-strategy .cursor/skills/verification-strategy && 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 "verification-strategy" agent skill from https://github.com/vstorm-co/pydantic-deepagents/tree/main/apps/cli/skills/verification-strategy into .cursor/skills/verification-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verification-strategy", 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/vstorm-co/pydantic-deepagents.git --path apps/cli/skills/verification-strategy--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 vstorm-co/pydantic-deepagents --skill verification-strategy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install vstorm-co/pydantic-deepagents verification-strategy --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vstorm-co/pydantic-deepagents.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/apps/cli/skills/verification-strategy .gemini/skills/verification-strategy && 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 "verification-strategy" agent skill from https://github.com/vstorm-co/pydantic-deepagents/tree/main/apps/cli/skills/verification-strategy into .gemini/skills/verification-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verification-strategy", 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 vstorm-co/pydantic-deepagents verification-strategyInstalls 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 vstorm-co/pydantic-deepagents --skill verification-strategy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/vstorm-co/pydantic-deepagents.git skills-src && mkdir -p .github/skills && cp -r skills-src/apps/cli/skills/verification-strategy .github/skills/verification-strategy && 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 "verification-strategy" agent skill from https://github.com/vstorm-co/pydantic-deepagents/tree/main/apps/cli/skills/verification-strategy into .github/skills/verification-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verification-strategy", 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 vstorm-co/pydantic-deepagents --skill verification-strategy -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install vstorm-co/pydantic-deepagents verification-strategy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vstorm-co/pydantic-deepagents.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/apps/cli/skills/verification-strategy .opencode/skills/verification-strategy && 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 "verification-strategy" agent skill from https://github.com/vstorm-co/pydantic-deepagents/tree/main/apps/cli/skills/verification-strategy into .opencode/skills/verification-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verification-strategy", 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
verification-strategy- GitHub stars
- 1.1k
- Token cost
- ~736 tokens
- SKILL.md length
- 376 words
- Files
- 1
- Skills in repo
- 14
- Repo updated
- First seen
- Licence
- MIT
At a glance
Thorough verification of completed work before declaring done
- Works in 6 steps: Re-read the original task → Check file outputs → Compile and run → …
- Agent Workflows work in your project
- SKILL.md covers The Verification Checklist, Reading Test Scripts, Common Verification Failures and Final Check
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Verification Strategy is an agent skill from vstorm-co/pydantic-deepagents. Thorough verification of completed work before declaring done
Its SKILL.md is about 740 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. The repository describes itself as: Open-source, self-hosted Claude Code - a terminal AI assistant and the Python framework behind it. Tool-calling, sandboxed execution, multi-agent teams, skills, checkpoints… The licence is MIT.
When your agent uses it
- Agent Workflows work in your project
Example prompts
- “/verification-strategy”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 650b592. 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 (its code samples are bash).
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 Strategy loads about 736 tokens when it runs. Until then it costs about 21 tokens; SKILL.md has 376 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 vstorm-co/pydantic-deepagents at commit 650b592, republished under its MIT licence (© vstorm-co). 376 words, ~736 tokens.
Download SKILL.mdSave it as
.claude/skills/verification-strategy/SKILL.md (or your agent's skills folder).- name
- verification-strategy
- description
- Thorough verification of completed work before declaring done
- tags
- testing, verification, benchmark
- version
- 1.0.0
Verification Strategy
How to verify your work is correct before declaring a task complete.
The Verification Checklist
After implementing a solution, go through ALL of these:
1. Re-read the original task
- Re-read the EXACT wording of the task instruction
- Check every requirement — file paths, names, formats, constraints
- Are there implicit requirements? ("compile with gcc -O3 -lm" means exact flags)
2. Check file outputs
- Do all required files exist at the exact paths specified?
- Are file sizes within any stated limits?
- Is the file format correct? (binary vs text, encoding, line endings)
ls -la /path/to/expected/output
wc -c /path/to/output # byte count
file /path/to/output # format detection
head -5 /path/to/output # content preview3. Compile and run
- Compile with the EXACT flags specified in the task
- Run with the EXACT command and arguments specified
- Check exit code:
echo $?(should be 0 for success) - Check both stdout AND stderr
4. Validate output
- Compare output against expected format
- Check exact field names, delimiters, number formatting
- If the task specifies output format, match it exactly:
- JSON: valid JSON? correct schema?
- CSV: correct headers? correct delimiter?
- Plain text: correct line endings? trailing newline?
5. Test edge cases
- Empty input (if applicable)
- The specific test inputs mentioned in the task
- Large inputs (if the task involves performance)
6. Check constraints
- Size limits (file size, code length)
- Time limits (does it finish in reasonable time?)
- Memory limits (does it stay within bounds?)
- No external dependencies that aren't available
Show full SKILL.md (156 more words)Show less
Reading Test Scripts
If you can find the test script, READ IT:
- What exact assertions does it make?
- What inputs does it use?
- What output format does it expect?
- What timeouts are set?
Tests often check things you didn't expect:
- Exact string matching (whitespace matters!)
- Specific numeric precision
- File permissions
- Process exit codes
Common Verification Failures
| What you think is right | What the test actually checks |
|---|---|
| Output on stdout | Output in a specific file |
| Human-readable numbers | Exact decimal precision |
| Relative file paths | Absolute file paths |
| "Close enough" answer | Exact match |
| Code that runs | Code under a specific size limit |
Final Check
Before declaring done, ask yourself:
- Did I create/modify ALL the files the task asks for?
- Did I use the EXACT paths, names, and formats specified?
- Does my code compile/run WITHOUT errors?
- Does my output match what automated tests would expect?
- Have I cleaned up any debug output or temporary files?
© vstorm-co, 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 apps/cli/skills/verification-strategy of vstorm-co/pydantic-deepagents.
Open the folder on GitHubat commit 650b592
Compare with similar skills
Verification Strategy 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 |
|---|---|---|---|---|---|---|
| Verification Strategy this skillvstorm-co/pydantic-deepagents | 1.1k | — | ~736 | Automated safety check: Pass | MIT | |
| MCP Server Builderanthropics/skills | 180k | 63 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Hook Development for Claude Code Pluginsanthropics/claude-plugins-official | 38k | 10 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 | 297k | 2 repos | ~5.1k | Automated safety check: Pass | MIT | |
| Skill CreatorAzure/azqr | 795 | 89 repos | ~8.2k | 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
Skill Creator
Azure/azqr
Create new skills, modify and improve existing skills, and measure skill performance.
- 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.
More from vstorm-co/pydantic-deepagents
All 14 skills in this repoData Formats
vstorm-co/pydantic-deepagents
Working with diverse data formats: binary, text, structured, and custom
Diagram Design
vstorm-co/pydantic-deepagents
Best practices for creating research diagrams with Excalidraw MCP tools
Research Methodology
vstorm-co/pydantic-deepagents
Best practices for systematic research, source evaluation, and evidence gathering
Systematic Debugging
vstorm-co/pydantic-deepagents
Systematic approach to diagnosing and fixing errors. An agent skill from vstorm-co/pydantic-deepagents.
Environment Discovery
vstorm-co/pydantic-deepagents
Systematic exploration of unknown environments before starting work
Skill Creator
vstorm-co/pydantic-deepagents
Create new reusable skills from conversation context. An agent skill from vstorm-co/pydantic-deepagents.
Related
Categories
Questions about Verification Strategy
What does Verification Strategy do?
Thorough verification of completed work before declaring done. Verification Strategy is an agent skill from vstorm-co/pydantic-deepagents.
When should I use Verification Strategy?
Verification Strategy fits situations like: agent Workflows work in your project.
How do I install Verification Strategy in Claude Code?
Run `npx skills add vstorm-co/pydantic-deepagents --skill verification-strategy -a claude-code`. Or copy the skill folder (apps/cli/skills/verification-strategy in vstorm-co/pydantic-deepagents) into .claude/skills/verification-strategy in your project. Claude Code loads it when a task matches its description.
How do I install Verification Strategy in Codex?
Run `npx skills add vstorm-co/pydantic-deepagents --skill verification-strategy -a codex`. Or copy the skill folder (apps/cli/skills/verification-strategy in vstorm-co/pydantic-deepagents) into .agents/skills/verification-strategy in your project. Codex loads it when a task matches its description.
Can I use Verification Strategy 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 vstorm-co/pydantic-deepagents --skill verification-strategy -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-strategy, .gemini/skills/verification-strategy, .github/skills/verification-strategy and .opencode/skills/verification-strategy in your project.
What does Verification Strategy need to run?
SKILL.md names no scripts, command-line tools or credentials: Verification Strategy is instructions for the agent only.
Does Verification Strategy 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 Strategy 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 Strategy use?
Verification Strategy 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 Strategy use?
About 736 tokens (SKILL.md is roughly 2.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 Verification Strategy?
Skills that share tags, products or a category with Verification Strategy: 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, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Verification Strategy?
vstorm-co (a GitHub organization) maintains it in vstorm-co/pydantic-deepagents, which has 1,077 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 6, 2026.
Source: vstorm-co/pydantic-deepagents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.