[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B2B9X2XZVM205A67PR9KHC":3,"skill-same:01M7B2B9X2XZVM205A67PR9KHC":46},{"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":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7B2B9X2XZVM205A67PR9KHC","arena",null,"Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for \u002Farena, 'arena this', 'throw it in the arena', or when one attempt at a non-trivial artifact would lock in the wrong shape.","ericlitman\u002Fopen-pstack","ericlitman","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F28211?v=4","01M7B2AZ3FNHC7ZM10GTT91Z8A","Eric Litman","01M7B2AZ42W4C26WEE3Y12YHC4",574,"MIT","https:\u002F\u002Fgithub.com\u002Fericlitman\u002Fopen-pstack\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Farena\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: arena\ndescription: \"Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for \u002Farena, 'arena this', 'throw it in the arena', or when one attempt at a non-trivial artifact would lock in the wrong shape.\"\n---\n\n# Arena\n\n**Dispatch contract.** Read [`provider-dispatch.md`](..\u002Fpoteto-mode\u002Freferences\u002Fprovider-dispatch.md) before fan-out. Configured values are provider-qualified descriptors, not host-native model slugs. The parent starts native and external lanes directly; children never route themselves. On Codex, resolve the remaining Claude tool names via [`codex-tools.md`](..\u002Fpoteto-mode\u002Freferences\u002Fcodex-tools.md).\n\nOpen a todolist with one entry per phase (Frame, Fan out, Cross-judge, Pick, Graft, Verify) before launching anything.\n\n## Phase A: Frame\n\nEvery candidate gets the same prompt, so the prompt is the contract.\n\n1. State the artifact each candidate is producing.\n2. Derive the rubric, 3-6 concrete gradeable criteria for what success looks like on *this* task. It is the picker's tool in Phase D. Candidates only see the task.\n3. Pick the runners. Use `arena runners` from the current harness's pstack model sheet when present. Otherwise use its [role default](..\u002Fpoteto-mode\u002Freferences\u002Fmodel-catalog.md#role-defaults), one runner per entry. Spawn more runners when the arena covers multiple design directions. Use the same descriptor N times when the work is generation-bound rather than judgment-sensitive. Pick each subagent's effort for the job, per the Subagents section of the **poteto-mode** skill.\n4. Give each candidate its own output location (a git worktree where possible, otherwise `\u002Ftmp\u002Farena-\u003Cslug>\u002Fcandidate-\u003Cn>\u002F`), per the **separate-before-serializing-shared-state** principle skill.\n\n## Phase B: Fan out\n\nStart all N lanes in one fan-out phase through the provider-dispatch contract. Native lanes are background subagents. External lanes are direct background launcher processes with retained task\u002Fsession handles, never foreground calls and never subagents supervising subprocesses. Give every lane the task, the path to the shared grounding, its own output path, and instructions to produce the artifact and a short rationale naming the alternatives it considered and what it rejected.\n\nAn external lane counts only when its receipt says `complete` and carries either a matching `provider-report` or Codex's exact `pinned-argv` evidence; a native lane counts when its tool transcript returns the assigned model's result. If a candidate fails, proceed with N-1 and note the exact dropout in the synthesis record. Never replace it with another provider silently.\n\n## Phase C: Cross-judge\n\nAfter all Phase B candidates complete, choose the judge from `arena cross-judge pool` in the current harness's pstack model sheet when present, otherwise from the runner defaults above. The judge is never from the parent's provider. Walk the pool in order and take the first entry from another provider that runs. An `auto` or `inherit-parent` entry is the parent model, so it never judges. An entry that does not run is a dropout: do not try a substitute slug or the default pool for it. If no entry runs, skip the judge, pick the base alone in Phase D, and say so in the output. Dispatch one read-only judge through the provider contract. It sees the rubric and the candidates by path label, scores each criterion, and recommends a base with rationale. It runs in parallel with your reading in Phase D. Don't dispatch it while candidates are still writing.\n\n## Phase D: Pick a base\n\nRead every candidate end to end before picking. Score each against the rubric criterion by criterion, not on holistic feel, and compare with the cross-judge when Phase C ran one. Agreement on the base confirms the pick. Disagreement means one of you is biased or the rubric was ambiguous. Read both rationales before deciding.\n\nPick the base a future maintainer can extend most easily without breaking invariants. When two feel tied, prefer the cleaner boundary or smaller API, per the Laziness Protocol.\n\n## Phase E: Graft\n\nWalk each losing candidate once more for what is worth porting into the base, usually one or two things per candidate, not most of it. Fold each graft in by hand, per the **redesign-from-first-principles** principle skill, so the result stays coherent under one mental model. Don't paste mechanically.\n\nIf the candidates converge on one shape, that is strong agreement. Note it and ship the consensus shape. No graft is needed. If they wildly diverge, Phase A was under-specified. Reframe and re-run rather than averaging the divergence.\n\n## Phase F: Verify\n\nVerify the synthesized artifact like any other output, per the **prove-it-works** principle skill. If verification finds a problem the arena missed, either Phase A was wrong (re-frame and re-run) or a candidate caught it and you missed the graft (go back to Phase E). Don't paper over it.\n\n## Outputs\n\nOne synthesized artifact, with a short synthesis note alongside naming the base and why, the cross-judge's verdict or that Phase C skipped the judge, each graft with its source candidate, what was rejected and why, any convergence or dropouts, and the verification result.\n","# Arena\n\n**Dispatch contract.** Read [`provider-dispatch.md`](..\u002Fpoteto-mode\u002Freferences\u002Fprovider-dispatch.md) before fan-out. Configured values are provider-qualified descriptors, not host-native model slugs. The parent starts native and external lanes directly; children never route themselves. On Codex, resolve the remaining Claude tool names via [`codex-tools.md`](..\u002Fpoteto-mode\u002Freferences\u002Fcodex-tools.md).\n\nOpen a todolist with one entry per phase (Frame, Fan out, Cross-judge, Pick, Graft, Verify) before launching anything.\n\n## Phase A: Frame\n\nEvery candidate gets the same prompt, so the prompt is the contract.\n\n1. State the artifact each candidate is producing.\n2. Derive the rubric, 3-6 concrete gradeable criteria for what success looks like on *this* task. It is the picker's tool in Phase D. Candidates only see the task.\n3. Pick the runners. Use `arena runners` from the current harness's pstack model sheet when present. Otherwise use its [role default](..\u002Fpoteto-mode\u002Freferences\u002Fmodel-catalog.md#role-defaults), one runner per entry. Spawn more runners when the arena covers multiple design directions. Use the same descriptor N times when the work is generation-bound rather than judgment-sensitive. Pick each subagent's effort for the job, per the Subagents section of the **poteto-mode** skill.\n4. Give each candidate its own output location (a git worktree where possible, otherwise `\u002Ftmp\u002Farena-\u003Cslug>\u002Fcandidate-\u003Cn>\u002F`), per the **separate-before-serializing-shared-state** principle skill.\n\n## Phase B: Fan out\n\nStart all N lanes in one fan-out phase through the provider-dispatch contract. Native lanes are background subagents. External lanes are direct background launcher processes with retained task\u002Fsession handles, never foreground calls and never subagents supervising subprocesses. Give every lane the task, the path to the shared grounding, its own output path, and instructions to produce the artifact and a short rationale naming the alternatives it considered and what it rejected.\n\nAn external lane counts only when its receipt says `complete` and carries either a matching `provider-report` or Codex's exact `pinned-argv` evidence; a native lane counts when its tool transcript returns the assigned model's result. If a candidate fails, proceed with N-1 and note the exact dropout in the synthesis record. Never replace it with another provider silently.\n\n## Phase C: Cross-judge\n\nAfter all Phase B candidates complete, choose the judge from `arena cross-judge pool` in the current harness's pstack model sheet when present, otherwise from the runner defaults above. The judge is never from the parent's provider. Walk the pool in order and take the first entry from another provider that runs. An `auto` or `inherit-parent` entry is the parent model, so it never judges. An entry that does not run is a dropout: do not try a substitute slug or the default pool for it. If no entry runs, skip the judge, pick the base alone in Phase D, and say so in the output. Dispatch one read-only judge through the provider contract. It sees the rubric and the candidates by path label, scores each criterion, and recommends a base with rationale. It runs in parallel with your reading in Phase D. Don't dispatch it while candidates are still writing.\n\n## Phase D: Pick a base\n\nRead every candidate end to end before picking. Score each against the rubric criterion by criterion, not on holistic feel, and compare with the cross-judge when Phase C ran one. Agreement on the base confirms the pick. Disagreement means one of you is biased or the rubric was ambiguous. Read both rationales before deciding.\n\nPick the base a future maintainer can extend most easily without breaking invariants. When two feel tied, prefer the cleaner boundary or smaller API, per the Laziness Protocol.\n\n## Phase E: Graft\n\nWalk each losing candidate once more for what is worth porting into the base, usually one or two things per candidate, not most of it. Fold each graft in by hand, per the **redesign-from-first-principles** principle skill, so the result stays coherent under one mental model. Don't paste mechanically.\n\nIf the candidates converge on one shape, that is strong agreement. Note it and ship the consensus shape. No graft is needed. If they wildly diverge, Phase A was under-specified. Reframe and re-run rather than averaging the divergence.\n\n## Phase F: Verify\n\nVerify the synthesized artifact like any other output, per the **prove-it-works** principle skill. If verification finds a problem the arena missed, either Phase A was wrong (re-frame and re-run) or a candidate caught it and you missed the graft (go back to Phase E). Don't paper over it.\n\n## Outputs\n\nOne synthesized artifact, with a short synthesis note alongside naming the base and why, the cross-judge's verdict or that Phase C skipped the judge, each graft with its source candidate, what was rejected and why, any convergence or dropouts, and the verification result.\n",{"name":5,"description":7},"main","faf512125b11f4a30f55c4eaf8a709a890668406","plugins\u002Fpstack\u002Fskills\u002Farena",90,"https:\u002F\u002Fgithub.com\u002Fericlitman\u002Fopen-pstack","https:\u002F\u002Fgithub.com\u002Fericlitman","Serial optimist, mirth-maker, founder @Healthspanners & @Aescape.","2026-11-09 04:25:18",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add ericlitman\u002Fopen-pstack --skill arena",{"tool":38,"command":39},"bunx","bunx skills add ericlitman\u002Fopen-pstack --skill arena",{"tool":41,"command":42},"pnpm","pnpm dlx skills add ericlitman\u002Fopen-pstack --skill arena","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fericlitman\u002Fopen-pstack\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Farena\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7B2GYDDVFEN1DMHMX8Y300Q","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\u002Fericlitman\u002Fopen-pstack\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7B2GWWKF0ENYRGW6KVAX272","what-did-i-get-done","Summarize authored commits over a user-specified time period into a concise update","https:\u002F\u002Fgithub.com\u002Fericlitman\u002Fopen-pstack\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Fwhat-did-i-get-done\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7B2GVK21EBZQ40EEA9BHDJF","unslop","Cut AI tells from any writing.","https:\u002F\u002Fgithub.com\u002Fericlitman\u002Fopen-pstack\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7B2GT41DP2XC4AJYSNF0A74","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002Fericlitman\u002Fopen-pstack\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Ftypescript-best-practices\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7B2GQ6HNZNB9R2WJNQ7TS9H","thermo-nuclear-code-quality-review","Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.","https:\u002F\u002Fgithub.com\u002Fericlitman\u002Fopen-pstack\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Fthermo-nuclear-code-quality-review\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7B2GM0NRQN7X5R9K60BZS0D","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\u002Fericlitman\u002Fopen-pstack\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Ftechnical-writing\u002FSKILL.md",[],[]]