Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →reinamaccredy/maestro-verify
Verify and close - cross-check coverage, run the VERIFY table, deliver the verdict, harvest durable lessons into decisions, close the bundle, and never claim remote state from local evidence.
Passed 12 of 16 test cases with the skill, and 7 of 16 without it.
and 10 more in the full report
8 fixed8 passed either way5 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
We dispatched a subagent for fresh-context verification of diff `checkout-flow`, but the subagent crashed at startup due to a runner system error. Should we keep retrying the subagent dispatch in a loop?
| Checked | Without skill | With skill |
|---|---|---|
| Treats subagent crash as a dispatch failure rather than code verification evidence. | Passed | Passed |
| Directs executing the verification checklist in the main session instead of polling. | Missed | Passed |
The instructions your model reads when the skill loads.
Use for verification and close. Read WORKFLOW.md for testing, recovery, authorization, and completion rules. Delivery actions such as commit, install, push, or release remain separate gates.
Precondition: an open bundle with a drafted VERIFY.md. Without a bundle,
verify inline and close a tracked item with maestro work done; an untracked
quickfix needs no record. This skill's table pass is for Full work. The
evidence-layer vocabulary below still applies to any claim at any tier.
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.The repository's verify-<repo> skill is the route to live and journey;
maestro recipe show verification-skill creates or maintains it.
"Tests pass" is a source claim. A claim that touches install or runtime must
include a readback at that layer. A suite that is green only on this machine
is not a source claim about the repo: before any commit, release, or handback
gate, re-run the touched suite with the developer environment removed
(HOME=$(mktemp -d), env -u HERDR_ENV). A test that reads the installed
copy, the room, or a home config passes for you and fails in CI. Every proof
and VERIFY result lists untested links explicitly as NOT TESTED, never by
omission:
proof: "suite 135 pass @ a52bd4a7 (source); runtime stamp readback a52bd4a7 (installed); live: NOT TESTED"
Assumptions not verified: None
Residual risks: None
test cases passed, vs 7 / 16 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.