How do I install the Verify skill?

Run npx skillmds@latest add shawn-sandy/verify in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Verify skill do?

Runtime-verify a change to a published skill in this repo by driving its script as a CLI and running its SKILL.md steps as a fresh agent. Repo-local tooling, not a published skill. It is listed under AI & ML on SkillMD.

Is Verify safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Verify?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Verify free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Verify?

shawn-sandy (@shawn-sandy) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Verify by shawn-sandy — Agent Skill

Name: Verify
Rating: 4.2 (5 reviews)
Author: shawn-sandy

File contents

Verification here means running the skill, not running tests/validate-all.sh (CI does that).

Script surface

Skill scripts are stdlib Python with no build step. Drive them as a user would:

python3 skills/<name>/scripts/<script>.py --help
python3 skills/<name>/scripts/<script>.py <args>

Real session logs live under ~/.claude/projects/<cwd with non-alphanumerics replaced by ->*/. For deterministic runs, write a fixture .jsonl in the scratchpad: one JSON object per line with type (user or assistant), timestamp, and message.content as a list of blocks (text, tool_use with name and input, tool_result).

Gotchas seen: zsh expands a bare =word argument as a command lookup, so quote it ('=word'). Default log discovery resolves the main checkout through git, so a run from inside a worktree scans both the worktree's and the main checkout's log directories. Confirm the session count in the header line matches a run from the main checkout.

SKILL.md surface

Copy the skill into a throwaway project and run a fresh agent against it:

T=<scratchpad>/verify-agent; mkdir -p "$T/.claude/skills"; cp -R skills/<name> "$T/.claude/skills/"
cd "$T" && env -u CLAUDECODE -u CLAUDE_CODE_ENTRYPOINT claude -p "<ask it to run one step of the skill>" \
  --allowedTools "Skill,Read,Glob,Grep,Bash(python3 *),Bash(ls *)" --max-turns 12

Also run the SKILL.md's own shell commands verbatim inside a real target project and compare what they print with what the SKILL.md says to expect.

Frequently asked questions

Verify