Maestro Verify

Maestro Verify is a Quality skill for Claude Code, published by ReinaMacCredy in maestro.

231 stars24 forkson ReinaMacCredy/maestroAdded 2026/09/03Repository updated 2026/09/02

agent-harnessagent-skillsai-agentsai-coding-agentsclaude-codeclicodexconductorharness-engineeringharness-oshermeshermes-agentlocal-firstmcporchestrationplugintypescriptworkflow

Install in seconds

Install Maestro Verify

Copy Maestro Verify into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/ReinaMacCredy/maestro/tree/main/src/plugins/skills/maestro-verify ~/.claude/skills/maestro-verify

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/ReinaMacCredy/maestro.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: src/plugins/skills/maestro-verify/SKILL.md in ReinaMacCredy/maestro
Installs to: ~/.claude/skills/maestro-verify
Collection: One of 5 skills cataloged from this repository
Category: Quality — 1478 skills

What Maestro Verify does

Maestro Verify cross-checks coverage, runs VERIFY scenarios, and records a verdict for close, commit, install, push, release, or archive gates. It also captures durable lessons into decisions and avoids claiming remote state from local evidence.

Maestro Verify is cataloged under Quality on DirSkills. Maestro Verify comes from a repository tagged agent-harness, agent-skills, ai-agents, ai-coding-agents and claude-code.

Documentation

README

Excerpt

maestro-verify

Use for close, commit, install, push, publish, release, or archive gates. Local implementation authority does not imply authority for remote or external state changes.

Evidence layers

Proof follows five links. Claim only as far as the last proven link.

source - source-level tests, lint, type checks, or direct inspection.
artifact - the built or packaged output is present and has been read back.
installed - the installed stamp, version, or files match the intended artifact.
live - the running process, pid, or active runtime matches the installed layer.
journey - the real user path reaches the observable outcome end to end.

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Maestro Verify

What else does ReinaMacCredy publish alongside Maestro Verify?
Maestro Verify is one of 5 skills that DirSkills catalogs from ReinaMacCredy/maestro, the repository it ships in. Its siblings there include Maestro Bundle, Maestro Design and Maestro Improve. Each one is a separate skill with its own page in this directory, installs the same way Maestro Verify does, and is maintained by ReinaMacCredy in that same repository. The rest of the collection is listed on the ReinaMacCredy/maestro page.
How does Maestro Verify compare to other Quality skills?
Maestro Verify ranks #1359 by stars among the 1478 Quality skills in this catalog. The most-starred ones next to it are Benchmark, Benchmark Optimization Loop and API Design Patterns. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Maestro Verify against them. Open each page to compare what they document and how they install.