[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CX8T6B4R0SX6CZN1ZGP3M5":3,"skill-same:01M7CX8T6B4R0SX6CZN1ZGP3M5":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":45},"01M7CX8T6B4R0SX6CZN1ZGP3M5","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.","BotHarness\u002FDeepSeekBot","BotHarness","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F330270786?v=4","01M7CX37EXWM53FHAQ28JNKZTZ","01M7CX37FHA8NY5D2KXFZWV63Y",852,"MIT","https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot\u002Fblob\u002Fmain\u002F.agents\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.\"\ndisable-model-invocation: true\n---\n\n# Arena\n\nIn Claude Code, read [the Claude Code adapter](..\u002F..\u002Fdocs\u002Fharness\u002Fclaude-code.md) once per session before you follow this skill. It maps the Cursor names in pstack skills to Claude Code.\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 the `arena runners` line in `~\u002F.cursor\u002Frules\u002Fpstack-models.mdc`. If the rule or that line is missing, default to one each on `claude-opus-5-5-xhigh` and `grok-4.7-xhigh-fast`. An `auto` or `inherit-parent` entry in this line or the cross-judge line means the parent model, so omit `model` for it. If the Task tool rejects a configured entry, run that seat on its family's default and say so. Families go by prefix: `claude-*`, and `grok-*` with `cursor-grok-*` and `composer-*`. A refused `composer-*` entry runs on `grok-4.7-xhigh-fast`. With no family match, use `claude-opus-5-5-xhigh`. If it rejects a default, use the closest valid slug of the same family from its error message. Spawn more runners when the arena covers multiple design directions. Use the same model N times when the work is generation-bound rather than judgment-sensitive. 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 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\nSpawn all N subagents in one message with `run_in_background: true`, each with 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\nIf a candidate produces no output, proceed with N-1 and note the dropout.\n\n## Phase C: Cross-judge\n\nAfter all Phase B candidates complete, choose one model from the `arena cross-judge pool` line in `~\u002F.cursor\u002Frules\u002Fpstack-models.mdc`. If the rule or that line is missing, choose from `claude-opus-5-5-xhigh` and `grok-4.7-xhigh-fast`. Prefer a different model family from the parent's. Spawn one readonly judge subagent on that model. 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 spawn 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. 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, each graft with its source candidate, what was rejected and why, any convergence or dropouts, and the verification result.\n","# Arena\n\nIn Claude Code, read [the Claude Code adapter](..\u002F..\u002Fdocs\u002Fharness\u002Fclaude-code.md) once per session before you follow this skill. It maps the Cursor names in pstack skills to Claude Code.\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 the `arena runners` line in `~\u002F.cursor\u002Frules\u002Fpstack-models.mdc`. If the rule or that line is missing, default to one each on `claude-opus-5-5-xhigh` and `grok-4.7-xhigh-fast`. An `auto` or `inherit-parent` entry in this line or the cross-judge line means the parent model, so omit `model` for it. If the Task tool rejects a configured entry, run that seat on its family's default and say so. Families go by prefix: `claude-*`, and `grok-*` with `cursor-grok-*` and `composer-*`. A refused `composer-*` entry runs on `grok-4.7-xhigh-fast`. With no family match, use `claude-opus-5-5-xhigh`. If it rejects a default, use the closest valid slug of the same family from its error message. Spawn more runners when the arena covers multiple design directions. Use the same model N times when the work is generation-bound rather than judgment-sensitive. 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 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\nSpawn all N subagents in one message with `run_in_background: true`, each with 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\nIf a candidate produces no output, proceed with N-1 and note the dropout.\n\n## Phase C: Cross-judge\n\nAfter all Phase B candidates complete, choose one model from the `arena cross-judge pool` line in `~\u002F.cursor\u002Frules\u002Fpstack-models.mdc`. If the rule or that line is missing, choose from `claude-opus-5-5-xhigh` and `grok-4.7-xhigh-fast`. Prefer a different model family from the parent's. Spawn one readonly judge subagent on that model. 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 spawn 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. 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, each graft with its source candidate, what was rejected and why, any convergence or dropouts, and the verification result.\n",{"name":5,"description":7,"disable-model-invocation":23},true,"main","d922e716d0801fbdf6c27f023b245c8da7e4c804",".agents\u002Fskills\u002Farena",63,"https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot","https:\u002F\u002Ftobs.app","https:\u002F\u002Fgithub.com\u002FBotHarness","https:\u002F\u002Fdeepseekbot.app\u002F","2026-11-15 06:17:31",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":23},[35,38,41],{"tool":36,"command":37},"npx","npx skills add BotHarness\u002FDeepSeekBot --skill arena",{"tool":39,"command":40},"bunx","bunx skills add BotHarness\u002FDeepSeekBot --skill arena",{"tool":42,"command":43},"pnpm","pnpm dlx skills add BotHarness\u002FDeepSeekBot --skill arena","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Farena\u002FSKILL.md",[],[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":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M7CY5WHFGASZATK5CQF05G0A","slide-authoring","Technical reference for writing or editing open-slide pages — file contract, 1920×1080 canvas, type scale, layout, palette\u002Fvisual direction, assets, speaker notes, stepped reveals, page transitions, and morph transitions. Consult this whenever you are about to write or modify any file under `slides\u002F\u003Cid>\u002F`, including from inside the `create-slide` or `apply-comments` workflows, or for any ad-hoc slide edit. Triggers on phrases like \"edit slide\", \"tweak this page\", \"fix the layout\", \"change the palette\", \"reveal one by one\", \"add a transition\", \"morph transition\", \"write the speaker notes\", \"generate the script \u002F talk track\", \"investigate the slide framework\", \"how do slides work here\".","https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot\u002Fblob\u002Fmain\u002Fapps\u002Fpresentations\u002F.agents\u002Fskills\u002Fslide-authoring\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M7CY5NMS099ZRH9ECYS47ZKG","current-slide","Resolve which slide, page, and (optionally) selected element the user is currently viewing in the open-slide dev server. Consult this whenever the user references \"this page\", \"this slide\", \"this element\", \"the slide I'm on\", \"the current page\", or any deictic reference to slide content without naming it. Re-read `node_modules\u002F.open-slide\u002Fcurrent.json` at the start of every such turn — the user navigates between turns, so a value you read earlier in the conversation is almost certainly stale.","https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot\u002Fblob\u002Fmain\u002Fapps\u002Fpresentations\u002F.agents\u002Fskills\u002Fcurrent-slide\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M7CY5G6XHNY7Y8KVGGKF654E","create-theme","Use this skill when the user wants to create, draft, author, or extract a slide theme in this open-slide repo. Triggers on phrases like \"create a theme\", \"make a theme called X\", \"extract a theme from \u003Cslide>\", \"build a theme from these images\". Produces two paired files under `themes\u002F` — `\u003Cid>.md` (palette, typography, layout, fixed Title\u002FFooter components, motion) and `\u003Cid>.demo.tsx` (a runnable demo slide that the dev-UI Themes panel previews). Do NOT use for editing real slides — only for authoring the theme bundle.","https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot\u002Fblob\u002Fmain\u002Fapps\u002Fpresentations\u002F.agents\u002Fskills\u002Fcreate-theme\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M7CY5B0DZNEVRY95X3QEKW3C","create-slide","Use this skill when the user wants to create, draft, author, or generate new slides \u002F a presentation in this open-slide repo. Triggers on phrases like \"make slides about X\", \"make a deck about X\", \"create a presentation\", \"draft slides for\", \"new slide\", \"a deck with speaker notes \u002F a script\", or when the user asks to add content under `slides\u002F`. Do NOT use for editing the framework itself — only for authoring content inside `slides\u002F\u003Cid>\u002F`.","https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot\u002Fblob\u002Fmain\u002Fapps\u002Fpresentations\u002F.agents\u002Fskills\u002Fcreate-slide\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7CY57ED279GA6QC3BFMPXG5","apply-comments","Apply pending @slide-comment markers written by the open-slide inspector tool. Use when the user asks to \"apply comments\", \"process slide comments\", \"apply the inspector comments\", or references markers left inside `slides\u002F\u003Cid>\u002Findex.tsx`.","https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot\u002Fblob\u002Fmain\u002Fapps\u002Fpresentations\u002F.agents\u002Fskills\u002Fapply-comments\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7CY53ZCYB0P3GYM2V3MEN1N","writing-shape","Writing, exploit: shape raw material into an article, paragraph by paragraph.","https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fwriting-shape\u002FSKILL.md",[],[]]