Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →reinamaccredy/maestro-bundle
Route work into the right maestro tier and drive the SPEC/NOTES/VERIFY bundle lifecycle - open, resume, close, recall.
Passed 18 of 22 test cases with the skill, and 4 of 22 without it.
and 16 more in the full report
15 fixed5 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 15 test cases the skill fixed. Same model, same prompt, with and without the skill.
I want to inspect the complete trio contract, linked work items, and associated decisions for bundle-707 without altering any state. What command should I use?
| Checked | Without skill | With skill |
|---|---|---|
| Includes the command `maestro bundle show bundle-707`. | Missed | Passed |
The instructions your model reads when the skill loads.
Use WORKFLOW.md for method rules and routing. This skill owns record creation, resume, and handoff procedures.
Apply Tiers after bounded reconnaissance.
For tracked work use maestro work add|start|done. When Full is warranted,
open the bundle in the store whose checkout will change, even when design
runs in the Hub. List Hub decisions as hub:<id>; maestro bundle show
renders them. Note the bundle on the Hub map and the map on its work item.
maestro bundle open <id> --work <workId> # scaffold SPEC/NOTES/VERIFY, link work
Follow Bundle contract.
Use maestro handoff <bundle-id> to render NOTES.md from work, decisions,
handbacks, failures, and the latest checkpoint. Fill only placeholders the
store cannot prove, including original authorization and retained gates.
Use maestro bundle show <id> to read the contract and linked decisions.
Never create root SPEC-*, NOTES-*, or VERIFY-* files.
maestro bundle open <id> [--work <id>] # scaffold + active row
maestro bundle close <id> # snapshot trio into the store, archive
maestro bundle pause <id> [--reason] # active stays open, out of the way
maestro bundle resume <id> # paused back to active
maestro bundle list # states: active | paused | archived
maestro bundle show <id> # trio + linked work + decisions
maestro bundle save <dir> # ingest a foreign trio dir as archived
maestro search "<term>" # recall: hits labeled (bundle, ...)
test cases passed, vs 4 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.