How do I install the Maestro Explore skill?

Run npx skillmds@latest add reinamaccredy/maestro-explore 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 Explore safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Maestro Explore?

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 Explore free to use?

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

Who published Maestro Explore?

ReinaMacCredy (@reinamaccredy) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Maestro Explore by reinamaccredy — Agent Skill

Name: Maestro Explore
Author: ReinaMacCredy

Maestro Explore

Answer an evidence question without touching production code - research external facts against primary sources, build or iterate a disposable prototype (its own bugfixes included), or baseline current repository behavior before deciding or implementing. Use when the question is answerable by reading, building, or measuring with no user decision required; unsettled decisions belong to maestro-design. Prototypes are throwaway.

ReinaMacCredy e041122 5 files · 19.5 KB Updated Sep 17, 2026

File contents

maestro-explore

Answer an open question with evidence, without touching production code. Read-only toward production paths; exploration never authorizes implementation. Any tier may use it.

Three modes; pick whichever settles the question:

research - documented or external facts: read source, docs, or the web; record findings with links so claims stay traceable. Procedure: references/research.md.
prototype - an environment-specific behavior question that reading cannot settle: build the smallest throwaway that answers it, outside production paths. Prototypes are disposable; only a decision-encoding fragment (a schema, a reducer, a type shape) may be inlined into a locked decision or the bundle's SPEC.md. Fixing the prototype's own bugs is still this mode - a fix routes to maestro-work only when the target is production code; iterate directly, no re-routing pass per request. When the user approves porting, the port is production work: route it by tier (maestro-bundle tier rule); the prototype never merges as-is. "Ship it as-is" waives the rewrite, not the route. A prototype that is deployed or relied on in real work is no longer throwaway: say so, and route its next change by tier. Procedure: references/prototype.md.
baseline - current repository behavior that must be preserved or changed: capture it as runnable commands with observed output, so maestro-verify can compare later. Phrase each behavior the work must preserve as a guard, "the system SHALL CONTINUE TO ", so preserved behavior is a checkable claim, not an assumption.

Where findings land

A fact that settles a fork becomes a decision: maestro decision draft "<choice>" --rationale "<why, with source link>" --work <id>, then maestro decision lock <id>.
Working evidence for an open work item: maestro work note <id> "<finding + link>"; in a bundle, also the NOTES.md Current State.
A baseline the work must preserve: a VERIFY.md scenario in the bundle, or the work item's acceptance when there is no bundle.
No work item and no bundle: deliver the findings in the conversation. Open a work item only if the question feeds work that will actually happen; a finding alone never opens a bundle.

maestro search "<topic>" before any research: a past decision or note may already hold the answer.

---name: maestro-exploredescription: Answer an evidence question without touching production code - research external facts against primary sources, build or iterate a disposable prototype (its own bugfixes included), or baseline current repository behavior before deciding or implementing. Use when the question is answerable by reading, building, or measuring with no user decision required; unsettled decisions belong to maestro-design. Prototypes are throwaway.---# maestro-exploreAnswer an open question with evidence, without touching production code.Read-only toward production paths; exploration never authorizesimplementation. Any tier may use it.Three modes; pick whichever settles the question:- **research** - documented or external facts: read source, docs, or the web; record findings with links so claims stay traceable. Procedure: [references/research.md](references/research.md).- **prototype** - an environment-specific behavior question that reading cannot settle: build the smallest throwaway that answers it, outside production paths. Prototypes are disposable; only a decision-encoding fragment (a schema, a reducer, a type shape) may be inlined into a locked decision or the bundle's SPEC.md. Fixing the prototype's own bugs is still this mode - a fix routes to `maestro-work` only when the target is production code; iterate directly, no re-routing pass per request. When the user approves porting, the port is production work: route it by tier (`maestro-bundle` tier rule); the prototype never merges as-is. "Ship it as-is" waives the rewrite, not the route. A prototype that is deployed or relied on in real work is no longer throwaway: say so, and route its next change by tier. Procedure: [references/prototype.md](references/prototype.md).- **baseline** - current repository behavior that must be preserved or changed: capture it as runnable commands with observed output, so `maestro-verify` can compare later. Phrase each behavior the work must preserve as a guard, "the system SHALL CONTINUE TO <existing behavior>", so preserved behavior is a checkable claim, not an assumption.## Where findings land- A fact that settles a fork becomes a decision: `maestro decision draft "<choice>" --rationale "<why, with source link>" --work <id>`, then `maestro decision lock <id>`.- Working evidence for an open work item: `maestro work note <id> "<finding + link>"`; in a bundle, also the NOTES.md Current State.- A baseline the work must preserve: a VERIFY.md scenario in the bundle, or the work item's acceptance when there is no bundle.- No work item and no bundle: deliver the findings in the conversation. Open a work item only if the question feeds work that will actually happen; a finding alone never opens a bundle.`maestro search "<topic>"` before any research: a past decision or note mayalready hold the answer.

Frequently asked questions