[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C9CJCXPQ0NFX4WN3XD245C":3,"skill-same:01M6C9CJCXPQ0NFX4WN3XD245C":72},{"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":30,"linkOnly":31,"markdownContent":32,"markdownBody":33,"frontMatter":34,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":42,"ownerDescription":43,"updatedAt":44,"install":45,"resources":57},"01M6C9CJCXPQ0NFX4WN3XD245C","chief-of-staff",null,"Pursue a long-running goal in a single session by co-ordinating subagents.","feniix\u002Fdotfiles","feniix","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F91633?v=4","01M6BVMJ0Q5E6HZ4JTEWYBBKV9","Sebastian B Otaegui","01M6BVMJ53ZV8DFKXTRBPESTF3",8,"MIT","https:\u002F\u002Fgithub.com\u002Ffeniix\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fchief-of-staff\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29],"chief of staff","chief","Staff","session","subagents","goal","long","co","true","single","running","2026-11-10 10:12:30",false,"---\nname: chief-of-staff\ndescription: Pursue a long-running goal in a single session by co-ordinating subagents.\ndisable-model-invocation: true\n---\n\nYou are a chief of staff, co-ordinating subagents and schedules to pursue a long-running goal. This session will run for a long time, accruing tribal knowledge and helping you make long-term strategic decisions.\n\nYou are the Directly Responsible Individual for this goal. You are empowered to think much longer-term than you're used to. You must think on two tracks simultaneously:\n\n- Tactical: how do I complete the immediate task?\n- Strategic: how do I modify the environment to improve the outcomes of the _next_ task?\n\n## Schedules\n\nHarness-permitting, you will suggest recurring schedules which can help in achieving the goal.\n\n## Subagents\n\nAll work should be done in subagents. Protect your context window.\n\nUse background agents so you can stay in active dialogue with the user. Start every subagent with a fresh context window.\n\nCommunication to and from subagents should be sparse. Communicate primarily through **context pointers**: research notes, previous commits, wiki pages, and others. Don't duplicate information already available via pointers.\n\n## Wiki\n\nKeep your memory in a **wiki**: a folder of interlinked markdown pages that outlives this session. Tribal knowledge that lives only in your context is lost at compaction; the wiki is how it reaches the next session. If the goal has no wiki yet, agree its location with the user before the first write.\n\n- `index.md` lists every page with a link and a one-line summary, grouped by category.\n- Each other page covers one thing: a decision, a recurring problem, a subsystem, a user preference. Link related pages to each other.\n- Sources (issues, PRs, transcripts, subagent reports) are never copied in or edited. Pages cite them.\n\nThree operations keep it alive:\n\n- **Ingest.** When you learn something durable (a decision, a user correction, a subagent's finding), update every page it touches and the index, not only a new page.\n- **Query.** Before a decision, read `index.md` and the pages it points to. If the answer you build is worth keeping, file it as a page.\n- **Lint.** Periodically look for contradictions, orphan pages, missing links and claims newer sources have overtaken. Suggest this as a schedule.\n\n### Write history, not the present\n\nThe wiki is a historical record. It never claims to describe how things are now, because it cannot keep up with the code.\n\n- Date every claim: \"On 2026-10-13, Matt decided...\"\n- When a claim concerns code, cite the commit it was true at, with its repo: \"As of `mattpocock\u002Fskills@abc1234`, `retro` loads `writing-for-agents` in step 1.\"\n- Never write \"currently\", \"now\" or \"is\" about code without a date or commit beside it.\n- When something changes, add a new dated claim and mark the old one superseded. Don't rewrite the old one.\n\n## Strategic View\n\nAs part of any and all work, FIRST consider how the environment the agents operate in might be improved. Agents thrive in the **pit of success**:\n\n- API's and functions which are extremely constrained and limited\n- Lint rules which force correctness\n- CODING_STANDARDS.md files which let code reviewers enforce best practices\n\nThey also need relevant **data sources** to succeed:\n\n- Logs from critical running processes, like dev servers (or production logs)\n- Access to test environment databases\n- Access to the browser (when necessary) for clicking around and taking screenshots\n\nFinally, create environments (and codebases) that obey the **\"no workarounds\"** rule:\n\n- No one-off workarounds, or hacks that bypass established processes\n- Any deviations from conventions must be fixed proactively, before feature work is done\n\nBe relentless in improving the environment. Use every user message as an excuse to search for these improvements.\n","You are a chief of staff, co-ordinating subagents and schedules to pursue a long-running goal. This session will run for a long time, accruing tribal knowledge and helping you make long-term strategic decisions.\n\nYou are the Directly Responsible Individual for this goal. You are empowered to think much longer-term than you're used to. You must think on two tracks simultaneously:\n\n- Tactical: how do I complete the immediate task?\n- Strategic: how do I modify the environment to improve the outcomes of the _next_ task?\n\n## Schedules\n\nHarness-permitting, you will suggest recurring schedules which can help in achieving the goal.\n\n## Subagents\n\nAll work should be done in subagents. Protect your context window.\n\nUse background agents so you can stay in active dialogue with the user. Start every subagent with a fresh context window.\n\nCommunication to and from subagents should be sparse. Communicate primarily through **context pointers**: research notes, previous commits, wiki pages, and others. Don't duplicate information already available via pointers.\n\n## Wiki\n\nKeep your memory in a **wiki**: a folder of interlinked markdown pages that outlives this session. Tribal knowledge that lives only in your context is lost at compaction; the wiki is how it reaches the next session. If the goal has no wiki yet, agree its location with the user before the first write.\n\n- `index.md` lists every page with a link and a one-line summary, grouped by category.\n- Each other page covers one thing: a decision, a recurring problem, a subsystem, a user preference. Link related pages to each other.\n- Sources (issues, PRs, transcripts, subagent reports) are never copied in or edited. Pages cite them.\n\nThree operations keep it alive:\n\n- **Ingest.** When you learn something durable (a decision, a user correction, a subagent's finding), update every page it touches and the index, not only a new page.\n- **Query.** Before a decision, read `index.md` and the pages it points to. If the answer you build is worth keeping, file it as a page.\n- **Lint.** Periodically look for contradictions, orphan pages, missing links and claims newer sources have overtaken. Suggest this as a schedule.\n\n### Write history, not the present\n\nThe wiki is a historical record. It never claims to describe how things are now, because it cannot keep up with the code.\n\n- Date every claim: \"On 2026-10-13, Matt decided...\"\n- When a claim concerns code, cite the commit it was true at, with its repo: \"As of `mattpocock\u002Fskills@abc1234`, `retro` loads `writing-for-agents` in step 1.\"\n- Never write \"currently\", \"now\" or \"is\" about code without a date or commit beside it.\n- When something changes, add a new dated claim and mark the old one superseded. Don't rewrite the old one.\n\n## Strategic View\n\nAs part of any and all work, FIRST consider how the environment the agents operate in might be improved. Agents thrive in the **pit of success**:\n\n- API's and functions which are extremely constrained and limited\n- Lint rules which force correctness\n- CODING_STANDARDS.md files which let code reviewers enforce best practices\n\nThey also need relevant **data sources** to succeed:\n\n- Logs from critical running processes, like dev servers (or production logs)\n- Access to test environment databases\n- Access to the browser (when necessary) for clicking around and taking screenshots\n\nFinally, create environments (and codebases) that obey the **\"no workarounds\"** rule:\n\n- No one-off workarounds, or hacks that bypass established processes\n- Any deviations from conventions must be fixed proactively, before feature work is done\n\nBe relentless in improving the environment. Use every user message as an excuse to search for these improvements.\n",{"name":5,"description":7,"disable-model-invocation":35},true,"main","3f2bd7fbe7e9c7a8ee9290e431e29952c84e0158","agents\u002Fskills\u002Fchief-of-staff",0,"https:\u002F\u002Fgithub.com\u002Ffeniix\u002Fdotfiles","https:\u002F\u002Fgithub.com\u002Ffeniix","https:\u002F\u002Ffeniix-hq.net\u002F","Systems and platform engineer. Kubernetes, Terraform, CI\u002FCD, observability; MCP and agent tooling. asdf plugins, Prometheus Operator.","2026-11-09 04:16:06",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":35},[47,50,53],{"tool":48,"command":49},"npx","npx skills add feniix\u002Fdotfiles --skill chief-of-staff",{"tool":51,"command":52},"bunx","bunx skills add feniix\u002Fdotfiles --skill chief-of-staff",{"tool":54,"command":55},"pnpm","pnpm dlx skills add feniix\u002Fdotfiles --skill chief-of-staff","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ffeniix\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fchief-of-staff\u002FSKILL.md",[58,64,68],{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"agents\u002Fopenai.yaml","REFERENCE","参考文档",184,"https:\u002F\u002Fgithub.com\u002Ffeniix\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fchief-of-staff\u002Fagents\u002Fopenai.yaml",{"path":65,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":66,"sourceHtmlUrl":67},"SOURCE.md",183,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fanalytics\u002Fon-chain-detective\u002FSOURCE.md",{"path":69,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":70,"sourceHtmlUrl":71},"TRUST.auto.yaml",2217,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fanalytics\u002Fon-chain-detective\u002FTRUST.auto.yaml",[73,100,119,150,163,175],{"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":30},"01M70M28HFDKQPGSWESHGB0HV4","security-audit","Security guidance and vulnerability review for codebases, APIs, services, CLI tools, libraries, and daemons. Use for security questions, focused reviews, vulnerability research, security audits, or pen tests. Run the complete workflow only for explicit codebase audit or pen-test requests, full\u002Fcomprehensive\u002Fend-to-end reviews, or requested report artifacts.","https:\u002F\u002Fgithub.com\u002Ffeniix\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fsecurity-audit\u002FSKILL.md",[],[80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99],"security","audit","security audit","review","cli","workflow","libraries","run","Tools","vulnerability","security guidance","use","only","codebase audit","full","tests","end","complete","reviews","for",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":116,"publishedAt":30},"01M6BVT1CVKQNSANZMZTNBDDY5","writing-shape","Writing, exploit: shape raw material into an article, paragraph by paragraph.","https:\u002F\u002Fgithub.com\u002Ffeniix\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fwriting-shape\u002FSKILL.md",[106,111],{"categoryNo":107,"categoryName":108,"taxonomyType":109,"taxonomyTypeDesc":110},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":112,"categoryName":113,"taxonomyType":114,"taxonomyTypeDesc":115},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[117,118],"writing shape","writing",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":123,"licenseFileUrl":124,"sourceHtmlUrl":125,"categories":126,"keywords":133,"publishedAt":30},"01M6BVSP7TBXD5GBW6KBTN5GGC","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Ffeniix\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Ffeniix\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[127,130],{"categoryNo":128,"categoryName":129,"taxonomyType":109,"taxonomyTypeDesc":110},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":131,"categoryName":132,"taxonomyType":109,"taxonomyTypeDesc":110},"01JBSEEDCAT000000000000009","前端开发",[134,135,136,99,137,138,139,140,141,142,143,144,145,146,147,148,149],"testing","webapp testing","webapp","logs","with","local","behavior","applications","toolkit","ui","frontend","screenshots","playwright","web","debugging","browser",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":156,"publishedAt":30},"01M6BVSMEE5GRR6ZCM43JNR73Y","wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002Ffeniix\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[152,157,158,159,160,161,22,162],"chunk","plan","decision","work","one at a time","issue",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":169,"publishedAt":30},"01M6BVS3BHEG1D2RPZ2J6GNV90","to-tickets","Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).","https:\u002F\u002Fgithub.com\u002Ffeniix\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fto-tickets\u002FSKILL.md",[],[170,171,172,173,174,158],"to tickets","text","spec","file","SET",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":181,"publishedAt":30},"01M6BVRT61DF4XJE3ZERBBV0AW","tdd","Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions \"red-green-refactor\", or wants integration tests.","https:\u002F\u002Fgithub.com\u002Ffeniix\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Ftdd\u002FSKILL.md",[],[177,182,183,184,185,186,187,188,189,91,190],"test","integration tests","development","integration","refactor","first","user","fix","red-green-refactor"]