How do I install the Verify skill?

Run npx skillmds@latest add promptpartner/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.

Is Verify safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: reads secrets. 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?

PromptPartner (@promptpartner) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Verify by promptpartner — Agent Skill

Name: Verify
Rating: 4.2 (5 reviews)
Author: PromptPartner

Verify

Answer "is this shippable / done?" with evidence before a commit or PR — fires on "verify", "is this done", "ready to ship?", pre-commit or pre-PR. Part of the Agentsmith harness; runs the project's verify phases and never claims "passing" without showing the output (R5).

PromptPartner Updated Sep 22, 2026

File contents

Verify — evidence before "done"

"Verified" is not a feeling; it's output you can point at. Never claim passing without showing it (R5 + verification-before-completion).

When this fires

"verify" / "is this done / shippable / ready to merge?" / just before a commit or PR.

Runtime neutrality

The verification runner and evidence standard are client-neutral. Never infer the active agent from this skill's install path: portable canonical content may be copied into a required client adapter such as .claude/skills. Use canonical AGENTS.md when an instruction is relevant.

Fast path — if the Agentsmith CLI is available

Run agentsmith verify (or the installed-project shim .agentsmith/agentsmith verify on macOS/Linux and .agentsmith\\agentsmith.cmd verify on Windows). It runs every phase in .harness/verify.conf and stops at the first failure). --list shows the phases; --only <tag> iterates just one. Add --record <directory> --tree-class <clean-clone|disposable-fixture|linked-worktree|operator-worktree> when deterministic command evidence needs a durable local receipt. The explicit class keeps a dirty operator tree from masquerading as clean-checkout evidence; clean-clone refuses a dirty tree. The destination must be new; relative paths resolve from the project target. Record mode redacts secret-shaped console and sidecar output before either is emitted.
On a failure: read the label + command it printed, explain in plain language what broke, and point at that phase's line in .harness/verify.conf to fix or refine.
Report the actual pass/fail output — not a summary of intent.

The v1 receipt covers deterministic commands only. Keep screenshots, videos, manual assertions, published results, and real runtime or visual checks as separately referenced artifacts. A green receipt does not satisfy an end-to-end gate that requires those observations.

Fallback — no runner or no conf

Say so plainly, and look at .harness/verify.conf.example for the intended phases.
Run the obvious checks for this project directly and show their output: build, test, lint, link/render check, a dry-run. For non-code work, "verify" = open the artifact and confirm it renders / the numbers reconcile / the links resolve.
If nothing is wired yet, propose the phases this project needs and offer to write .harness/verify.conf — but still run the checks by hand this time.

Report

State each check and its evidence: "build ok, 42 tests green, lint clean" — with the output, not "should pass". Anything skipped is "deferred: reason", never silence.

---name: verifydescription: Answer "is this shippable / done?" with evidence before a commit or PR — fires on "verify", "is this done", "ready to ship?", pre-commit or pre-PR. Part of the Agentsmith harness; runs the project's verify phases and never claims "passing" without showing the output (R5).---# Verify — evidence before "done""Verified" is not a feeling; it's output you can point at. Never claim passing without showing it(R5 + verification-before-completion).## When this fires"verify" / "is this done / shippable / ready to merge?" / just before a commit or PR.## Runtime neutralityThe verification runner and evidence standard are client-neutral. Never infer the active agentfrom this skill's install path: portable canonical content may be copied into a required clientadapter such as `.claude/skills`. Use canonical `AGENTS.md` when an instruction is relevant.## Fast path — if the Agentsmith CLI is available1. Run `agentsmith verify` (or the installed-project shim `.agentsmith/agentsmith verify` on macOS/Linux and `.agentsmith\\agentsmith.cmd verify` on Windows). It runs every phase in `.harness/verify.conf` and stops at the first failure). `--list` shows the phases; `--only <tag>` iterates just one. Add `--record <directory> --tree-class <clean-clone|disposable-fixture|linked-worktree|operator-worktree>` when deterministic command evidence needs a durable local receipt. The explicit class keeps a dirty operator tree from masquerading as clean-checkout evidence; `clean-clone` refuses a dirty tree. The destination must be new; relative paths resolve from the project target. Record mode redacts secret-shaped console and sidecar output before either is emitted.2. On a failure: read the label + command it printed, explain in plain language what broke, and point at that phase's line in `.harness/verify.conf` to fix or refine.3. Report the actual pass/fail output — not a summary of intent.The v1 receipt covers deterministic commands only. Keep screenshots, videos, manual assertions,published results, and real runtime or visual checks as separately referenced artifacts. A greenreceipt does not satisfy an end-to-end gate that requires those observations.## Fallback — no runner or no conf1. Say so plainly, and look at `.harness/verify.conf.example` for the intended phases.2. Run the obvious checks for this project directly and show their output: build, test, lint, link/render check, a dry-run. For non-code work, "verify" = open the artifact and confirm it renders / the numbers reconcile / the links resolve.3. If nothing is wired yet, propose the phases this project needs and offer to write `.harness/verify.conf` — but still run the checks by hand this time.## ReportState each check and its evidence: "build ok, 42 tests green, lint clean" — with the output, not"should pass". Anything skipped is "deferred: reason", never silence.

Frequently asked questions