[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79BWMPXH9NWFTHAZNJ87CTV":3,"skill-same:01M79BWMPXH9NWFTHAZNJ87CTV":44},{"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":13,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":43},"01M79BWMPXH9NWFTHAZNJ87CTV","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.","jackwynne\u002Ffinance-tracking","jackwynne","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6869144?v=4","01M79BWEB0X3CFN7YRKDN5H4GR","01M79BWEBZKSJH7P1JW70H9MQS",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjackwynne\u002Ffinance-tracking\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\nResolve model choices and tool arguments through [the repository model policy](..\u002F..\u002Fpstack-models.md). Its availability and parent-inheritance rules override the inline defaults below.\n\nFan out N parallel attempts at the same task. Read every candidate end to end. Pick the strongest as the base. Graft the best ideas from the others into it. Verify the synthesized result.\n\n## Start\n\nOpen a todolist with one entry per phase before launching anything. The arena runs autonomously and the list keeps phases from silently disappearing.\n\n1. Frame\n2. Fan out\n3. Cross-judge\n4. Pick\n5. Graft\n6. Verify\n\n## Phase A: Frame\n\nThe N candidates will receive the same prompt, so the prompt is the contract. Get it right before spawning anything.\n\n1. State the artifact each candidate is producing.\n2. Derive the rubric. State what success looks like for *this* task, then turn it into 3-6 concrete gradeable criteria. Concrete: `Adds a --dry-run flag that skips writes`. Vague: `code is correct`. The rubric is the picker's tool in Phase D; candidates only see the task.\n3. Pick the runners. Use `arena runners` from `.agents\u002Fpstack-models.md` when present. Otherwise default to one each on `claude-fable-5-thinking-max`, `gpt-5.6-sol-max`, `grok-4.6-fast-xhigh`, `claude-opus-5-thinking-xhigh`. Spawn more when the arena covers multiple design directions. Same model N times when the work is generation-bound rather than judgment-sensitive.\n4. Assign output paths. Each candidate writes to its own location (a git worktree where possible, otherwise `\u002Ftmp\u002Farena-\u003Cslug>\u002Fcandidate-\u003Cn>\u002F`). N candidates writing to the same path is shared mutable state and fails the the **separate-before-serializing-shared-state** principle skill test.\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 both the artifact and a short rationale.\n\nThe rationale is mandatory. Without it, the parent cannot tell whether a candidate's structure is principled or accidental, which makes Phase E grafting unreliable. Each rationale names the alternatives the candidate considered and what it rejected.\n\nIf a candidate fails to produce output, proceed with N-1 and note the dropout in the synthesis record.\n\n## Phase C: Cross-judge\n\nAfter all Phase B candidates complete, choose one model from the `arena cross-judge pool` in `.agents\u002Fpstack-models.md` when present. Otherwise use `claude-fable-5-thinking-max`, `gpt-5.6-sol-max`, `grok-4.6-fast-xhigh`, `claude-opus-5-thinking-xhigh`. 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 the parent's reading in Phase D, not with the candidates themselves. Spawning while candidates are still writing means the judge sees partial or empty outputs and reports them as dropouts.\n\n## Phase D: Pick a base\n\nRead every candidate end to end before picking. Skimming N candidates surfaces only the candidate whose surface looks most familiar.\n\nScore each candidate against the rubric criterion by criterion, not on holistic feel. Compare against 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 on which candidate a future maintainer can extend most easily without breaking invariants. Prefer the cleaner boundary or smaller surface area when two feel tied, per the Laziness Protocol.\n\nRecord the pick and the reason in a short synthesis note alongside the base artifact, including the cross-judge's verdict.\n\n## Phase E: Graft\n\nWalk each losing candidate once more and identify what is worth porting into the base. The signal is usually one or two things per candidate, not most of it.\n\nFold each graft in by hand, per the **redesign-from-first-principles** principle skill. Don't paste mechanically. The result has to remain coherent under one mental model.\n\nRecord what was grafted, from which candidate, and what was rejected and why. The rejection notes are the highest-signal part of the record. Future readers learn from what you considered and dropped, not just what you kept.\n\nWhen N candidates converge on the same shape, that is a strong agreement signal. Note the convergence in the record and ship the consensus shape. No graft is needed. When N candidates wildly diverge, Phase A was under-specified. Reframe and re-run rather than averaging the divergence.\n\n## Phase F: Verify\n\nThe synthesized artifact has to hold up under the same scrutiny as any other output, per the **prove-it-works** principle skill. The arena does not earn you a pass.\n\nIf verification surfaces a problem the arena did not catch, either Phase A was wrong (re-frame and re-run) or one candidate caught it and you missed the graft (go back to Phase E). Don't paper over.\n\n## Outputs\n\nOne synthesized artifact. One short synthesis note alongside, naming the base, the grafts (with source candidate), the rejections, the dropouts if any, and the verification result.\n","# Arena\n\nResolve model choices and tool arguments through [the repository model policy](..\u002F..\u002Fpstack-models.md). Its availability and parent-inheritance rules override the inline defaults below.\n\nFan out N parallel attempts at the same task. Read every candidate end to end. Pick the strongest as the base. Graft the best ideas from the others into it. Verify the synthesized result.\n\n## Start\n\nOpen a todolist with one entry per phase before launching anything. The arena runs autonomously and the list keeps phases from silently disappearing.\n\n1. Frame\n2. Fan out\n3. Cross-judge\n4. Pick\n5. Graft\n6. Verify\n\n## Phase A: Frame\n\nThe N candidates will receive the same prompt, so the prompt is the contract. Get it right before spawning anything.\n\n1. State the artifact each candidate is producing.\n2. Derive the rubric. State what success looks like for *this* task, then turn it into 3-6 concrete gradeable criteria. Concrete: `Adds a --dry-run flag that skips writes`. Vague: `code is correct`. The rubric is the picker's tool in Phase D; candidates only see the task.\n3. Pick the runners. Use `arena runners` from `.agents\u002Fpstack-models.md` when present. Otherwise default to one each on `claude-fable-5-thinking-max`, `gpt-5.6-sol-max`, `grok-4.6-fast-xhigh`, `claude-opus-5-thinking-xhigh`. Spawn more when the arena covers multiple design directions. Same model N times when the work is generation-bound rather than judgment-sensitive.\n4. Assign output paths. Each candidate writes to its own location (a git worktree where possible, otherwise `\u002Ftmp\u002Farena-\u003Cslug>\u002Fcandidate-\u003Cn>\u002F`). N candidates writing to the same path is shared mutable state and fails the the **separate-before-serializing-shared-state** principle skill test.\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 both the artifact and a short rationale.\n\nThe rationale is mandatory. Without it, the parent cannot tell whether a candidate's structure is principled or accidental, which makes Phase E grafting unreliable. Each rationale names the alternatives the candidate considered and what it rejected.\n\nIf a candidate fails to produce output, proceed with N-1 and note the dropout in the synthesis record.\n\n## Phase C: Cross-judge\n\nAfter all Phase B candidates complete, choose one model from the `arena cross-judge pool` in `.agents\u002Fpstack-models.md` when present. Otherwise use `claude-fable-5-thinking-max`, `gpt-5.6-sol-max`, `grok-4.6-fast-xhigh`, `claude-opus-5-thinking-xhigh`. 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 the parent's reading in Phase D, not with the candidates themselves. Spawning while candidates are still writing means the judge sees partial or empty outputs and reports them as dropouts.\n\n## Phase D: Pick a base\n\nRead every candidate end to end before picking. Skimming N candidates surfaces only the candidate whose surface looks most familiar.\n\nScore each candidate against the rubric criterion by criterion, not on holistic feel. Compare against 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 on which candidate a future maintainer can extend most easily without breaking invariants. Prefer the cleaner boundary or smaller surface area when two feel tied, per the Laziness Protocol.\n\nRecord the pick and the reason in a short synthesis note alongside the base artifact, including the cross-judge's verdict.\n\n## Phase E: Graft\n\nWalk each losing candidate once more and identify what is worth porting into the base. The signal is usually one or two things per candidate, not most of it.\n\nFold each graft in by hand, per the **redesign-from-first-principles** principle skill. Don't paste mechanically. The result has to remain coherent under one mental model.\n\nRecord what was grafted, from which candidate, and what was rejected and why. The rejection notes are the highest-signal part of the record. Future readers learn from what you considered and dropped, not just what you kept.\n\nWhen N candidates converge on the same shape, that is a strong agreement signal. Note the convergence in the record and ship the consensus shape. No graft is needed. When N candidates wildly diverge, Phase A was under-specified. Reframe and re-run rather than averaging the divergence.\n\n## Phase F: Verify\n\nThe synthesized artifact has to hold up under the same scrutiny as any other output, per the **prove-it-works** principle skill. The arena does not earn you a pass.\n\nIf verification surfaces a problem the arena did not catch, either Phase A was wrong (re-frame and re-run) or one candidate caught it and you missed the graft (go back to Phase E). Don't paper over.\n\n## Outputs\n\nOne synthesized artifact. One short synthesis note alongside, naming the base, the grafts (with source candidate), the rejections, the dropouts if any, and the verification result.\n",{"name":5,"description":7,"disable-model-invocation":23},true,"main","e0702036cb52e7ea4069290826f12c74e8416c42",".agents\u002Fskills\u002Farena","https:\u002F\u002Fgithub.com\u002Fjackwynne\u002Ffinance-tracking","https:\u002F\u002Ffinance-tracking-wine.vercel.app","https:\u002F\u002Fgithub.com\u002Fjackwynne","2026-10-03 09:46:58",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":23},[33,36,39],{"tool":34,"command":35},"npx","npx skills add jackwynne\u002Ffinance-tracking --skill arena",{"tool":37,"command":38},"bunx","bunx skills add jackwynne\u002Ffinance-tracking --skill arena",{"tool":40,"command":41},"pnpm","pnpm dlx skills add jackwynne\u002Ffinance-tracking --skill arena","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjackwynne\u002Ffinance-tracking\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Farena\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":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":18},"01M79C2ZP0JW4JE4RJ2WPK3MWE","finance-updates","Review Koru spending, bank exports, dated holdings and monthly purchase emails, then prepare proposals for the user's review. Use with a Koru review bundle or connected Koru MCP tools.","https:\u002F\u002Fgithub.com\u002Fjackwynne\u002Ffinance-tracking\u002Fblob\u002Fmain\u002Fplugins\u002Fkoru\u002Fskills\u002Ffinance-updates\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M79C2XPQ5EASBQKAWTW8PCRD","convex","Routes general Convex requests to the right project skill. Use when the user asks which Convex skill to use or gives an underspecified Convex app task.","https:\u002F\u002Fgithub.com\u002Fjackwynne\u002Ffinance-tracking\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fconvex\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M79C2V0EVRQ82YA2GXGGJX4C","convex-setup-auth","Sets up Convex auth, identity mapping, and access control. Use for login, auth providers, users tables, protected functions, or roles in a Convex app.","https:\u002F\u002Fgithub.com\u002Fjackwynne\u002Ffinance-tracking\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fconvex-setup-auth\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M79C2QNEAVSB9Y02YT50M8GP","convex-quickstart","Creates or adds Convex to an app. Use for new Convex projects, npm create convex@latest, frontend setup, env vars, or the first npx convex dev run.","https:\u002F\u002Fgithub.com\u002Fjackwynne\u002Ffinance-tracking\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fconvex-quickstart\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M79C2KH6CEQ9CA2G8QA3PBST","convex-performance-audit","Audits Convex performance for reads, subscriptions, write contention, and function limits. Use for slow features, insights findings, OCC conflicts, or read amplification.","https:\u002F\u002Fgithub.com\u002Fjackwynne\u002Ffinance-tracking\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fconvex-performance-audit\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M79C2FDTVEFFDZM2W9FXPEAD","convex-migration-helper","Plans Convex schema and data migrations with widen-migrate-narrow and @convex-dev\u002Fmigrations. Use for breaking schema changes, backfills, table reshaping, or zero-downtime rollouts.","https:\u002F\u002Fgithub.com\u002Fjackwynne\u002Ffinance-tracking\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fconvex-migration-helper\u002FSKILL.md",[],[]]