How do I install the Maestro skill?

Run npx skillmds@latest add tomevault-io/maestro-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Maestro safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: CAUTION, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Maestro?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Maestro free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Maestro?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Maestro by tomevault-io — Agent Skill

Name: Maestro
Author: tomevault-io

File contents

Maestro in Gemini CLI

You are operating Maestro inside Gemini CLI. Keep everything native:

Commands: /maestro, /maestro:setup, /maestro:newTrack, /maestro:implement, /maestro:orchestrate, /maestro:status, /maestro:revert, /maestro:leindex, /maestro:tui.
Where commands come from: ~/.gemini/commands/maestro/*.toml (installed by the Maestro wizard).
MCP: mcpServers.leindex → { command: "maestro", args: ["mcp", "tool-search"] } (stdio) so Gemini reaches the Maestro MCP pool through the dynamic broker. Do not route to maestro.tldr or any archive/tldr paths.
Skill location: ~/.gemini/skills/maestro/ (this skill). Load it whenever a Maestro workflow is requested.

Quick flow

/maestro setup — initialize/refresh product, tech stack, workflow, track registry.
/maestro newTrack "<goal>" — generate spec + plan with clarifying questions.
/maestro implement <track> — execute plan; rely on LeIndex 5-phase analysis for file scoping.
/maestro orchestrate — cockpit/orchestrator panel (Rust TUI pane).
/maestro status — surface phase/task progress and blockers.
/maestro revert [track|phase|task] — controlled rollback.
/maestro leindex — LeIndex-first analysis; no TLDR imports.
/maestro tui — launch Rust cockpit (primary TUI; Go/Python TUIs are deprecated).

Guardrails

Avoid maestro.tldr and anything under maestro/archive/tldr; these are reference-only.
Keep token usage lean by constraining file scopes via LeIndex queries.
Respect installed MCP config; if LeIndex is missing, request /maestro:configure rerun.
Do not introduce cross-tool paths (no ~/.claude, ~/.config/opencode, etc.).

Validation checklist

~/.gemini/commands/maestro/*.toml are present and reference __MAESTRO_HOME__-substituted paths.
~/.gemini/settings.json contains mcpServers.leindex pointing to maestro mcp tool-search.
Skill lives at ~/.gemini/skills/maestro/.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: maestro-2description: Maestro spec-driven development for Gemini CLI. Use when running /maestro* commands or orchestrating tracks; keep LeIndex as the analysis engine and avoid legacy TLDR routing. Use when this capability is needed.---# Maestro in Gemini CLIYou are operating Maestro inside Gemini CLI. Keep everything native:- **Commands:** `/maestro`, `/maestro:setup`, `/maestro:newTrack`, `/maestro:implement`, `/maestro:orchestrate`, `/maestro:status`, `/maestro:revert`, `/maestro:leindex`, `/maestro:tui`.- **Where commands come from:** `~/.gemini/commands/maestro/*.toml` (installed by the Maestro wizard).- **MCP:** `mcpServers.leindex` → `{ command: "maestro", args: ["mcp", "tool-search"] }` (stdio) so Gemini reaches the Maestro MCP pool through the dynamic broker. Do **not** route to `maestro.tldr` or any archive/tldr paths.- **Skill location:** `~/.gemini/skills/maestro/` (this skill). Load it whenever a Maestro workflow is requested.## Quick flow1) `/maestro setup` — initialize/refresh product, tech stack, workflow, track registry.2) `/maestro newTrack "<goal>"` — generate spec + plan with clarifying questions.3) `/maestro implement <track>` — execute plan; rely on LeIndex 5-phase analysis for file scoping.4) `/maestro orchestrate` — cockpit/orchestrator panel (Rust TUI pane).5) `/maestro status` — surface phase/task progress and blockers.6) `/maestro revert [track|phase|task]` — controlled rollback.7) `/maestro leindex` — LeIndex-first analysis; no TLDR imports.8) `/maestro tui` — launch Rust cockpit (primary TUI; Go/Python TUIs are deprecated).## Guardrails- Avoid `maestro.tldr` and anything under `maestro/archive/tldr`; these are reference-only.- Keep token usage lean by constraining file scopes via LeIndex queries.- Respect installed MCP config; if LeIndex is missing, request `/maestro:configure` rerun.- Do not introduce cross-tool paths (no `~/.claude`, `~/.config/opencode`, etc.).## Validation checklist- `~/.gemini/commands/maestro/*.toml` are present and reference `__MAESTRO_HOME__`-substituted paths.- `~/.gemini/settings.json` contains `mcpServers.leindex` pointing to `maestro mcp tool-search`.- Skill lives at `~/.gemini/skills/maestro/`.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/scooter-lacroix) — claim your Tome and manage your conversions.

Frequently asked questions

Maestro