[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75CR8VNEBA09T2R3V1C047N":3,"skill-same:01M75CR8VNEBA09T2R3V1C047N":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"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":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M75CR8VNEBA09T2R3V1C047N","cto-review",null,"\u002Fcs:cto-review \u003Cplan> — Architecture and scaling interrogation. Tech debt, scaling cliffs, team scaling, build-vs-buy.","agisota\u002Fold-one","agisota","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121413592?v=4","01M75B4BRNT67EC1NDRT8QZEP2","01M75B4BS7QR9VP580MSCPTS3X",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fcto-review\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: \"cto-review\"\ndescription: \"\u002Fcs:cto-review \u003Cplan> — Architecture and scaling interrogation. Tech debt, scaling cliffs, team scaling, build-vs-buy.\"\n---\n\n# \u002Fcs:cto-review — CTO Forcing Questions\n\n**Command:** `\u002Fcs:cto-review \u003Cplan>`\n\nPressure-tests architecture and engineering scaling decisions. Six questions to surface the next scaling cliff before you hit it.\n\n## When to Run\n\n- Before approving a major architecture change\n- Before doubling the engineering team\n- Before a build-vs-buy decision > $100K\u002Fyear\n- When a system is showing reliability stress (SLOs missed)\n- Before committing to a new platform \u002F language \u002F DB\n\n## The Six CTO Questions\n\n### 1. Scaling Cliff\n**Where does the current architecture break, in terms of users \u002F requests \u002F data volume?**\n- Be specific. \"It breaks at 10× current load because the primary DB writes saturate.\"\n- If you don't know, run a load test before deciding.\n\n### 2. Tech Debt Inventory\n**What's the top tech debt item, what's it costing per week, and when does it become blocking?**\n```bash\npython ..\u002F..\u002F..\u002Fskills\u002Fcto-advisor\u002Fscripts\u002Ftech_debt_analyzer.py\n```\n\n### 3. Team Scaling\n**For each open req, what's the ramp time and contribution model?**\n```bash\npython ..\u002F..\u002F..\u002Fskills\u002Fcto-advisor\u002Fscripts\u002Fteam_scaling_calculator.py\n```\n\n### 4. Build vs Buy\n**Why are we building this instead of buying it — and what's the 3-year TCO of each?**\n- If \"we want control\" or \"it's not that hard\" — push back.\n- If the answer is \"this is our core moat,\" build.\n\n### 5. SLO \u002F Reliability\n**What are the SLOs for this system and what's the current error budget burn?**\n- Without an SLO, you can't reason about reliability tradeoffs.\n- See `engineering\u002Fslo-architect` for SLO design.\n\n### 6. Security & Compliance Surface\n**What does this expose, and has cs-ciso-advisor signed off?**\n- Architecture decisions are compliance decisions.\n- Loop in cs-ciso-advisor before commit.\n\n## Workflow\n\n1. Run the tech debt analyzer + team scaling calculator\n2. Define the scaling-cliff hypothesis explicitly\n3. Cross-check with cs-ciso-advisor for security implications\n4. Apply the verdict\n\n## Output Format\n\n```markdown\n# CTO Review: \u003Cplan>\n**Date:** YYYY-MM-DD\n\n## Scaling Cliff\n- Current capacity: \u003Cmetric>\n- Break point: \u003Cmetric>\n- Headroom: X months at current growth\n\n## Tech Debt\n- Top item: \u003Cdescription>\n- Cost per week: $X or N eng-hours\n- Blocking date estimate: \u003Cdate>\n\n## Team\n- Open reqs: N\n- Median ramp: X months\n- Contribution model: \u003Cpairing \u002F squad \u002F area>\n\n## Build vs Buy\n- 3-year build TCO: $X\n- 3-year buy TCO: $X\n- Strategic fit: \u003Ccore \u002F context>\n- Decision: BUILD | BUY\n\n## Reliability\n- SLO defined: yes \u002F no\n- Error budget burn: X% (target \u003C Y%)\n\n## Security\n- cs-ciso sign-off: ✅ \u002F ❌\n\n## Verdict\n🟢 SHIP | 🟡 SHARPEN | 🔴 BLOCK\n\n## Next Steps\n[3 concrete actions]\n```\n\n## Routing\n\n- `\u002Fcs:ciso-review` — mandatory if data surface changes\n- `\u002Fcs:cfo-review` — for build-vs-buy > $100K\n- `\u002Fcs:execute` — quarterly plan\n- `\u002Fcs:boardroom` — for architecture pivots\n\n## Related\n\n- Agent: [`cs-cto-advisor`](..\u002F..\u002F..\u002F..\u002Fagents\u002Fc-level\u002Fcs-cto-advisor.md)\n- Skill: [`cto-advisor`](..\u002F..\u002F..\u002Fskills\u002Fcto-advisor\u002FSKILL.md)\n- SLO: `..\u002F..\u002F..\u002F..\u002Fengineering\u002Fslo-architect\u002F`\n\n---\n\n**Version:** 1.0.0\n","# \u002Fcs:cto-review — CTO Forcing Questions\n\n**Command:** `\u002Fcs:cto-review \u003Cplan>`\n\nPressure-tests architecture and engineering scaling decisions. Six questions to surface the next scaling cliff before you hit it.\n\n## When to Run\n\n- Before approving a major architecture change\n- Before doubling the engineering team\n- Before a build-vs-buy decision > $100K\u002Fyear\n- When a system is showing reliability stress (SLOs missed)\n- Before committing to a new platform \u002F language \u002F DB\n\n## The Six CTO Questions\n\n### 1. Scaling Cliff\n**Where does the current architecture break, in terms of users \u002F requests \u002F data volume?**\n- Be specific. \"It breaks at 10× current load because the primary DB writes saturate.\"\n- If you don't know, run a load test before deciding.\n\n### 2. Tech Debt Inventory\n**What's the top tech debt item, what's it costing per week, and when does it become blocking?**\n```bash\npython ..\u002F..\u002F..\u002Fskills\u002Fcto-advisor\u002Fscripts\u002Ftech_debt_analyzer.py\n```\n\n### 3. Team Scaling\n**For each open req, what's the ramp time and contribution model?**\n```bash\npython ..\u002F..\u002F..\u002Fskills\u002Fcto-advisor\u002Fscripts\u002Fteam_scaling_calculator.py\n```\n\n### 4. Build vs Buy\n**Why are we building this instead of buying it — and what's the 3-year TCO of each?**\n- If \"we want control\" or \"it's not that hard\" — push back.\n- If the answer is \"this is our core moat,\" build.\n\n### 5. SLO \u002F Reliability\n**What are the SLOs for this system and what's the current error budget burn?**\n- Without an SLO, you can't reason about reliability tradeoffs.\n- See `engineering\u002Fslo-architect` for SLO design.\n\n### 6. Security & Compliance Surface\n**What does this expose, and has cs-ciso-advisor signed off?**\n- Architecture decisions are compliance decisions.\n- Loop in cs-ciso-advisor before commit.\n\n## Workflow\n\n1. Run the tech debt analyzer + team scaling calculator\n2. Define the scaling-cliff hypothesis explicitly\n3. Cross-check with cs-ciso-advisor for security implications\n4. Apply the verdict\n\n## Output Format\n\n```markdown\n# CTO Review: \u003Cplan>\n**Date:** YYYY-MM-DD\n\n## Scaling Cliff\n- Current capacity: \u003Cmetric>\n- Break point: \u003Cmetric>\n- Headroom: X months at current growth\n\n## Tech Debt\n- Top item: \u003Cdescription>\n- Cost per week: $X or N eng-hours\n- Blocking date estimate: \u003Cdate>\n\n## Team\n- Open reqs: N\n- Median ramp: X months\n- Contribution model: \u003Cpairing \u002F squad \u002F area>\n\n## Build vs Buy\n- 3-year build TCO: $X\n- 3-year buy TCO: $X\n- Strategic fit: \u003Ccore \u002F context>\n- Decision: BUILD | BUY\n\n## Reliability\n- SLO defined: yes \u002F no\n- Error budget burn: X% (target \u003C Y%)\n\n## Security\n- cs-ciso sign-off: ✅ \u002F ❌\n\n## Verdict\n🟢 SHIP | 🟡 SHARPEN | 🔴 BLOCK\n\n## Next Steps\n[3 concrete actions]\n```\n\n## Routing\n\n- `\u002Fcs:ciso-review` — mandatory if data surface changes\n- `\u002Fcs:cfo-review` — for build-vs-buy > $100K\n- `\u002Fcs:execute` — quarterly plan\n- `\u002Fcs:boardroom` — for architecture pivots\n\n## Related\n\n- Agent: [`cs-cto-advisor`](..\u002F..\u002F..\u002F..\u002Fagents\u002Fc-level\u002Fcs-cto-advisor.md)\n- Skill: [`cto-advisor`](..\u002F..\u002F..\u002Fskills\u002Fcto-advisor\u002FSKILL.md)\n- SLO: `..\u002F..\u002F..\u002F..\u002Fengineering\u002Fslo-architect\u002F`\n\n---\n\n**Version:** 1.0.0\n",{"name":5,"description":7},"main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fcto-review",1,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one","https:\u002F\u002Fagisota.github.io\u002Fold-one\u002F","https:\u002F\u002Fgithub.com\u002Fagisota","pzd.world","2026-07-04 22:32:06",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add agisota\u002Fold-one --skill cto-review",{"tool":38,"command":39},"bunx","bunx skills add agisota\u002Fold-one --skill cto-review",{"tool":41,"command":42},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill cto-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fcto-review\u002FSKILL.md",true,[],[47,54,61,70,77,84],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M75KRGZWQWE9JDBS6RX42NWV","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M75KRCZHKE0ZYAQFFYHS0YNP","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":65,"licenseFileUrl":66,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M75KR94KYQ30DTE1P9WNDAE0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M75KR3H13YJ9QHMD49818FA1","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M75KQMPY8A4Y8XTDD2DT0M9T","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M75KQHNZ0ANZNJGZY6M8MDAK","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]