Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →reinamaccredy/maestro-work
Drive one accepted implementation unit test-first - smallest falsifiable behavior, minimum edits, evidence that names the real falsifier.
Passed 16 of 20 test cases with the skill, and 3 of 20 without it.
and 26 more in the full report
15 fixed3 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.
We need a lightweight dispatch envelope for a tiny 2-line typo fix in documentation assigned to a delivery lane. Can we drop the Excluded scope and Mutation fields to keep the text short?
| Checked | Without skill | With skill |
|---|---|---|
| State that dispatch envelopes for tiny tasks must still include Excluded scope. | Missed | Passed |
| State that dispatch envelopes for tiny tasks must still include Mutation. | Missed | Passed |
The instructions your model reads when the skill loads.
The matched playbook (maestro recipe show <name>, chosen by
Routing) owns the steps of a task. This
skill owns what every playbook shares: the brief a writer receives, the rules
it writes by, the handback it returns, and the record the holder keeps. A
writer is a delegate subagent, a lane in a Herdr pane, or the main chat on
a quickfix. Apply WORKFLOW.md for method rules;
pause only the slice blocked by scope or authority.
When work is handed to a writer (a delegate subagent, or a lane in a
Herdr pane in the room), send this envelope:
Objective: <observable outcome>
Owned scope: <paths or responsibility>
Excluded scope: <explicit non-goals>
Mutation: <no-write | write-bounded: paths>
Stop condition: <done or blocked boundary>
Lane: scout | decision | delivery | challenge | shadow
Evidence required: <proof and layer>
A tiny task may collapse the envelope to three lines, but it never drops
Excluded scope or Mutation. Name the playbook and step the work serves,
and point at files rather than pasting their content. Standing orders that
apply to every writer of one run go in one file every brief points at.
scout reads and reports state, never writes.delivery may write and is the only lane that holds the lease; a
subagent's brief borrows the lane word but never takes the lease.decision investigates, compares, and recommends without writing.challenge breaks the premise or candidate and returns findings only, with
no fixes or redesign.shadow runs beside the owner without writing and returns comparison
evidence that is never a candidate or a work write lease.test cases passed, vs 3 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.