Agent skill

Maestro Bundle

by ReinaMacCredy in ReinaMacCredy/maestro

Route work into the right maestro tier and drive the SPEC/NOTES/VERIFY bundle lifecycle - open, resume, close, recall.

MITAuto-check passedMobile

Install Maestro Bundle

skills CLI
$ npx skills add ReinaMacCredy/maestro --skill maestro-bundle -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ReinaMacCredy/maestro maestro-bundle --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ReinaMacCredy/maestro.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/plugins/skills/maestro-bundle .claude/skills/maestro-bundle && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
maestro-bundle
GitHub stars
233
Token cost
~1.3k tokens
SKILL.md length
599 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

Route work into the right maestro tier and drive the SPEC/NOTES/VERIFY bundle lifecycle - open, resume, close, recall.

  • Works in 3 steps: Continuation with a bundle. A future… → Transfer. The work leaves this… → No bundle. For tracked work, save the…
  • Tasks that involve Mobile testing and debugging
  • SKILL.md covers Tier rule, The trio contract, Verbs and Authorization boundaries, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Maestro Bundle is an agent skill from ReinaMacCredy/maestro. Route work into the right maestro tier and drive the SPEC/NOTES/VERIFY bundle lifecycle - open, resume, close, recall.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Mobile, covering Mobile testing and debugging. It works with Git. The repository describes itself as: Local-first coordination for human and agent work: durable work, decisions, dispatches, evidence, and prompt-first methods, powered by TypeScript and Bun. The licence is MIT.

When your agent uses it

  • Tasks that involve Mobile testing and debugging

Example prompts

  • “/maestro-bundle”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Continuation with a bundle. A future session, in any tool, continues
  2. Transfer. The work leaves this workspace, to a person, another repo,
  3. No bundle. For tracked work, save the continuation packet as a

What it can do on your machine

Read from SKILL.md and the folder at commit 2412403. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Maestro Bundle loads about 1.3k tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 599 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~33
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from ReinaMacCredy/maestro at commit 2412403, republished under its MIT licence (© ReinaMacCredy). 599 words, ~1,296 tokens.

Download SKILL.mdSave it as .claude/skills/maestro-bundle/SKILL.md (or your agent's skills folder).
name
maestro-bundle
description
Route work into the right maestro tier and drive the SPEC/NOTES/VERIFY bundle lifecycle - open, resume, close, recall.
review-date
2026-11-28
<!-- maestro-skill-version: dev -->

maestro-bundle

Use WORKFLOW.md for method rules and routing. This skill owns record creation, resume, and handoff procedures.

Tier rule

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

The trio contract

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.

Verbs

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, ...)

Authorization boundaries

Follow Authorization boundaries. Put the original user instruction or retrievable reference on the work item so the successor can verify the grant, rather than relying on an agent's summary.

Routing

Use Routing; a skill transition is internal, not another user approval gate.

Resume protocol

Follow Resume. For Light, read the work and checkpoint without opening a bundle. For Full, locate and read the existing bundle, then reconcile it with the checkout before continuing.

Concurrency and git

Follow Concurrency and git. Record the work owner and task-owned paths in the handoff, not just the branch.

Compact or hand off

Hand off instead of compacting when:

  • the owner changes
  • a dependency becomes its own branch
  • the role changes
  • the context is full of false starts

Compact only when ownership, scope, and role stay stable and the history still helps the same writer continue. Compaction gives no warning turn in either harness, so the checkpoint must already exist: keep a checkpoint: work note (state / next / avoid, latest wins) on each held item, rewritten at every meaningful change of state or next action; the SessionStart brief prints it back after the compaction. Nothing summarized is trusted over it.

Use break-before-make when the writer on a moving scope changes: release the lease and refresh the handoff before the new session starts. The handoff packet must preserve the base, Current State, Next Action, Authority transferred and retained, Failed approaches, and Do not repeat.

Show full SKILL.md (228 more words)Show less

Hand-off

