[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75PCDGGHSCD7QRD3WFY72GY":3,"skill-same:01M75PCDGGHSCD7QRD3WFY72GY":43},{"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":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M75PCDGGHSCD7QRD3WFY72GY","cto-review",null,"\u002Fcs:cto-review \u003Cplan> — Architecture and scaling interrogation. Tech debt, scaling cliffs, team scaling, build-vs-buy. Use when committing to an architecture, planning for 10x load, or weighing a rebuild against a vendor.","TehutiRaEl\u002FTHEHIVE","TehutiRaEl","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F267495122?v=4","01M75N1QQQHT359S3XMYK7NPCB","01M75N1QRAW5P8P43HEHWMXCTE",0,"MIT","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fc-level-advisor\u002Fc-level-agents\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. Use when committing to an architecture, planning for 10x load, or weighing a rebuild against a vendor.\"\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","b4ebd6d8c3b36347a5d435bcb343a5fc1c6f08d1","skills-library\u002Fc-level-advisor\u002Fc-level-agents\u002Fskills\u002Fcto-review","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE","https:\u002F\u002Fgithub.com\u002FTehutiRaEl","2026-11-15 04:00:21",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add TehutiRaEl\u002FTHEHIVE --skill cto-review",{"tool":35,"command":36},"bunx","bunx skills add TehutiRaEl\u002FTHEHIVE --skill cto-review",{"tool":38,"command":39},"pnpm","pnpm dlx skills add TehutiRaEl\u002FTHEHIVE --skill cto-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fc-level-advisor\u002Fc-level-agents\u002Fskills\u002Fcto-review\u002FSKILL.md",true,[],[44,51,57,64,71,78],{"skillNo":45,"name":46,"nameZh":6,"description":47,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":48,"categories":49,"keywords":50,"publishedAt":18},"01M76XP63XDM4PFPX8MMVYN9JX","preamble-gate","Use BEFORE doing any work in this repo — before the first file edit, commit, push, PR, branch operation, workflow dispatch, scheduled trigger or timer, agent\u002Fsubagent spawn, dependency install, or message sent to an outside service. Forces a plain-language preamble to the founder first: WHAT you are about to do, WHY, HOW, why it is NECESSARY, the PROJECTED IMPROVEMENT, and the COST and RISK — then, for consequential work (governance, security, money, CI\u002Ftriggers, rewriting history, multi-agent fan-out), waits for an explicit go-ahead. Read-only investigation (reading files, grep, git log\u002Fdiff, answering questions) is exempt. Applies to every AI that works in this repo, not just Claude. Founder rule, 2026-11-10, written after an unattended automation ran up cost and froze the hive. Not a substitute for wired-or-not (which governs how completion is CLAIMED); this governs what happens BEFORE work starts.","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpreamble-gate\u002FSKILL.md",[],[],{"skillNo":52,"name":53,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":18},"01M75RAYXC1W361YR9NBXD59AM","visionary-recommender","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills\u002Fvisionary-recommender\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":18},"01M75RAQN9Q450RD57J2S6FSR4","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M75RAG1XMCJMF30HFV5S79AK","research","Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends\u002Fsentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Use when the user makes any research request that doesn't obviously match a more-specific specialist skill (e.g., \"research [topic]\", \"look into [topic]\", \"what do we know about [topic]\", \"investigate [topic]\", \"find me information on [topic]\", \"do some research on [topic]\", \"I need to understand [topic]\"). Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M75RA8RK2JVWB8MYGRB65V75","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M75RA08RXYRFSTNC6EEEX4ZD","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[]]