[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71JMP4SG49YZARGMDSSCP9J":3,"skill-same:01M71JMP4SG49YZARGMDSSCP9J":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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":44,"commitSha":45,"skillDirectory":5,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":65},"01M71JMP4SG49YZARGMDSSCP9J","playbook",null,"Pick the right ordered sequence of skills for the job at hand, announce it, and keep reminding the user which skill comes next after each stage completes — so they never have to remember the chain themselves. Only active when explicitly invoked.","caezium\u002Fskills","caezium","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113233555?v=4","01M71JB77ZPBAWEK009Y2W8BP7","Henry Zhang","01M71JB792NVXCWSYD27HQ0964",3,"MIT","https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fplaybook\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"stage","user","it","announce","sequence","at","active","next","hand","keep","when","only","true","pick","for","chain","never","which","remember","2026-11-10 10:12:30",false,"---\nname: playbook\ndescription: Pick the right ordered sequence of skills for the job at hand, announce it, and keep reminding the user which skill comes next after each stage completes — so they never have to remember the chain themselves. Only active when explicitly invoked.\ndisable-model-invocation: true\n---\n\n# Playbook\n\nThe user knows skills exist but shouldn't have to memorise which ones to run in which order. When this skill is invoked, you become the keeper of that sequence for the rest of the session.\n\nThis is **not** default behavior. Never volunteer skill-sequence guidance unless the user invoked `\u002Fplaybook` (or explicitly asks). Once invoked, the guidance persists for the whole session.\n\n## Process\n\n### 1. Pick the workflow\n\nRead the argument and conversation context, then match against the workflow table:\n\n| Workflow | When it fits |\n|---|---|\n| [feature](workflows\u002Ffeature.md) | Building a feature or making a nontrivial change: design → spec → tickets → implementation → review (Matt Pocock's spec-driven flow) |\n\n- If the user passed a workflow name as an argument (`\u002Fplaybook feature`), use that one.\n- If the context clearly matches one workflow, propose it and confirm in one line.\n- If ambiguous or nothing fits, list the workflows with one-line summaries and ask which one — or offer to run freeform without a playbook.\n\n### 2. Announce the sequence\n\nRead the chosen workflow file. Present the full sequence up front as a short numbered list: each step's skill, what it produces, and which step the user is currently at.\n\nDon't assume they're at step 1 — if the conversation already contains a sharpened design, they may be at the spec step; if a spec already exists on the tracker, they may be at tickets. Say where you think they are and why.\n\n### 3. Shepherd the sequence — this is the core job\n\nFor the rest of the session:\n\n- **When a step completes** (the skill finishes, its artifact exists), tell the user plainly: \"Step N done. Next: `\u002Fskill-name` — \u003Cwhat it does>.\" Put this at the END of your final message for the turn so it's the last thing they read.\n- **Never auto-run the next skill.** Each step is the user's call — they may want to pause, review, or leave the rest for a fresh session. Your job is only to make the next command copy-pasteable.\n- **If the user skips ahead or goes off-script**, don't fight it. Note where the sequence now stands and keep tracking from the new position.\n- **If the session ends mid-sequence**, when asked to summarise or hand off, include which step is next so a future session can resume.\n- **Respect each step's prerequisites** — the workflow file notes them (e.g. one-time repo setup). If a prerequisite is missing when the user reaches that step, surface it before they run the skill, not after it fails.\n\n## Adding workflows\n\nEach workflow is one file in [workflows\u002F](workflows\u002F): a name, when it fits, and an ordered list of steps (skill + what it produces + prerequisites). To add a new arrangement for a different context of work, add a file there and a row to the table above. Keep steps as existing skills — a playbook orders skills, it doesn't define new ones.\n","# Playbook\n\nThe user knows skills exist but shouldn't have to memorise which ones to run in which order. When this skill is invoked, you become the keeper of that sequence for the rest of the session.\n\nThis is **not** default behavior. Never volunteer skill-sequence guidance unless the user invoked `\u002Fplaybook` (or explicitly asks). Once invoked, the guidance persists for the whole session.\n\n## Process\n\n### 1. Pick the workflow\n\nRead the argument and conversation context, then match against the workflow table:\n\n| Workflow | When it fits |\n|---|---|\n| [feature](workflows\u002Ffeature.md) | Building a feature or making a nontrivial change: design → spec → tickets → implementation → review (Matt Pocock's spec-driven flow) |\n\n- If the user passed a workflow name as an argument (`\u002Fplaybook feature`), use that one.\n- If the context clearly matches one workflow, propose it and confirm in one line.\n- If ambiguous or nothing fits, list the workflows with one-line summaries and ask which one — or offer to run freeform without a playbook.\n\n### 2. Announce the sequence\n\nRead the chosen workflow file. Present the full sequence up front as a short numbered list: each step's skill, what it produces, and which step the user is currently at.\n\nDon't assume they're at step 1 — if the conversation already contains a sharpened design, they may be at the spec step; if a spec already exists on the tracker, they may be at tickets. Say where you think they are and why.\n\n### 3. Shepherd the sequence — this is the core job\n\nFor the rest of the session:\n\n- **When a step completes** (the skill finishes, its artifact exists), tell the user plainly: \"Step N done. Next: `\u002Fskill-name` — \u003Cwhat it does>.\" Put this at the END of your final message for the turn so it's the last thing they read.\n- **Never auto-run the next skill.** Each step is the user's call — they may want to pause, review, or leave the rest for a fresh session. Your job is only to make the next command copy-pasteable.\n- **If the user skips ahead or goes off-script**, don't fight it. Note where the sequence now stands and keep tracking from the new position.\n- **If the session ends mid-sequence**, when asked to summarise or hand off, include which step is next so a future session can resume.\n- **Respect each step's prerequisites** — the workflow file notes them (e.g. one-time repo setup). If a prerequisite is missing when the user reaches that step, surface it before they run the skill, not after it fails.\n\n## Adding workflows\n\nEach workflow is one file in [workflows\u002F](workflows\u002F): a name, when it fits, and an ordered list of steps (skill + what it produces + prerequisites). To add a new arrangement for a different context of work, add a file there and a row to the table above. Keep steps as existing skills — a playbook orders skills, it doesn't define new ones.\n",{"name":5,"description":7,"disable-model-invocation":43},true,"main","6ef866230c1ba3459fd08fc65141dfd37fffd41a",0,"https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills","https:\u002F\u002Fskills.henryzh.dev","https:\u002F\u002Fgithub.com\u002Fcaezium","henryzh.dev","quant, data science, full-stack, robotics.\r\nbuilding cool stuff","2026-08-24 19:21:44",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":43},[55,58,61],{"tool":56,"command":57},"npx","npx skills add caezium\u002Fskills --skill playbook",{"tool":59,"command":60},"bunx","bunx skills add caezium\u002Fskills --skill playbook",{"tool":62,"command":63},"pnpm","pnpm dlx skills add caezium\u002Fskills --skill playbook","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fplaybook\u002FSKILL.md",[66],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"workflows\u002Ffeature.md","REFERENCE","参考文档",2302,"https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fplaybook\u002Fworkflows\u002Ffeature.md",[73,95,123,141,161,183],{"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":89,"publishedAt":38},"01M71JT4RYCAS18RF6003YYR1D","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fwriting-for-agents\u002FSKILL.md",[79,84],{"categoryNo":80,"categoryName":81,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":85,"categoryName":86,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[90,33,91,92,93,94,29],"writing for agents","writing","editing","use","documents",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":104,"publishedAt":38},"01M71JT0GES4AZ5ADH8EADNN1Z","wrangler","Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fwrangler\u002FSKILL.md",[101],{"categoryNo":102,"categoryName":103,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000010","后端与接口",[97,105,106,107,108,109,110,111,112,113,114,115,116,33,117,118,119,120,121,122],"cloudflare","d1","knowledge","workflows","cli","secrets","commands","syntax","cloudflare workers","r2","queues","running","containers","correct","load","workers","best practices","store",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":38},"01M71JSWX4R203M32K9A18AAW8","workers-best-practices","Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from Cloudflare docs over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fworkers-best-practices\u002FSKILL.md",[],[130,120,121,131,132,133,33,105,134,107,135,97,91,119,29,136,137,138,139,140],"workers best practices","observability","reviews","promises","worker","new","code","common","streaming","state","anti-patterns",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":38},"01M71JST6P88MXGT2MWDTPJGEG","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fwizard\u002FSKILL.md",[],[143,116,148,33,149,150,151,30,93,152,29,153,154,155,156,157,158,159,160,110],"setting","up","ci","provisioning infrastructure","invoke","Bash","one","interactive","can","credentials","dashboard","generate","human",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":165,"sourceHtmlUrl":166,"categories":167,"keywords":168,"publishedAt":38},"01M71JSQ95S7BQ61DAPN95X2W4","why","Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available evidence sources, searches each relevant category, and returns a cited read on decisions and tradeoffs. Use how for runtime behavior.","https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fwhy\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fwhy\u002FSKILL.md",[],[163,169,170,171,172,33,173,174,93,175,176,177,178,179,180,181,182],"sources","thresholds","evidence","relevant","runtime","design","decisions","work","how","behavior","read","data","rationale","returns",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":192,"publishedAt":38},"01M71JSMHFVSH8HK8GXN6YAX6J","week-prep","Generate a briefing with calendar, tasks, and attention flags. Use for \"week prep\", \"briefing\", or \"what's on this week\".","https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fweek-prep\u002FSKILL.md",[189],{"categoryNo":190,"categoryName":191,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000023","Skill与智能体开发",[193,194,195,196,197,33,198,199,200,201,93,153,202,203,204,159,205,179,206,207],"week prep","prep","deep","attention","get","search","messages","briefing","MCP","tasks","with","slack","calendar","flags","grep"]