Run maestro handoff <bundle-id> to seed untouched NOTES.md sections when a bundle exists. Then decide which of three cases this is; the destination differs:

  1. Continuation with a bundle. A future session, in any tool, continues this bundle in this workspace. The handoff IS the rendered NOTES.md covering every section the trio contract names, with a Driver: line naming the tool expected to resume. The bundle stays active; the next session's resume protocol must find it.
  2. Transfer. The work leaves this workspace, to a person, another repo, or an agent that will not resume the bundle. Write the standalone document below, then close the bundle per maestro-verify's close order, citing the handoff target.
  3. No bundle. For tracked work, save the continuation packet as a checkpoint: work note with original authorization and retained gates. If an untracked quickfix needs continuation, create a Light work item. For a transfer outside this workspace, provide a standalone document in the OS temporary directory, report its path, and transfer it to the recipient; a local path alone is not accessible from another machine.

The standalone document (cases 2 and 3) names the suggested skills for the next agent, references specs, decisions, commits, and diffs by path or id instead of duplicating them, and redacts secrets and personal data.

Design lane -> use the maestro-design skill. Implementation -> maestro-work. Verification and close -> maestro-verify.

© ReinaMacCredy, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in src/plugins/skills/maestro-bundle of ReinaMacCredy/maestro.

Open the folder on GitHubat commit 2412403

Compare with similar skills

Maestro Bundle next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Maestro Bundle compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Maestro Bundle this skillReinaMacCredy/maestro233—~1.3kAutomated safety check: PassMIT
Maestro Mergecatlog22/maestro-flow564—~1.3kAutomated safety check: NotesNone
Maestro Forkcatlog22/maestro-flow564—~1.3kAutomated safety check: NotesNone
Maaend Test ImageMaaEnd/MaaEnd4k—~1.3kAutomated safety check: PassAGPL-3.0
MAUI UI Test Writerdotnet/maui23k—~3kAutomated safety check: PassMIT
Phone HarnessShawnPana/phone-harness3.2k—~4.3kAutomated safety check: PassMIT

