Przejdź do treści
Biblioteka skilli
AI i agenci · Integracja z narzędziem

maestro

/maestro

Odpowiada na pytania o narzędzie maestro, konfiguruje je w projekcie, uruchamia i odzyskuje koncerty oraz pisze kompozycje i paczki.

Repozytorium
maestro ↗
Licencja
MIT
Ostatnia zmiana repozytorium
13.11.2026

Ocena i bezpieczeństwo

90/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść25 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
14
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 13.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Odpowiada na pytania o narzędzie maestro, konfiguruje je w projekcie, uruchamia i odzyskuje koncerty oraz pisze kompozycje i paczki.

Oryginalny opis (EN)

maestro, the CLI that composes and performs agent compositions as concerts. Use when answering a question about maestro, setting it up in a project (.maestro/config.yaml), performing, following or recovering a concert, reading its exit code, record or changeset, or writing a composition or pack.

Jak działa

  1. Words
  2. Where to look
  3. Exit codes and outcomes
  4. Ground rules
Sekcje z nagłówków SKILL.md, w oryginale · 75 linii, 841 słów
Podgląd SKILL.md
---
name: maestro
description:
  maestro, the CLI that composes and performs agent compositions as concerts. Use when answering a question about
  maestro, setting it up in a project (.maestro/config.yaml), performing, following or recovering a concert, reading its
  exit code, record or changeset, or writing a composition or pack.
---

# maestro

maestro builds a composition into a checked plan with `compose`, which spends nothing, then `perform`s it as a concert.
Its agents and checks work in lanes, never in the user's checkout; results leave as a changeset the user applies.

Checked against maestro 0.2.0-rc.3. Where `maestro --version` names another release, trust `maestro <verb> --help`.

## Words

- **Composition**: authored code that builds a graph from typed params; `<pack>.<composition>` or a `.ts` file.
- **Compose**: builds the graph and ends in **pre-flight**, the full check before any spend. No side effects.
- **Plan**: what compose prints: node counts, bounds (`up to 3 repo.agent`) and diagnostics.
- **Perform**: starts a **concert** from a plan. A concert has an id, a record and a result.
- **Node instance**: one node within a concert, named like `test`, `loop[0]/repair` or `parMap[risk]/skeptic`.
- **Outcome**: how an instance or a concert ended: `ok`, `rejected`, `failed` or `skipped`.
- **Lane**: an isolated, versioned working copy cut from the target. Each version is `<concert id>.<node instance>`.
- **Changeset**: a lane version's patches, the only way results leave a concert.
- **Profile**: a named agent setup: its runtime (harness, model, thinking level), instructions and limits.
- **Seat**: a composition's slot for an agent; it names a profile, and config may rebind it.
- **Check**: a named shell command from config (tests, lint, build) run in a lane; its exit code is its verdict.
- **Preset**: a named config layer switched per concert with `--preset`.
- **Stub concert**: a concert whose agents change nothing, for a rehearsal with no spend.
- **Pack**: an installed set of compositions. The release ships `classics`; its `README.md` and `maestro rep classics`
  describe it.
- **Workspace**: the nearest directory from the cwd up holding `.maestro/`; its config layers over the user's.
- **Tour**: a slug grouping related concerts, for listing and pruning them together.

## Where to look

| To                                                             | Read                                                     |
| -------------------------------------------------------------- | -------------------------------------------------------- |
| Set maestro up in a project, or fix a `CFG.*` or `HOST.*`      | [bootstrap.md](bootstrap.md)                             |
| Write or change a config key: target, checks, prepare, sandbox | [config.md](config.md)                                   |
| Layer config: a preset, a `-c` flag, `!append`, `!delete`      | [presets.md](presets.md)                                 |
| Give a profile a harness and model, inspect or probe it        | [profiles.md](profiles.md)                               |
| Perform a composition, follow it and read its result           | [perform.md](perform.md)                                 |
| Rehearse a composition with no spend                           | [stub.md](stub.md)                                       |
| Read a concert's instances, artifacts, lanes or data root      | [records.md](records.md)                                 |
| Show or apply a changeset                                      | [changesets.md](changesets.md)                           |
| Resume, encore, kill, prune or tour concerts                   | [recover.md](recover.md)                                 |
| Write a composition for a shape no pack has                    | [composition.md](composition.md)                         |
| Look up an SDK call, a seat's options or a code node's `ctx`   | [sdk.md](sdk.md)                                         |
| Write an agent's task prompt or profile instructions           | [prompts.md](prompts.md)                                 |
| Build a pack, or build on the classics pack's parts            | [packs.md](packs.md)                                     |
| Learn a verb's flags                                           | `maestro --help`, `maestro <verb> --help`                |
| Learn an installed composition's params                        | `maestro rep --json`, `maestro rep <pack>.<composition>` |

