[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DDCYHCY2XAYN11FBPDWN41":3,"skill-same:01M6DDCYHCY2XAYN11FBPDWN41":69},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":14,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":54,"install":55,"resources":68},"01M6DDCYHCY2XAYN11FBPDWN41","orchestration-patterns",null,"Use when orchestrating a multi-agent or multi-step coding workflow and you need the proven cross-vendor patterns for THIS Windows workspace - the Architect-to-Editor split (an Opus architect emits a typed change-spec, Codex applies it via the mounted codex mcp-server rail, cross-vendor diversity per work-unit), the sandbox ladder (route risky or untrusted exec to WSL2 native, the docker MCP, or a modal_sandbox, because Windows has no native OS-level process sandbox, the constraint that kills a naive local-sandbox build), a Serena-seeded PageRank repo-map (rank the most central symbols by running PageRank over the mounted Serena LSP reference edges, no tree-sitter pipeline and no vector store), Goose-style lead\u002Fworker failure-threshold escalation (on N worker failures escalate to the lead for re-decomposition instead of grinding), and a per-edit lint ladder capped at max_reflections=3 (changed-file-only lint, escalate not grind). Triggers include split architect and editor across models, route risky exec to a sandbox, build a repo map without embeddings, cap agent retries, escalate a stuck work-unit, or design the orchestration loop. NOT for wiring the Codex fan-out channel itself (use multi-ai-mingle) or picking among finished candidate patches (use execution-grounded-bon).","Prekzursil\u002Fagent-skills-toolchain","Prekzursil","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54636077?v=4","01M6DACZ1PCQHD99SCR1YXG28B","Andrei Mihai Visalon","01M6DACZ670WZF535V3WYYSS4Z",0,"MIT","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Fplatform\u002Frouting\u002Ffixtures\u002Fhome\u002F.claude\u002Fskills\u002Forchestration-patterns\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"orchestration patterns","orchestration","patterns","only","worker","local","across","map","lsp","route","cap","design","work","loop","pipeline","server","vector","change","workflow","MCP","2026-11-10 10:12:30",false,"---\nname: orchestration-patterns\ndescription: Use when orchestrating a multi-agent or multi-step coding workflow and you need the proven cross-vendor patterns for THIS Windows workspace - the Architect-to-Editor split (an Opus architect emits a typed change-spec, Codex applies it via the mounted codex mcp-server rail, cross-vendor diversity per work-unit), the sandbox ladder (route risky or untrusted exec to WSL2 native, the docker MCP, or a modal_sandbox, because Windows has no native OS-level process sandbox, the constraint that kills a naive local-sandbox build), a Serena-seeded PageRank repo-map (rank the most central symbols by running PageRank over the mounted Serena LSP reference edges, no tree-sitter pipeline and no vector store), Goose-style lead\u002Fworker failure-threshold escalation (on N worker failures escalate to the lead for re-decomposition instead of grinding), and a per-edit lint ladder capped at max_reflections=3 (changed-file-only lint, escalate not grind). Triggers include split architect and editor across models, route risky exec to a sandbox, build a repo map without embeddings, cap agent retries, escalate a stuck work-unit, or design the orchestration loop. NOT for wiring the Codex fan-out channel itself (use multi-ai-mingle) or picking among finished candidate patches (use execution-grounded-bon).\n---\n\n# orchestration-patterns\n\nFive orchestration patterns that ride the **already-mounted bus** on this Windows 11 machine\n(codex mcp-server, Serena LSP, the docker + cloud-hub\u002Fmodal MCPs, WSL2, the smallest-check\nladder). They are **advisory patterns Claude applies while orchestrating** — not a new runtime,\nnot a new gate, not a hook. Every one deliberately re-uses existing infrastructure rather than\nbuilding a parallel stack (the anti-overfit gate: no 2nd orchestration runtime, no vector\u002FKG\nmemory engine, no tree-sitter chunker, no local sandbox build, no trained router).\n\n## When to use\n- You are decomposing work into agents \u002F work-units and want the cross-vendor, Windows-correct\n  shape for the loop (who plans, who edits, where risky code runs, how the loop stops grinding).\n- You need a repo map \u002F context bundle **without** embeddings or a tree-sitter pipeline.\n- A work-unit is stuck and you must decide \"retry vs escalate vs re-decompose\".\n\n## When NOT to use\n- Wiring the Codex fan-out channel or the agent-mail back-channel itself → **`multi-ai-mingle`**.\n- Choosing among several *finished* candidate patches → **`execution-grounded-bon`** (execution\n  consensus), not this skill.\n- Running the smallest test for a diff in isolation → **`smallest-check-ladder`** (this skill\n  only wires its L0 into the per-edit loop).\n\n## The bus these ride (no new runtime)\n| Pattern | Existing rail it rides | New infra? |\n|---|---|---|\n| Architect→Editor split | `mcp__codex__codex` (mounted codex mcp-server) | none |\n\n### Pattern 1 — Architect→Editor split (cross-vendor per work-unit)\n### Pattern 2 — Sandbox ladder (the Windows constraint that kills the naive build)\n### Pattern 3 — Serena-seeded PageRank repo-map (no tree-sitter, no vector)\n### Pattern 4 — Goose-style lead\u002Fworker failure-threshold escalation\n### Pattern 5 — Per-edit lint ladder + reflection cap (max_reflections=3)\n### Shadow-mode \u002F advisory posture (council C5)\n### Anti-overfit boundary (what this deliberately does NOT build)\n### Testing \u002F real proof (how this file was validated)\n### Evidence\n","# orchestration-patterns\n\nFive orchestration patterns that ride the **already-mounted bus** on this Windows 11 machine\n(codex mcp-server, Serena LSP, the docker + cloud-hub\u002Fmodal MCPs, WSL2, the smallest-check\nladder). They are **advisory patterns Claude applies while orchestrating** — not a new runtime,\nnot a new gate, not a hook. Every one deliberately re-uses existing infrastructure rather than\nbuilding a parallel stack (the anti-overfit gate: no 2nd orchestration runtime, no vector\u002FKG\nmemory engine, no tree-sitter chunker, no local sandbox build, no trained router).\n\n## When to use\n- You are decomposing work into agents \u002F work-units and want the cross-vendor, Windows-correct\n  shape for the loop (who plans, who edits, where risky code runs, how the loop stops grinding).\n- You need a repo map \u002F context bundle **without** embeddings or a tree-sitter pipeline.\n- A work-unit is stuck and you must decide \"retry vs escalate vs re-decompose\".\n\n## When NOT to use\n- Wiring the Codex fan-out channel or the agent-mail back-channel itself → **`multi-ai-mingle`**.\n- Choosing among several *finished* candidate patches → **`execution-grounded-bon`** (execution\n  consensus), not this skill.\n- Running the smallest test for a diff in isolation → **`smallest-check-ladder`** (this skill\n  only wires its L0 into the per-edit loop).\n\n## The bus these ride (no new runtime)\n| Pattern | Existing rail it rides | New infra? |\n|---|---|---|\n| Architect→Editor split | `mcp__codex__codex` (mounted codex mcp-server) | none |\n\n### Pattern 1 — Architect→Editor split (cross-vendor per work-unit)\n### Pattern 2 — Sandbox ladder (the Windows constraint that kills the naive build)\n### Pattern 3 — Serena-seeded PageRank repo-map (no tree-sitter, no vector)\n### Pattern 4 — Goose-style lead\u002Fworker failure-threshold escalation\n### Pattern 5 — Per-edit lint ladder + reflection cap (max_reflections=3)\n### Shadow-mode \u002F advisory posture (council C5)\n### Anti-overfit boundary (what this deliberately does NOT build)\n### Testing \u002F real proof (how this file was validated)\n### Evidence\n",{"name":5,"description":7},"main","a298c929b6cbd662e1fce54302ce520d5ceea1a5","platform\u002Frouting\u002Ffixtures\u002Fhome\u002F.claude\u002Fskills\u002Forchestration-patterns","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain","https:\u002F\u002Fgithub.com\u002FPrekzursil","2026-11-02 14:30:57",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add Prekzursil\u002Fagent-skills-toolchain --skill orchestration-patterns",{"tool":61,"command":62},"bunx","bunx skills add Prekzursil\u002Fagent-skills-toolchain --skill orchestration-patterns",{"tool":64,"command":65},"pnpm","pnpm dlx skills add Prekzursil\u002Fagent-skills-toolchain --skill orchestration-patterns","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Fplatform\u002Frouting\u002Ffixtures\u002Fhome\u002F.claude\u002Fskills\u002Forchestration-patterns\u002FSKILL.md",true,[],[70,92,116,143,157,172],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":44},"01M6DF7D7478R55P46REYH4QAC","clarify-requirements","Resolve genuine pre-execution ambiguity by scanning repo context, generating 1-6 grounded options, and asking 1-3 focused questions via AskUserQuestion. NOT for mid-task use (injection risk); NOT when the goal is already unambiguous; use to disambiguate vague prompts before any file edits.","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Fworkspace-hooks\u002Fskills\u002Fclarify-requirements\u002FSKILL.md",[],[77,78,79,80,81,82,83,84,85,86,87,88,89,90,91],"clarify requirements","clarify","requirements","risk","options","task","prompts","goal","scanning","use","context","repo","injection","execution","file",{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":99,"publishedAt":44},"01M6DF79CA4BHJS66J8EZDBPWJ","openmm-md","Run FREE, open-source, Windows-native GPU molecular dynamics via the openmm-md MCP (OpenMM + CUDA on the local NVIDIA GPU). Use for protein \u002F protein-ligand MD when you want a free stack or are on Windows without a Schrodinger license. Covers the full workflow (prepare, solvate, minimize, equilibrate, production, analyze, mmgbsa) AND an honest decision guide vs Schrodinger Desmond, including how to run Desmond legitimately on Linux or a cloud GPU with a real license. This is a deliberately LESSER free alternative and does NOT replace the schrodinger MCP tools. Do NOT use it to pick a free tool when a validated FEP+, WaterMap, IFD-MD, or Prime MM-GBSA result is actually required.","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Fmcp\u002Fopenmm-md-mcp\u002Fskill\u002Fopenmm-md\u002FSKILL.md",[98],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[100,101,102,103,104,105,106,107,108,109,110,111,42,112,86,113,114,29,115,43],"openmm md","how","decision","pick","linux","analyze","tool","stack","open","NVIDIA","gpu","license","windows","free","molecular dynamics","do",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":128,"publishedAt":44},"01M6DF76C1MG85VEWP8VZCBNMN","visual-review","Take screenshots of web pages and UI using Playwright for visual review and iteration","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Feditor\u002Fmetaswarm\u002Fskills\u002Fvisual-review\u002FSKILL.md",[122,125],{"categoryNo":123,"categoryName":124,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":126,"categoryName":127,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[129,130,131,132,133,134,135,136,137,138,101,139,140,141,142],"review","visual","visual review","pages","web","false","iteration","take","check","slides","ui","screenshot","playwright","screenshots",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":44},"01M6DF73AQVCBZKEN0YXEX9FXP","status","Diagnostic status report — shows metaswarm installation state, project setup, and potential issues","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Feditor\u002Fmetaswarm\u002Fskills\u002Fstatus\u002FSKILL.md",[],[145,150,151,152,153,154,155,156],"setup","report","project","installation","project setup","issues","state",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":164,"publishedAt":44},"01M6DF6X6C2XB0P6GX76P7TTYV","start","Use when starting work on any task, when the user mentions metaswarm, or when the user wants to begin tracked development work","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Feditor\u002Fmetaswarm\u002Fskills\u002Fstart\u002FSKILL.md",[163],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[159,165,82,166,167,168,86,169,36,170,171],"start issue","issue","ready","work on issue","user","work on","development",{"skillNo":173,"name":150,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":177,"publishedAt":44},"01M6DF6QMJ9AJKFKHHKRT005PQ","Interactive project setup — detects your project, configures metaswarm, writes project-local files","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Feditor\u002Fmetaswarm\u002Fskills\u002Fsetup\u002FSKILL.md",[],[150,152,29,178,154,179],"files","interactive"]