Similar skills

  • Maestro Merge

    catlog22/maestro-flow

    Merge session worktree branch back to main. An agent skill from catlog22/maestro-flow.

    564 GitHub stars~1.3k tokensUpdated 2 days ago
    MobileAuto-check: notes
  • Maestro Fork

    catlog22/maestro-flow

    Create or sync session worktree for parallel dev. An agent skill from catlog22/maestro-flow.

    564 GitHub stars~1.3k tokensUpdated 2 days ago
    MobileAuto-check: notes
  • Maaend Test Image

    MaaEnd/MaaEnd

    为 MaaEnd 添加、导入或补充节点识别测试截图,并按仓库约定脱敏图片、放入 tests/MaaEndTestset、维护 tests//test.json 和运行 pnpm check/pnpm test 验证。用户提到“添加测试图片/截图”“把截图加入 ADB 或 Win32 测试集”“给节点补正例或反例”“更新 hits/box”“UID…

    4k GitHub stars~1.3k tokensUpdated today
    MobileAuto-check passed
  • Official

    Writes UI tests that reproduce a GitHub issue in .NET MAUI and keeps iterating until the tests actually fail, proving they catch the bug.

    23k GitHub stars~3k tokensUpdated today
    Testing & QAAuto-check passed
  • Phone Harness

    ShawnPana/phone-harness

    Control the user's phone — an iPhone through the Mac's iPhone Mirroring window, an Android over adb, or a rented cloud Android: open apps, tap, type, swipe, read the screen.

    3.2k GitHub stars~4.3k tokensUpdated yesterday
    MobileAuto-check passed
  • Maa Issue Log Analysis

    MaaAssistantArknights/MaaAssistantArknights

    分析 MaaAssistantArknights 上游仓库公开 Issue(https://github.com/MaaAssistantArknights/MaaAssistantArknights/issues/...

    24k GitHub stars~4k tokensUpdated today
    MobileAuto-check passed

More from ReinaMacCredy/maestro

All 11 skills in this repo
  • Maestro Improve

    ReinaMacCredy/maestro

    Turn filed lessons into the smallest doctrine edit. An agent skill from ReinaMacCredy/maestro.

    233 GitHub stars~1.9k tokensUpdated 12 days ago
    Auto-check passed
  • Maestro Council

    ReinaMacCredy/maestro

    Lead-only council for a hard-to-reverse fork - a neutral brief, sealed independent seats, one premise verifier on unanimity, bounded verifiers, one cross-examination round, a draft-verdict audit…

    233 GitHub stars~2.9k tokensUpdated 12 days ago
    Auto-check passed
  • Maestro Design

    ReinaMacCredy/maestro

    Resolve material unknowns blocking the next authorized slice, using research, grilling, prototypes, models, or wayfinding.

    233 GitHub stars~2.1k tokensUpdated 12 days ago
    Auto-check passed
  • Maestro Graph

    ReinaMacCredy/maestro

    Drive a pre-known multi-agent path as a maestro graph - run it by name or from a file you just wrote, pull each agent node with graph next, spawn it as a sub-agent under its maestro-<profile…

    233 GitHub stars~2.1k tokensUpdated 12 days ago
    Auto-check passed
  • Maestro Verify

    ReinaMacCredy/maestro

    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.

    233 GitHub stars~1.9k tokensUpdated 12 days ago
    Auto-check passed
  • Maestro Work

    ReinaMacCredy/maestro

    Implement or fix one authorized unit with minimal edits and sufficient evidence.

    233 GitHub stars~2.6k tokensUpdated 12 days ago
    Auto-check passed

Works with

Categories

Questions about Maestro Bundle

What does Maestro Bundle do?

Route work into the right maestro tier and drive the SPEC/NOTES/VERIFY bundle lifecycle - open, resume, close, recall. Maestro Bundle is an agent skill from ReinaMacCredy/maestro. Route work into the right maestro tier and drive the SPEC/NOTES/VERIFY bundle lifecycle - open, resume, close, recall.

When should I use Maestro Bundle?

Maestro Bundle fits situations like: tasks that involve Mobile testing and debugging.

How do I install Maestro Bundle in Claude Code?

Run `npx skills add ReinaMacCredy/maestro --skill maestro-bundle -a claude-code`. Or copy the skill folder (src/plugins/skills/maestro-bundle in ReinaMacCredy/maestro) into .claude/skills/maestro-bundle in your project. Claude Code loads it when a task matches its description.

How do I install Maestro Bundle in Codex?

Run `npx skills add ReinaMacCredy/maestro --skill maestro-bundle -a codex`. Or copy the skill folder (src/plugins/skills/maestro-bundle in ReinaMacCredy/maestro) into .agents/skills/maestro-bundle in your project. Codex loads it when a task matches its description.

Can I use Maestro Bundle in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ReinaMacCredy/maestro --skill maestro-bundle -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/maestro-bundle, .gemini/skills/maestro-bundle, .github/skills/maestro-bundle and .opencode/skills/maestro-bundle in your project.

What does Maestro Bundle need to run?

SKILL.md names no scripts, command-line tools or credentials: Maestro Bundle is instructions for the agent only.

Does Maestro Bundle access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Maestro Bundle safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Maestro Bundle use?

Maestro Bundle is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Maestro Bundle use?

About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Maestro Bundle?

Skills that share tags, products or a category with Maestro Bundle: Maestro Merge (catlog22/maestro-flow, 564 stars), Maestro Fork (catlog22/maestro-flow, 564 stars), Maaend Test Image (MaaEnd/MaaEnd, 4k stars) and MAUI UI Test Writer (dotnet/maui, 23k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Maestro Bundle?

ReinaMacCredy (a GitHub user) maintains it in ReinaMacCredy/maestro, which has 233 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on September 28, 2026.

Source: ReinaMacCredy/maestro on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.