For a user who wants every task driven through a composition written for it, point at the `/maestro-ultracode` mode.

## Exit codes and outcomes

| Code    | Means                                                                    | Next                                                 |
| ------- | ------------------------------------------------------------------------ | ---------------------------------------------------- |
| 0       | Done, or the concert settled `ok`                                        | Report the outputs and the changeset                 |
| 1       | The concert settled `failed`, or a composition, config or command failed | Read the message and hints; fix the cause and resume |
| 2       | Usage error                                                              | Fix the command                                      |
| 3       | The concert settled `rejected`, or `cs apply` left conflicts             | Report the root cause instance and its reason        |
| 124     | `wait --timeout` passed, the concert still running                       | Wait again                                           |
| 130/143 | `perform`, `resume` or `encore` was stopped by Ctrl-C or SIGTERM         | `maestro resume <id>`                                |

- `rejected` is a verdict: a red check or a verdict agent's no. The concert's reason is its root cause's.
- `failed` is a crash, a broken contract (a timeout, a missing declared output, a cancel) or an agent's
  `blocked: <cause>`. Fix the cause, then resume.
- `skipped` is an instance whose guard was false or whose input was not `ok`; its root cause is elsewhere.

## Ground rules

- The user's checkout stays theirs: maestro never writes it, and applying a changeset waits for the user's yes.
- Before a perform on a paid harness, give the user the plan's `repo.agent` bound as the spend ceiling.
- Kill a concert, or prune one, only when you started it or the user names it.
- Secrets live in the environment (`CLAUDE_CODE_OAUTH_TOKEN`, a harness login); params and committed config hold none.
- A pack is code that runs with the user's permissions: install or list under `packs` only packs the user chose.
- Parse `--json` output, which every verb but `cs` takes; the text form is for people.
Pliki w paczce (14)
  • SKILL.md 7 KB
  • bootstrap.md 5 KB
  • changesets.md 1 KB
  • composition.md 7 KB
  • config.md 5 KB
  • packs.md 5 KB
  • perform.md 5 KB
  • presets.md 2 KB
  • profiles.md 4 KB
  • prompts.md 2 KB
  • records.md 4 KB
  • recover.md 3 KB
  • sdk.md 8 KB
  • stub.md 2 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · dvalnn/maestro90MIT
justinedevs/meta-architect90MIT
jassics/awesome-claude-security90GPL-3.0

Migawka bazy z 13.11.2026 · wersja paczki 02919e9437e1 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100teach-maestro
    Prowadzi wstępną rozmowę o projekcie z Maestro, by zapisać kontekst w pliku .maestro.md przy pierwszym uruchomieniu.
  • 95running-as-maestro
    Przełącza sesję w tryb maestro: nadzoruje pracę podagentów i może kierować modele oraz poziom wysiłku.
  • 100microsoft-maestro
    Kieruje zadania dotyczące usług Microsoft SaaS do właściwego sub-maestro lub specjalisty, uruchamiając pojedynczego agenta albo zespół równoległy do czterech.
  • 100ai-maestro-agents-management
    Zarządza cyklem życia agentów AI przez CLI AI Maestro: tworzenie, lista, usuwanie, zmiana nazwy, hibernacja, wybudzanie, instalacja wtyczek, eksport i restart.
  • 90herdr-demo
    Pokazuje na żywo w panelach herdr przebieg uruchomienia maestro CLI lub testów akceptacyjnych.
  • 95agent-management
    Tworzy, zarządza i orkiestruje agentów AI przez CLI AI Maestro: tworzenie, listowanie, usuwanie, hibernacja, budzenie, instalacja pluginów i restart agentów.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.