[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7E6ZR2CFYR0JMHE4V3Y6Y4T":3,"skill-same:01M7E6ZR2CFYR0JMHE4V3Y6Y4T":47},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7E6ZR2CFYR0JMHE4V3Y6Y4T","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.","paramcodes\u002Fostack","paramcodes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F190682747?v=4","01M7E6SGQX3X1GN8QHH9TPRN6Y","Paramveer Singh","01M7E6SGRXBACX52S3T6J2RGCX",1,"MIT","https:\u002F\u002Fgithub.com\u002Fparamcodes\u002Fostack\u002Fblob\u002Fmain\u002Fcontent\u002Fskills\u002Fswarm\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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.\"\n---\n\nThis skill is invoked only via `\u002Fswarm` or an explicit user request. Do not auto-trigger from the description alone.\n\n# Swarm\n\nFan out N parallel cloud workers. They may cover separate slices, race the same brief, or mix both. The parent waits, aggregates, and returns one report.\n\n## Start\n\nWrite one line per phase into `todo.md` at the repository root 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. Set N from the user or derive it from the shape. N is total workers, not the cloud concurrency limit.\n4. Pick the worker model from the `swarm workers` line in `~\u002F.config\u002Fopencode\u002Fpstack-models.json`. If the rule or that line is missing, use `grok-4.7-xhigh-fast`. 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.\n5. 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 as a background batch with `agent: general` and the step 4 model, left unset for `auto` or `inherit-parent`. This harness has no cloud or local environment split: every subagent runs on this machine, so a worker that needs local state already has it. Give each worker its own worktree or output directory so two never write one target.\n\nWhen a worker must start from a non-default pushed branch, pass `cloud_base_branch`.\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\nKeep a compact result table, one-line evidenced issues, and explicit gaps or dropouts.\n\n## Phase D: Report\n\nReturn one consolidated in-chat report with the table, issue one-liners, gaps or dropouts, and the race rule when used.\n","This skill is invoked only via `\u002Fswarm` or an explicit user request. Do not auto-trigger from the description alone.\n\n# Swarm\n\nFan out N parallel cloud workers. They may cover separate slices, race the same brief, or mix both. The parent waits, aggregates, and returns one report.\n\n## Start\n\nWrite one line per phase into `todo.md` at the repository root 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. Set N from the user or derive it from the shape. N is total workers, not the cloud concurrency limit.\n4. Pick the worker model from the `swarm workers` line in `~\u002F.config\u002Fopencode\u002Fpstack-models.json`. If the rule or that line is missing, use `grok-4.7-xhigh-fast`. 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.\n5. 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 as a background batch with `agent: general` and the step 4 model, left unset for `auto` or `inherit-parent`. This harness has no cloud or local environment split: every subagent runs on this machine, so a worker that needs local state already has it. Give each worker its own worktree or output directory so two never write one target.\n\nWhen a worker must start from a non-default pushed branch, pass `cloud_base_branch`.\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\nKeep a compact result table, one-line evidenced issues, and explicit gaps or dropouts.\n\n## Phase D: Report\n\nReturn one consolidated in-chat report with the table, issue one-liners, gaps or dropouts, and the race rule when used.\n",{"name":5,"description":7},"main","6bfc4d0a61ace77dcf2857f34c360cd50ec78604","content\u002Fskills\u002Fswarm",0,"https:\u002F\u002Fgithub.com\u002Fparamcodes\u002Fostack","https:\u002F\u002Fgithub.com\u002Fparamcodes","paramveer.me","on my way to become 1000x engineer","2026-10-06 19:51:22",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add paramcodes\u002Fostack --skill swarm",{"tool":39,"command":40},"bunx","bunx skills add paramcodes\u002Fostack --skill swarm",{"tool":42,"command":43},"pnpm","pnpm dlx skills add paramcodes\u002Fostack --skill swarm","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fparamcodes\u002Fostack\u002Fblob\u002Fmain\u002Fcontent\u002Fskills\u002Fswarm\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7E70AA1SXNZ7MYB8Y5PJ1W0","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\u002Fparamcodes\u002Fostack\u002Fblob\u002Fmain\u002Fcontent\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7E708BD5REN09DTH0AR2M8K","unslop","Cut AI tells from any writing. Must always apply.","https:\u002F\u002Fgithub.com\u002Fparamcodes\u002Fostack\u002Fblob\u002Fmain\u002Fcontent\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7E706HRA328SZJPQBX333W5","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002Fparamcodes\u002Fostack\u002Fblob\u002Fmain\u002Fcontent\u002Fskills\u002Ftypescript-best-practices\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7E701YECJYA8SNV5VX35Z8F","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\u002Fparamcodes\u002Fostack\u002Fblob\u002Fmain\u002Fcontent\u002Fskills\u002Ftechnical-writing\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7E6ZYXGM639ZFDP9Q5CEQW2","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\u002Fparamcodes\u002Fostack\u002Fblob\u002Fmain\u002Fcontent\u002Fskills\u002Fteach\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7E6ZTGNBWCX5CZXASPN2GDG","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\u002Fparamcodes\u002Fostack\u002Fblob\u002Fmain\u002Fcontent\u002Fskills\u002Ftdd\u002FSKILL.md",[],[]]