[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71JC7D95QFVP45NG03HRRTM":3,"skill-same:01M71JC7D95QFVP45NG03HRRTM":71},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":5,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M71JC7D95QFVP45NG03HRRTM","blast-radius",null,"Find what a code, schema, API, config, or behavior change could break beyond its visible diff, then prove the safety-critical assumption with real code. Use whenever the user asks what could break, requests a blast-radius review, or distrusts a deceptively small change.","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\u002Fblast-radius\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fblast-radius\u002FSKILL.md",[],[20,21,22,23,24,25,26,5,27,28,29,30,31,32,33,34,35,36,37,38],"blast radius","radius","use","prove","break","requests","what could break","with","critical","schema","diff","review","behavior","find","api","Safety","code","config","change","2026-11-10 10:12:30",false,"---\nname: blast-radius\ndescription: Find what a code, schema, API, config, or behavior change could break beyond its visible diff, then prove the safety-critical assumption with real code. Use whenever the user asks what could break, requests a blast-radius review, or distrusts a deceptively small change.\n---\n\n# Blast radius\n\nFind breakage a caller list will miss. The deliverable is not a convincing risk essay; it is the one safety-critical fact either proved against real behavior or marked unproven.\n\n## Evidence ladder\n\nFor every fact the change's safety depends on, climb as far as practical and report where you stopped:\n\n1. An unsupported assertion—never sufficient.\n2. A concrete `file:line`, pinned dependency source, schema, or contract.\n3. A traced bad case showing whether it can reach the changed behavior.\n4. A script or test that calls the real code and fails loudly if the fact is false.\n5. A reproduction through the running product.\n\nAny safety fact below level 4 stays explicitly unproven.\n\n## Tool availability\n\n| Need | Preferred route | Fallback |\n|---|---|---|\n| Change and history | Local git diff\u002Flog plus an available source-control connector | Local repository only; name missing PR context |\n| Downstream consumers | Code search, schemas, generated clients, migrations, pinned dependency source | Trace the reachable local chain and mark external consumers unknown |\n| Runtime proof | Existing tests, verification harness, or a small deterministic script | Minimal isolated repro; if execution is impossible, stop at the evidence level reached |\n| Independent review | Invoke `interrogate` when the user authorizes a multi-agent review | One lead-review pass; disclose the missing independent signal |\n\n## Process\n\n1. **Read the change.** Inspect the diff, changed symbols, deleted behavior, commits, and surrounding contracts. State what now behaves differently, including effects the diff does not spell out.\n2. **Name the safety fact.** Find the one or two assumptions that collapse most scary cases if true. Spend effort here instead of producing a long speculative list.\n3. **Look past symbol search.** Check pinned library behavior and local patches; event timing and teardown; serialized data, database columns, wire formats, other-language consumers, feature flags, jobs, caches, and code several hops downstream.\n4. **Trace real risks.** For each candidate, show a reachable failure path, likelihood, cost, and a concrete check. A search that finds nothing is evidence when the search scope is stated.\n5. **Prove the safety fact.** Prefer the smallest script or test importing the same code the product ships. Run it and retain output. Reproduce through the product when proportionate.\n6. **Widen only when useful.** For a broad or high-risk change, suggest `interrogate`; do not launch agents unless current policy and user intent allow it.\n\n## Output contract\n\n- **What changed:** the visible and implicit behavior change.\n- **Safety fact:** the assumption, evidence level reached, and proof output; otherwise `UNPROVEN`.\n- **Risks:** only reachable risks, each with location, likelihood, impact, and check.\n- **Cleared:** candidates investigated and why they do not reach.\n- **Before merge:** the cheapest test or repro that catches the real failure.\n- **Coverage gaps:** unavailable repositories, services, connectors, or runtime paths.\n\nUse plain language, cite real code, and remove private material before public sharing.\n\n\u003C!-- Adapted from poteto\u002Fpstack blast-radius, MIT License, Lauren Tan, cursor\u002Fplugins@51a96e0. -->\n","# Blast radius\n\nFind breakage a caller list will miss. The deliverable is not a convincing risk essay; it is the one safety-critical fact either proved against real behavior or marked unproven.\n\n## Evidence ladder\n\nFor every fact the change's safety depends on, climb as far as practical and report where you stopped:\n\n1. An unsupported assertion—never sufficient.\n2. A concrete `file:line`, pinned dependency source, schema, or contract.\n3. A traced bad case showing whether it can reach the changed behavior.\n4. A script or test that calls the real code and fails loudly if the fact is false.\n5. A reproduction through the running product.\n\nAny safety fact below level 4 stays explicitly unproven.\n\n## Tool availability\n\n| Need | Preferred route | Fallback |\n|---|---|---|\n| Change and history | Local git diff\u002Flog plus an available source-control connector | Local repository only; name missing PR context |\n| Downstream consumers | Code search, schemas, generated clients, migrations, pinned dependency source | Trace the reachable local chain and mark external consumers unknown |\n| Runtime proof | Existing tests, verification harness, or a small deterministic script | Minimal isolated repro; if execution is impossible, stop at the evidence level reached |\n| Independent review | Invoke `interrogate` when the user authorizes a multi-agent review | One lead-review pass; disclose the missing independent signal |\n\n## Process\n\n1. **Read the change.** Inspect the diff, changed symbols, deleted behavior, commits, and surrounding contracts. State what now behaves differently, including effects the diff does not spell out.\n2. **Name the safety fact.** Find the one or two assumptions that collapse most scary cases if true. Spend effort here instead of producing a long speculative list.\n3. **Look past symbol search.** Check pinned library behavior and local patches; event timing and teardown; serialized data, database columns, wire formats, other-language consumers, feature flags, jobs, caches, and code several hops downstream.\n4. **Trace real risks.** For each candidate, show a reachable failure path, likelihood, cost, and a concrete check. A search that finds nothing is evidence when the search scope is stated.\n5. **Prove the safety fact.** Prefer the smallest script or test importing the same code the product ships. Run it and retain output. Reproduce through the product when proportionate.\n6. **Widen only when useful.** For a broad or high-risk change, suggest `interrogate`; do not launch agents unless current policy and user intent allow it.\n\n## Output contract\n\n- **What changed:** the visible and implicit behavior change.\n- **Safety fact:** the assumption, evidence level reached, and proof output; otherwise `UNPROVEN`.\n- **Risks:** only reachable risks, each with location, likelihood, impact, and check.\n- **Cleared:** candidates investigated and why they do not reach.\n- **Before merge:** the cheapest test or repro that catches the real failure.\n- **Coverage gaps:** unavailable repositories, services, connectors, or runtime paths.\n\nUse plain language, cite real code, and remove private material before public sharing.\n\n\u003C!-- Adapted from poteto\u002Fpstack blast-radius, MIT License, Lauren Tan, cursor\u002Fplugins@51a96e0. -->\n",{"name":5,"description":7},"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":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add caezium\u002Fskills --skill blast-radius",{"tool":59,"command":60},"bunx","bunx skills add caezium\u002Fskills --skill blast-radius",{"tool":62,"command":63},"pnpm","pnpm dlx skills add caezium\u002Fskills --skill blast-radius","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fblast-radius\u002FSKILL.md",true,[67],{"path":68,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":16},"LICENSE","许可证",1067,[72,95,123,140,161,182],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":88,"publishedAt":39},"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",[78,83],{"categoryNo":79,"categoryName":80,"taxonomyType":81,"taxonomyTypeDesc":82},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":84,"categoryName":85,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[89,90,91,92,22,93,94],"writing for agents","for","writing","editing","documents","when",{"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":39},"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":81,"taxonomyTypeDesc":82},"01JBSEEDCAT000000000000010","后端与接口",[97,105,106,107,108,109,110,111,112,113,114,115,116,90,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":39},"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,90,105,134,107,135,97,91,119,94,36,136,137,138,139],"workers best practices","observability","reviews","promises","worker","new","common","streaming","state","anti-patterns",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":39},"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",[],[142,116,147,90,148,149,150,151,22,152,94,153,154,155,156,157,158,159,160,110],"setting","up","ci","provisioning infrastructure","only","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":39},"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,90,173,174,22,175,176,177,32,178,179,180,181],"sources","thresholds","evidence","relevant","runtime","design","decisions","work","how","read","data","rationale","returns",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":191,"publishedAt":39},"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",[188],{"categoryNo":189,"categoryName":190,"taxonomyType":81,"taxonomyTypeDesc":82},"01JBSEEDCAT000000000000023","Skill与智能体开发",[192,193,194,195,196,90,197,198,199,200,22,153,201,27,202,159,203,178,204,205],"week prep","prep","deep","attention","get","search","messages","briefing","MCP","tasks","slack","calendar","flags","grep"]