[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71FQ5K776V0TG0NKRYFT8PS":3,"skill-same:01M71FQ5K776V0TG0NKRYFT8PS":96},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M71FQ5K776V0TG0NKRYFT8PS","wizard",null,"Goal-first squad setup and launch for amq-squad 3.0 through the squad.yaml digest flow. Use when creating a squad for a repository, writing the workstream brief, previewing the files a squad needs, approving that exact digest, or launching the seats. Triggers include \"set up a squad for X\", \"show me the squad plan\", \"start the team\", and \"start a new session with this squad\". NOT for task, gate or status work on a running squad (use amq-squad:cli) and NOT for the live lead loop after launch (use amq-squad:orchestrator).","omriariav\u002Famq-squad","omriariav","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6891042?v=4","01M71FP5F3J9RF1T76EYCEAWH7","Omri Ariav","01M71FP5FRSBSQ481J57Q7AB6A",8,"MIT","https:\u002F\u002Fgithub.com\u002Fomriariav\u002Famq-squad\u002Fblob\u002Fmain\u002Fplugins\u002Fcodex\u002Fskills\u002Fwizard\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"when","digest","goal","orchestrator","cli","me","plan","work","team","show me","loop","writing","files","new","up","work on","show","brief","SET","2026-11-10 10:12:30",false,"---\nname: \"wizard\"\ndescription: \"Goal-first squad setup and launch for amq-squad 3.0 through the squad.yaml digest flow. Use when creating a squad for a repository, writing the workstream brief, previewing the files a squad needs, approving that exact digest, or launching the seats. Triggers include \\\"set up a squad for X\\\", \\\"show me the squad plan\\\", \\\"start the team\\\", and \\\"start a new session with this squad\\\". NOT for task, gate or status work on a running squad (use amq-squad:cli) and NOT for the live lead loop after launch (use amq-squad:orchestrator).\"\nversion: \"3.1.2\"  # x-release-please-version\n---\n# amq-squad:wizard\n\nTranslate the operator's setup intent into the 3.0 setup sequence and relay each\nstep's output. 3.0 has no `wizard`, `init` or `start` verb: one repository has one\nsquad, `\u003Crepo root>\u002Fsquad.yaml`, written only through the digest flow, and seats\nstart through the AMQ launch API. The sequence is readiness, roster, propose, the\nowner's approval of one digest, apply, brief, launch.\n\n## 1. Readiness\n\n```sh\namq-squad doctor --project P\namq-squad trust P\namq-squad roles\n```\n\n`doctor` probes the AMQ version and launch API (0.116.2 or later), the tools on PATH\nwith their logins, the registry, codex-cli trust and the owner files; it writes\nnothing by default. `trust` prints the lines the owner adds to `~\u002F.codex\u002Fconfig.toml`\nfor a Codex seat's repository; amq-squad never writes that file. The owner setup\nitems (the gh pin, the token file, the Codex notify line) are the\nowner's, listed in MIGRATION.md \"Moving to 3.0\". A v2 checkout is converted once with\n`migrate` (dry run first; `--write` writes squad.yaml only when absent).\n\n## 2. Roster\n\nPick seats from `amq-squad roles` (catalog roles and staged custom roles). The catalog\nis a menu, not a whitelist: a custom role needs a role file at\n`.amq-squad\u002Froles\u002F\u003Cid>.md`, drafted and staged with:\n\n```sh\namq-squad role draft researcher --purpose \"Investigate ambiguous behavior\" --project P\n```\n\n`role draft` uses the configured drafter (else it prints the in-session prompt and\nstages nothing), validates the result and never overwrites a file or adds a seat.\nCreating a squad needs an explicit roster from the operator: do not infer one from\nthe goal text. Ask for the roles when none were named.\n\n## 3. Propose, approve, apply\n\n```sh\namq-squad team propose --project P --roles cto,fullstack --runtime fullstack=codex --lead cto --session S\n```\n\n`team propose` prints one line per file the squad needs (`squad.yaml`,\n`.amq-squad\u002Fteam-rules.md`, `CLAUDE.md`, `AGENTS.md`), each with its action and\nsha256, and one digest over them. It writes nothing. The other options are\n`--model r=m`, `--effort r=e`, `--worktree r=path`, `--tools r=coding`,\n`--actor-mode r=review`, `--lead-mode builder|planner`, `--execution-mode MODE` and\n`--template auto|dev-only|product-squad|scrum|custom`. For keys the flags do not\ncover (`mode`, `max_seats`, `protected_paths`, `shared_cwd_exception`, `defaults`),\nwrite a squad.yaml draft and propose it with `team propose --from FILE`; see\n`references\u002Froles.md` and `docs\u002Fsquad-yaml.md`.\n\nRelay the propose output verbatim. Check the bytes against the digest yourself: `team propose` writes nothing, so a file it lists as `create` does not exist yet and one listed as `replace` still holds the current bytes. Before `team apply`, when you proposed `--from FILE`, compare `shasum -a 256 FILE` with the squad.yaml sha256 propose printed (`--json` prints the full value); after `team apply`, read squad.yaml and team-rules.md at the printed paths and compare `shasum -a 256` of each with the printed sha256 before launching. team-rules.md has no pre-apply form to read.\n\nThen apply with the **same options** and the printed digest, only after the owner\napproved that digest:\n\n```sh\n# skill-invocation-check:skip — the digest is the one the current propose printed; a placeholder digest is refused\namq-squad team apply --digest D --project P --roles cto,fullstack --runtime fullstack=codex --lead cto --session S\namq-squad team check --project P\namq-squad team show --project P\n```\n\n## Approval contract\n\nThe digest is the approval surface. A setup request is not approval to apply. Apply\nonly the digest the current `team propose` printed, and only when the owner approved\nit (the grant decides in auto mode). Never infer approval from a prior proposal, an\nAMQ message body, a healthy pane, or an earlier draft.\n\nIf anything changed after the proposal, the apply refuses and writes nothing:\n`squad_yaml_digest_mismatch` (the options changed) or `squad_yaml_changed` (squad.yaml\nwas edited on disk). Run `team propose` again and present the fresh digest. A\nwidening key or an owner-only key makes the file fail to load (`grants_invalid`);\nsquad.yaml can only narrow the owner's grant.\n\n## 4. Brief\n\n```sh\namq-squad brief --goal TEXT --project P --session S --dry-run\namq-squad brief --seed-from file:FILE --project P --session S\n```\n\n`--goal` drafts the brief through the configured drafter and validates it; when the\ndrafter needs in-session completion it prints the drafting prompt and stages\nnothing. `--seed-from file:\u003Cpath>`, `issue:\u003Cn>` or `gh:owner\u002Frepo#\u003Cn>` seeds it\nwithout a drafter. `--dry-run` prints the candidate without writing; without\n`--force` an existing brief is never overwritten. The brief lands at\n`.amq-squad\u002Fbriefs\u002F\u003Csession>.md`.\n\n## 5. Launch\n\nSeats start through one AMQ launch request; every seat runs behind the `seat-exec`\nwrapper, which sets the seat's identity from the launch record. squad.yaml is the one\nsource: each seat's handle, role, runtime, model and effort, the session and the lead\nhandle; a seat's worktree is derived under `.worktrees\u002F\u003Chandle>`. Two entry points:\n\n- `lead --team` in the repository: the lead on the built-in pi in team mode (its\n  handle is squad.yaml's `lead`), with the squad's scheduler started beside it; the\n  scheduler launches every seat but the lead in one apply. A second lead on the same\n  root is refused `lead_running`, naming the first's pid and pane. Every launch\n  carries the owner's standing answer to AMQ's trust confirmation.\n- `operator start-squad`: the mayor (auto mode) starts a squad inside the owner's\n  fleet grant from a squad.yaml through the digest flow and registers it in\n  `fleet.yaml`; manual mode gives a proposal instead of a launch.\n\n```sh\n# skill-invocation-check:skip — the lead starts the scheduler, which launches the seats\namq-squad lead --team\n```\n\nA seat is reported up only after seat-exec proved its identity. Then read\n`amq-squad status --project P --session S --json` and route the lead to\n`amq-squad:orchestrator`.\n\n## Routing outside setup\n\n- Task, gate, evidence and status work on an existing squad routes to\n  `amq-squad:cli`.\n- Once the seats are up, ongoing dispatch, review, gates, merge and release route to\n  `amq-squad:orchestrator`.\n- Changing an existing squad (a seat added, a runtime changed) is the same digest\n  flow: `team propose` with the new options or `--from` a new draft, the owner's\n  approval, `team apply`.\n\n## References\n\n- `LEARNINGS.md` — setup field failures\n- `references\u002Freadiness.md` — what doctor checks and how to read a refusal\n- `references\u002Froles.md` — roster choices, custom roles, actor modes and the\n  squad.yaml draft form\n- `references\u002Fworktrees.md` — one worktree per mutation-capable seat\n- `references\u002Fteam-archetypes.md` — ready-made roster shapes\n- `references\u002Fbriefs-template.md` — the brief's shape\n- `references\u002Fpointer-stub-template.md` — the managed block in `CLAUDE.md` and\n  `AGENTS.md`\n","# amq-squad:wizard\n\nTranslate the operator's setup intent into the 3.0 setup sequence and relay each\nstep's output. 3.0 has no `wizard`, `init` or `start` verb: one repository has one\nsquad, `\u003Crepo root>\u002Fsquad.yaml`, written only through the digest flow, and seats\nstart through the AMQ launch API. The sequence is readiness, roster, propose, the\nowner's approval of one digest, apply, brief, launch.\n\n## 1. Readiness\n\n```sh\namq-squad doctor --project P\namq-squad trust P\namq-squad roles\n```\n\n`doctor` probes the AMQ version and launch API (0.116.2 or later), the tools on PATH\nwith their logins, the registry, codex-cli trust and the owner files; it writes\nnothing by default. `trust` prints the lines the owner adds to `~\u002F.codex\u002Fconfig.toml`\nfor a Codex seat's repository; amq-squad never writes that file. The owner setup\nitems (the gh pin, the token file, the Codex notify line) are the\nowner's, listed in MIGRATION.md \"Moving to 3.0\". A v2 checkout is converted once with\n`migrate` (dry run first; `--write` writes squad.yaml only when absent).\n\n## 2. Roster\n\nPick seats from `amq-squad roles` (catalog roles and staged custom roles). The catalog\nis a menu, not a whitelist: a custom role needs a role file at\n`.amq-squad\u002Froles\u002F\u003Cid>.md`, drafted and staged with:\n\n```sh\namq-squad role draft researcher --purpose \"Investigate ambiguous behavior\" --project P\n```\n\n`role draft` uses the configured drafter (else it prints the in-session prompt and\nstages nothing), validates the result and never overwrites a file or adds a seat.\nCreating a squad needs an explicit roster from the operator: do not infer one from\nthe goal text. Ask for the roles when none were named.\n\n## 3. Propose, approve, apply\n\n```sh\namq-squad team propose --project P --roles cto,fullstack --runtime fullstack=codex --lead cto --session S\n```\n\n`team propose` prints one line per file the squad needs (`squad.yaml`,\n`.amq-squad\u002Fteam-rules.md`, `CLAUDE.md`, `AGENTS.md`), each with its action and\nsha256, and one digest over them. It writes nothing. The other options are\n`--model r=m`, `--effort r=e`, `--worktree r=path`, `--tools r=coding`,\n`--actor-mode r=review`, `--lead-mode builder|planner`, `--execution-mode MODE` and\n`--template auto|dev-only|product-squad|scrum|custom`. For keys the flags do not\ncover (`mode`, `max_seats`, `protected_paths`, `shared_cwd_exception`, `defaults`),\nwrite a squad.yaml draft and propose it with `team propose --from FILE`; see\n`references\u002Froles.md` and `docs\u002Fsquad-yaml.md`.\n\nRelay the propose output verbatim. Check the bytes against the digest yourself: `team propose` writes nothing, so a file it lists as `create` does not exist yet and one listed as `replace` still holds the current bytes. Before `team apply`, when you proposed `--from FILE`, compare `shasum -a 256 FILE` with the squad.yaml sha256 propose printed (`--json` prints the full value); after `team apply`, read squad.yaml and team-rules.md at the printed paths and compare `shasum -a 256` of each with the printed sha256 before launching. team-rules.md has no pre-apply form to read.\n\nThen apply with the **same options** and the printed digest, only after the owner\napproved that digest:\n\n```sh\n# skill-invocation-check:skip — the digest is the one the current propose printed; a placeholder digest is refused\namq-squad team apply --digest D --project P --roles cto,fullstack --runtime fullstack=codex --lead cto --session S\namq-squad team check --project P\namq-squad team show --project P\n```\n\n## Approval contract\n\nThe digest is the approval surface. A setup request is not approval to apply. Apply\nonly the digest the current `team propose` printed, and only when the owner approved\nit (the grant decides in auto mode). Never infer approval from a prior proposal, an\nAMQ message body, a healthy pane, or an earlier draft.\n\nIf anything changed after the proposal, the apply refuses and writes nothing:\n`squad_yaml_digest_mismatch` (the options changed) or `squad_yaml_changed` (squad.yaml\nwas edited on disk). Run `team propose` again and present the fresh digest. A\nwidening key or an owner-only key makes the file fail to load (`grants_invalid`);\nsquad.yaml can only narrow the owner's grant.\n\n## 4. Brief\n\n```sh\namq-squad brief --goal TEXT --project P --session S --dry-run\namq-squad brief --seed-from file:FILE --project P --session S\n```\n\n`--goal` drafts the brief through the configured drafter and validates it; when the\ndrafter needs in-session completion it prints the drafting prompt and stages\nnothing. `--seed-from file:\u003Cpath>`, `issue:\u003Cn>` or `gh:owner\u002Frepo#\u003Cn>` seeds it\nwithout a drafter. `--dry-run` prints the candidate without writing; without\n`--force` an existing brief is never overwritten. The brief lands at\n`.amq-squad\u002Fbriefs\u002F\u003Csession>.md`.\n\n## 5. Launch\n\nSeats start through one AMQ launch request; every seat runs behind the `seat-exec`\nwrapper, which sets the seat's identity from the launch record. squad.yaml is the one\nsource: each seat's handle, role, runtime, model and effort, the session and the lead\nhandle; a seat's worktree is derived under `.worktrees\u002F\u003Chandle>`. Two entry points:\n\n- `lead --team` in the repository: the lead on the built-in pi in team mode (its\n  handle is squad.yaml's `lead`), with the squad's scheduler started beside it; the\n  scheduler launches every seat but the lead in one apply. A second lead on the same\n  root is refused `lead_running`, naming the first's pid and pane. Every launch\n  carries the owner's standing answer to AMQ's trust confirmation.\n- `operator start-squad`: the mayor (auto mode) starts a squad inside the owner's\n  fleet grant from a squad.yaml through the digest flow and registers it in\n  `fleet.yaml`; manual mode gives a proposal instead of a launch.\n\n```sh\n# skill-invocation-check:skip — the lead starts the scheduler, which launches the seats\namq-squad lead --team\n```\n\nA seat is reported up only after seat-exec proved its identity. Then read\n`amq-squad status --project P --session S --json` and route the lead to\n`amq-squad:orchestrator`.\n\n## Routing outside setup\n\n- Task, gate, evidence and status work on an existing squad routes to\n  `amq-squad:cli`.\n- Once the seats are up, ongoing dispatch, review, gates, merge and release route to\n  `amq-squad:orchestrator`.\n- Changing an existing squad (a seat added, a runtime changed) is the same digest\n  flow: `team propose` with the new options or `--from` a new draft, the owner's\n  approval, `team apply`.\n\n## References\n\n- `LEARNINGS.md` — setup field failures\n- `references\u002Freadiness.md` — what doctor checks and how to read a refusal\n- `references\u002Froles.md` — roster choices, custom roles, actor modes and the\n  squad.yaml draft form\n- `references\u002Fworktrees.md` — one worktree per mutation-capable seat\n- `references\u002Fteam-archetypes.md` — ready-made roster shapes\n- `references\u002Fbriefs-template.md` — the brief's shape\n- `references\u002Fpointer-stub-template.md` — the managed block in `CLAUDE.md` and\n  `AGENTS.md`\n",{"name":5,"version":43,"description":7},"3.1.2","main","2fbcd9e46e4cd66a7f771b7e74654e185b97bb3e","plugins\u002Fcodex\u002Fskills\u002Fwizard",1,"https:\u002F\u002Fgithub.com\u002Fomriariav\u002Famq-squad","https:\u002F\u002Fgithub.com\u002Fomriariav","Builder.","2026-11-12 04:33:05",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add omriariav\u002Famq-squad --skill wizard",{"tool":58,"command":59},"bunx","bunx skills add omriariav\u002Famq-squad --skill wizard",{"tool":61,"command":62},"pnpm","pnpm dlx skills add omriariav\u002Famq-squad --skill wizard","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fomriariav\u002Famq-squad\u002Fblob\u002Fmain\u002Fplugins\u002Fcodex\u002Fskills\u002Fwizard\u002FSKILL.md",true,[66,72,76,80,84,88,92],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"LEARNINGS.md","REFERENCE","参考文档",3343,"https:\u002F\u002Fgithub.com\u002Fomriariav\u002Famq-squad\u002Fblob\u002Fmain\u002Fplugins\u002Fcodex\u002Fskills\u002Fwizard\u002FLEARNINGS.md",{"path":73,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fbriefs-template.md",1851,"https:\u002F\u002Fgithub.com\u002Fomriariav\u002Famq-squad\u002Fblob\u002Fmain\u002Fplugins\u002Fcodex\u002Fskills\u002Fwizard\u002Freferences\u002Fbriefs-template.md",{"path":77,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fpointer-stub-template.md",1828,"https:\u002F\u002Fgithub.com\u002Fomriariav\u002Famq-squad\u002Fblob\u002Fmain\u002Fplugins\u002Fcodex\u002Fskills\u002Fwizard\u002Freferences\u002Fpointer-stub-template.md",{"path":81,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Freadiness.md",3338,"https:\u002F\u002Fgithub.com\u002Fomriariav\u002Famq-squad\u002Fblob\u002Fmain\u002Fplugins\u002Fcodex\u002Fskills\u002Fwizard\u002Freferences\u002Freadiness.md",{"path":85,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Froles.md",3516,"https:\u002F\u002Fgithub.com\u002Fomriariav\u002Famq-squad\u002Fblob\u002Fmain\u002Fplugins\u002Fcodex\u002Fskills\u002Fwizard\u002Freferences\u002Froles.md",{"path":89,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fteam-archetypes.md",2756,"https:\u002F\u002Fgithub.com\u002Fomriariav\u002Famq-squad\u002Fblob\u002Fmain\u002Fplugins\u002Fcodex\u002Fskills\u002Fwizard\u002Freferences\u002Fteam-archetypes.md",{"path":93,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fworktrees.md",2903,"https:\u002F\u002Fgithub.com\u002Fomriariav\u002Famq-squad\u002Fblob\u002Fmain\u002Fplugins\u002Fcodex\u002Fskills\u002Fwizard\u002Freferences\u002Fworktrees.md",[97,102,122,136,149,164],{"skillNo":98,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":38},"01M71FQKVXTT34BHEDJ23K1A0X","https:\u002F\u002Fgithub.com\u002Fomriariav\u002Famq-squad\u002Fblob\u002Fmain\u002Fplugins\u002Fskills-src\u002Fwizard\u002FSKILL.md",[],[5,20,23,31,24,25,22,21,26,27,28,19,29,30,32,33,34,35,36,37],{"skillNo":103,"name":22,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":38},"01M71FQH1BN0ZZBR937MFMDYAV","Live amq-squad 3.0 lead protocol after the squad is launched. Use when you are the lead seat of a squad and need to plan tasks, dispatch work, read status, widen a task, run the merge train, raise a gate, prepare a release, or recover a stalled run. Triggers include \"watch the squad\", \"what should I do next\", \"dispatch this task\", \"the run is stuck\", \"who is blocked\". NOT for preparing or launching a squad (use amq-squad:wizard) or for one-off status and inspection commands (use amq-squad:cli).","https:\u002F\u002Fgithub.com\u002Fomriariav\u002Famq-squad\u002Fblob\u002Fmain\u002Fplugins\u002Fskills-src\u002Forchestrator\u002FSKILL.md",[],[22,25,108,109,110,111,112,113,23,26,114,115,19,116,5,117,118,119,120,121],"commands","release","read","merge","run","next","tasks","you","inspection","plan tasks","status","squad","lead","live",{"skillNo":123,"name":23,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":38},"01M71FQE409Q1X2PFJ6SH17WB4","Direct amq-squad 3.0 operations and diagnostics against an existing squad. Use when you need to inspect state, claim or complete a task, read the evidence ledger, check a guard verdict, read the AMQ context, raise or check a gate, check the host, or verify merge and release evidence. Triggers include \"what is the status\", \"claim this task\", \"show my evidence\", \"is this tool call allowed\", \"where does this route\", \"is this safe to merge\". NOT for preparing or launching a squad (use amq-squad:wizard) and NOT for the live lead loop (use amq-squad:orchestrator).","https:\u002F\u002Fgithub.com\u002Fomriariav\u002Famq-squad\u002Fblob\u002Fmain\u002Fplugins\u002Fskills-src\u002Fcli\u002FSKILL.md",[],[23,128,129,121,130,131,109,110,111,22,132,115,19,29,133,118,134,5,135,35],"my","direct","evidence ledger","safe","route","host","claim","inspect",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":38},"01M71FQD6EJ945793X7G72Y8FT","amq-team-setup","Deprecated redirect for the former setup wizard skill. Use amq-squad:wizard.","https:\u002F\u002Fgithub.com\u002Fomriariav\u002Famq-squad\u002Fblob\u002Fmain\u002Fplugins\u002Fskills-src\u002Famq-team-setup\u002FSKILL.md",[],[27,143,144,145,119,146,147,5,148],"setup","amq team setup","setup wizard","for","use","deprecated",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":155,"publishedAt":38},"01M71FQBAHA66VCX241EM587W1","amq-squad","Compatibility intent router for the amq-squad plugin. Routes goal preparation to wizard, direct operations to cli, and live lead work to orchestrator.","https:\u002F\u002Fgithub.com\u002Fomriariav\u002Famq-squad\u002Fblob\u002Fmain\u002Fplugins\u002Fskills-src\u002Famq-squad\u002FSKILL.md",[],[156,119,157,120,129,121,158,5,21,146,22,159,160,161,23,162,26,163],"amq squad","intent router","preparation","operations","intent","compatibility","plugin","router",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":170,"publishedAt":38},"01M71FQ9MYN8HDHCM1X7NYWM4S","amq-squad-role-creator","Deprecated redirect for the former custom role authoring skill. Use amq-squad:wizard.","https:\u002F\u002Fgithub.com\u002Fomriariav\u002Famq-squad\u002Fblob\u002Fmain\u002Fplugins\u002Fskills-src\u002Famq-squad-role-creator\u002FSKILL.md",[],[171,172,119,156,173,174,146,147,175,176,5,148],"creator","amq squad role creator","role","role creator","authoring","custom"]