Agent-Skills.md

Agent Skills: Maestro Setup

Scaffolds project context (product, tech stack, coding guidelines, product guidelines, workflow) and initializes track registry. Use for first-time project onboarding.

UncategorizedID: ReinaMacCredy/my-workflow/maestro-setup

Repository

ReinaMacCredy/my-workflow
ReinaMacCredyLicense: MIT
233

Install this agent skill to your local

pnpm dlx add-skill https://github.com/ReinaMacCredy/maestro/tree/HEAD/embedded/skills/maestro-setup

Skill Files

Browse the full folder contents for maestro-setup.

Download Skill

Loading file tree…

embedded/skills/maestro-setup/SKILL.md

Skill Metadata

Name
maestro-setup
Description
"Use after Maestro init/install or doctor warnings to tune a repository harness from verified repo evidence."

Maestro Setup

Tune a Maestro-enabled repository harness from current repository evidence.

Activate: maestro hook record --event skill_activation --skill maestro-setup

Use

  • After maestro init.
  • After maestro install.
  • When maestro doctor reports setup or local agent integration problems.
  • When a repo's build/test/harness instructions are missing or stale.

Do

  1. Run pwd, then maestro status.
  2. If the repo is not initialized, run maestro init --dry-run.
  3. If dry-run prints operating on <path> and that path is not the intended current project root, stop and ask the user to pick or create the root before any write.
  4. Only after the root is correct, run maestro init --yes.
  5. Run maestro doctor.
  6. If no agent integration is installed, run maestro install --agent codex unless the user asked for another agent.
  7. Inspect repo structure, build/test commands, and workflow constraints.
  8. Read in the existing agent and doc instructions as a BOUNDED set: at the repo root, and under each folder matched by the projects: globs in .maestro/harness/harness.yml, read AGENTS.md, CLAUDE.md, README.md, and top-level docs/*.md. Stay shallow (one level per location, no deep crawl) and skip outsized files (roughly 64 KB and up) so a vendored doc dump cannot flood context. With no projects: declared, this is the repo root alone.
  9. Synthesize what you read into the SINGLE root harness guidance, one section per project (a single section when nothing is declared). This is read-in only: never write maestro-managed guidance into a sub-project's own AGENTS.md/CLAUDE.md -- maestro install/sync write managed blocks at the repo root alone. Cite the inspected files; do not tune from guesses.
  10. Run maestro doctor, then maestro status.

Stop

  • maestro init --dry-run writes nothing; use it before init writes.
  • maestro init --yes keeps existing files and creates missing files.
  • Use maestro init --force only for deliberate refresh; it backs up managed files first.
  • Do not tune the harness from guesses, package-manager defaults, or stale chat memory.
  • Per-project docs are read-in only. Maestro owns one root scope; never write maestro-managed guidance into a sub-project's AGENTS.md/CLAUDE.md.

Done

  • Setup is healthy, or the remaining setup blocker is explicit.
  • The next handoff is visible from maestro status.
  • Harness guidance changes cite inspected files or commands.
Maestro Setup Skill | Agent Skills