[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FCC3J28WFHT1EMR1DZKNGW":3,"skill-same:01M7FCC3J28WFHT1EMR1DZKNGW":44},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":43},"01M7FCC3J28WFHT1EMR1DZKNGW","swarm",null,"Fan out N parallel workers, drain them, and return one report. Use for \u002Fswarm, 'swarm this', or parallel coverage, races, gauntlets, and exploration.","chinlung\u002Fpi-pstack","chinlung","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F696924?v=4","01M7FC70KK37NN6FE15PYSFZPD","SCL","01M7FC70M6AD8EN4NSGZ2BJ7M1",0,"MIT","https:\u002F\u002Fgithub.com\u002Fchinlung\u002Fpi-pstack\u002Fblob\u002Fmain\u002Fskills\u002Fswarm\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: swarm\ndescription: \"Fan out N parallel workers, drain them, and return one report. Use for \u002Fswarm, 'swarm this', or parallel coverage, races, gauntlets, and exploration.\"\ndisable-model-invocation: true\n---\n\n# Swarm\n\nIn Pi, read [the Pi adapter](..\u002F..\u002Fdocs\u002Fharness\u002Fpi.md) once per session before you follow this skill. It maps the Cursor names in pstack skills to Pi.\n\n## Start\n\nOpen a checklist with one entry per phase before launching anything.\n\n1. Frame\n2. Fan out\n3. Aggregate\n4. Report\n\n## Phase A: Frame\n\n1. State the done predicate and the artifact or report the swarm must return.\n2. Choose the shape. Partition into slices, race N workers on identical briefs, or mix both. For a race or mixed shape, declare `first pass`, `rank all`, or `best-of` before spawning.\n3. Pick the worker model from the `swarm workers` line in the pstack role map (the `pstack_models` tool returns it). If the rule or that line is missing, use the role map's entry for that role. For `auto` or `inherit-parent`, omit `model` so the workers run on the parent model. If the `subagent` tool rejects a slug, use the default and say so. If it rejects the default, use the closest valid slug of the same family from its error message. For a model race, name each arm's model up front. Pick each subagent's reasoning level and fast or standard speed for the job, per the Subagents section of the **poteto-mode** skill.\n4. Give each worker its own writable output when it writes. When workers verify or measure commits, each brief names the exact SHAs. A measurement brief also names the method (sample count, what one sample is, order). The worker records both in its result.\n\n## Phase B: Fan out\n\nSpawn all N workers in one message with `agent: \"delegate\"`, `worktree: true`, `async: true`, and the step 3 model, left unset for `auto` or `inherit-parent`. Use no `worktree` flag only when the worker needs access to something on the user's computer.\n\nWhen a worker must start from a non-default pushed branch, tell the worker which branch to check out.\n\nEvery brief stands alone. Include the goal, scope, exact slice or race arm, how to verify, and what to report. Reports use `PASS`, `ISSUES`, or `BLOCKED` with evidence. A worker that can prove a defect reports `ISSUES` and lists every issue it can prove, not only the first.\n\nIf a worker drops out, proceed with N-1 and note it.\n\n## Phase C: Aggregate\n\nRead the terminal results. Drop a result that does not record the SHAs and method its brief names, and respawn that worker once. After a second miss, record a gap. A gap does not count as a pass. For coverage, every required slice needs a result. For a race, apply the selection rule declared up front. Use first pass, rank all, or best-of. Do not paste raw worker dumps.\n\n## Phase D: Report\n\nReturn one consolidated in-chat report with a result table, issue one-liners, gaps or dropouts, and the race rule when used.\n","# Swarm\n\nIn Pi, read [the Pi adapter](..\u002F..\u002Fdocs\u002Fharness\u002Fpi.md) once per session before you follow this skill. It maps the Cursor names in pstack skills to Pi.\n\n## Start\n\nOpen a checklist with one entry per phase before launching anything.\n\n1. Frame\n2. Fan out\n3. Aggregate\n4. Report\n\n## Phase A: Frame\n\n1. State the done predicate and the artifact or report the swarm must return.\n2. Choose the shape. Partition into slices, race N workers on identical briefs, or mix both. For a race or mixed shape, declare `first pass`, `rank all`, or `best-of` before spawning.\n3. Pick the worker model from the `swarm workers` line in the pstack role map (the `pstack_models` tool returns it). If the rule or that line is missing, use the role map's entry for that role. For `auto` or `inherit-parent`, omit `model` so the workers run on the parent model. If the `subagent` tool rejects a slug, use the default and say so. If it rejects the default, use the closest valid slug of the same family from its error message. For a model race, name each arm's model up front. Pick each subagent's reasoning level and fast or standard speed for the job, per the Subagents section of the **poteto-mode** skill.\n4. Give each worker its own writable output when it writes. When workers verify or measure commits, each brief names the exact SHAs. A measurement brief also names the method (sample count, what one sample is, order). The worker records both in its result.\n\n## Phase B: Fan out\n\nSpawn all N workers in one message with `agent: \"delegate\"`, `worktree: true`, `async: true`, and the step 3 model, left unset for `auto` or `inherit-parent`. Use no `worktree` flag only when the worker needs access to something on the user's computer.\n\nWhen a worker must start from a non-default pushed branch, tell the worker which branch to check out.\n\nEvery brief stands alone. Include the goal, scope, exact slice or race arm, how to verify, and what to report. Reports use `PASS`, `ISSUES`, or `BLOCKED` with evidence. A worker that can prove a defect reports `ISSUES` and lists every issue it can prove, not only the first.\n\nIf a worker drops out, proceed with N-1 and note it.\n\n## Phase C: Aggregate\n\nRead the terminal results. Drop a result that does not record the SHAs and method its brief names, and respawn that worker once. After a second miss, record a gap. A gap does not count as a pass. For coverage, every required slice needs a result. For a race, apply the selection rule declared up front. Use first pass, rank all, or best-of. Do not paste raw worker dumps.\n\n## Phase D: Report\n\nReturn one consolidated in-chat report with a result table, issue one-liners, gaps or dropouts, and the race rule when used.\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","33efbcc2e2adf18daa64a5fb25f4acc2b793934f","skills\u002Fswarm","https:\u002F\u002Fgithub.com\u002Fchinlung\u002Fpi-pstack","https:\u002F\u002Fgithub.com\u002Fchinlung","2026-11-13 05:25:09",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":24},[33,36,39],{"tool":34,"command":35},"npx","npx skills add chinlung\u002Fpi-pstack --skill swarm",{"tool":37,"command":38},"bunx","bunx skills add chinlung\u002Fpi-pstack --skill swarm",{"tool":40,"command":41},"pnpm","pnpm dlx skills add chinlung\u002Fpi-pstack --skill swarm","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fchinlung\u002Fpi-pstack\u002Fblob\u002Fmain\u002Fskills\u002Fswarm\u002FSKILL.md",[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":19},"01M7FCJD85PKWYNRB7ME57GF6X","why","Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.","https:\u002F\u002Fgithub.com\u002Fchinlung\u002Fpi-pstack\u002Fblob\u002Fmain\u002Fupstream\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7FCJA8WYNVGYP7TABXXPWZ6","unslop","Cut AI tells from any writing.","https:\u002F\u002Fgithub.com\u002Fchinlung\u002Fpi-pstack\u002Fblob\u002Fmain\u002Fupstream\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7FCJ76BHPVWF4583V7SYBE2","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002Fchinlung\u002Fpi-pstack\u002Fblob\u002Fmain\u002Fupstream\u002Fskills\u002Ftypescript-best-practices\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7FCJ3M78YVZTRAHW9EDACSN","technical-writing","Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for \u002Ftechnical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.","https:\u002F\u002Fgithub.com\u002Fchinlung\u002Fpi-pstack\u002Fblob\u002Fmain\u002Fupstream\u002Fskills\u002Ftechnical-writing\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7FCJ04VJRBF2EYQX2268B20","teach","Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.","https:\u002F\u002Fgithub.com\u002Fchinlung\u002Fpi-pstack\u002Fblob\u002Fmain\u002Fupstream\u002Fskills\u002Fteach\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7FCHWHTS5C05PKY2FFVD134","tdd","Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.","https:\u002F\u002Fgithub.com\u002Fchinlung\u002Fpi-pstack\u002Fblob\u002Fmain\u002Fupstream\u002Fskills\u002Ftdd\u002FSKILL.md",[],[]]