[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75PDYP1BHDTK11Y2SWMPZZE":3,"skill-same:01M75PDYP1BHDTK11Y2SWMPZZE":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},"01M75PDYP1BHDTK11Y2SWMPZZE","founder-mode",null,"\u002Fcs:founder-mode \u003Cquestion> — Auto-routes any founder question to the right C-role advisor or to \u002Fcs:boardroom for multi-role topics. The single-command entry point. Use when a founder asks any strategic question without knowing which advisor or command fits — e.g. 'runway pressure' routes to the CFO, 'gross retention dropped' routes to the CCO.","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\u002Ffounder-mode\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: \"founder-mode\"\ndescription: \"\u002Fcs:founder-mode \u003Cquestion> — Auto-routes any founder question to the right C-role advisor or to \u002Fcs:boardroom for multi-role topics. The single-command entry point. Use when a founder asks any strategic question without knowing which advisor or command fits — e.g. 'runway pressure' routes to the CFO, 'gross retention dropped' routes to the CCO.\"\n---\n\n# \u002Fcs:founder-mode — The Auto-Router\n\n**Command:** `\u002Fcs:founder-mode \u003Cquestion>`\n\nThe single command a founder needs to remember. Routes the question to the right C-role automatically, or triggers `\u002Fcs:boardroom` if multi-role.\n\nThis is the **killer command** — the answer to \"I don't know which slash command to use.\" Type the question; the system figures out the room.\n\n## Routing Logic\n\nThe router (via `cs-chief-of-staff`) does keyword + intent matching:\n\n| Signal in question | Route |\n|---|---|\n| burn, runway, fundraise, dilution, model, LTV, CAC | `cs-cfo-advisor` |\n| pipeline, win rate, forecast, quota, ramp, sales motion | `cs-cro-advisor` |\n| positioning, ICP, message, brand, channel, campaign | `cs-cmo-advisor` |\n| roadmap, PMF, JTBD, North Star, RICE, kill | `cs-cpo-advisor` |\n| cadence, OKR, scorecard, DRI, operating system, rhythm | `cs-coo-advisor` |\n| hiring, comp, ladder, level, attrition, eNPS, equity | `cs-chro-advisor` |\n| security, threat, breach, compliance, audit, SOC 2 | `cs-ciso-advisor` |\n| architecture, scaling, tech debt, SLO, latency | `cs-cto-advisor` |\n| contract, IP, term sheet, regulator, license | `cs-general-counsel-advisor` |\n| retention, GRR, NRR, churn, customer success, CSM, time-to-value, renewals | `cs-cco-advisor` |\n| training data, data rights, consent, data asset, warehouse, lakehouse, data mesh | `cs-cdo-advisor` |\n| model selection, eval, hallucination, AI risk, EU AI Act, fine-tune, build vs buy AI | `cs-caio-advisor` |\n| DORA, cycle time, deploy frequency, eng hiring funnel, team topology, delivery throughput | `cs-vpe-advisor` |\n| strategy, vision, board, M&A, raise, exit | `cs-ceo-advisor` |\n| **2+ signals from different roles** | `\u002Fcs:boardroom` |\n| **ambiguous** | `\u002Fcs:office-hours` first, then route |\n\n## Workflow\n\n1. Parse the question for role signals\n2. If exactly one role: invoke that cs-* agent directly\n3. If 2+ roles: build a brief via `\u002Fcs:brief` and trigger `\u002Fcs:boardroom`\n4. If ambiguous \u002F no signal match: trigger `\u002Fcs:office-hours` to force the founder to sharpen\n5. Log the routing decision (raw layer) via `decision-logger`\n\n## Output\n\nThe router emits one of three responses:\n\n### Single-role route\n```\n**Routing:** cs-cfo-advisor\n**Why:** Question hits burn rate and unit economics.\n**Next:** Invoking cs-cfo-advisor with company-context loaded.\n\n[Advisor's response follows]\n```\n\n### Multi-role route\n```\n**Routing:** \u002Fcs:boardroom\n**Why:** Question touches CFO + CMO + CPO (pricing change has finance, positioning, and product implications).\n**Next:** Building brief via \u002Fcs:brief, then running boardroom.\n\nBrief saved: ~\u002F.claude\u002Fbriefs\u002F2026-05-12-pricing-v3.md\nRun: \u002Fcs:boardroom ~\u002F.claude\u002Fbriefs\u002F2026-05-12-pricing-v3.md\n```\n\n### Ambiguous → office hours\n```\n**Routing:** \u002Fcs:office-hours\n**Why:** Question is too broad (\"should we grow faster?\"). Need framing before any advisor can help.\n**Next:** Six-question intake.\n\n[Office hours questions follow]\n```\n\n## Why This Is the Killer Command\n\ngstack requires the founder to know all 23 slash commands and pick the right one. That's a cognitive tax. `\u002Fcs:founder-mode` collapses that to one — the system picks. This is also where persistent memory pays off: with company-context.md + decision-logger, the router knows what's already been decided and won't re-litigate.\n\n## Examples\n\n```\n\u002Fcs:founder-mode \"should we raise a Series B now or wait 6 months?\"\n   → boardroom (CFO + CEO + CRO touched)\n\n\u002Fcs:founder-mode \"the win rate dropped 20% this month\"\n   → cs-cro-advisor\n\n\u002Fcs:founder-mode \"gross retention dropped 5 points this quarter\"\n   → cs-cco-advisor\n\n\u002Fcs:founder-mode \"let's hire a VP Marketing\"\n   → boardroom (CHRO + CMO + CFO touched)\n\n\u002Fcs:founder-mode \"should we be growing faster?\"\n   → \u002Fcs:office-hours (too ambiguous)\n```\n\n## Related\n\n- Agent: [`cs-chief-of-staff`](..\u002F..\u002Fagents\u002Fcs-chief-of-staff.md) — does the routing\n- Skill: [`chief-of-staff`](..\u002F..\u002F..\u002Fskills\u002Fchief-of-staff\u002FSKILL.md) — routing logic\n- Skill: [`context-engine`](..\u002F..\u002F..\u002Fskills\u002Fcontext-engine\u002FSKILL.md) — loads context\n\n---\n\n**Version:** 1.0.0\n","# \u002Fcs:founder-mode — The Auto-Router\n\n**Command:** `\u002Fcs:founder-mode \u003Cquestion>`\n\nThe single command a founder needs to remember. Routes the question to the right C-role automatically, or triggers `\u002Fcs:boardroom` if multi-role.\n\nThis is the **killer command** — the answer to \"I don't know which slash command to use.\" Type the question; the system figures out the room.\n\n## Routing Logic\n\nThe router (via `cs-chief-of-staff`) does keyword + intent matching:\n\n| Signal in question | Route |\n|---|---|\n| burn, runway, fundraise, dilution, model, LTV, CAC | `cs-cfo-advisor` |\n| pipeline, win rate, forecast, quota, ramp, sales motion | `cs-cro-advisor` |\n| positioning, ICP, message, brand, channel, campaign | `cs-cmo-advisor` |\n| roadmap, PMF, JTBD, North Star, RICE, kill | `cs-cpo-advisor` |\n| cadence, OKR, scorecard, DRI, operating system, rhythm | `cs-coo-advisor` |\n| hiring, comp, ladder, level, attrition, eNPS, equity | `cs-chro-advisor` |\n| security, threat, breach, compliance, audit, SOC 2 | `cs-ciso-advisor` |\n| architecture, scaling, tech debt, SLO, latency | `cs-cto-advisor` |\n| contract, IP, term sheet, regulator, license | `cs-general-counsel-advisor` |\n| retention, GRR, NRR, churn, customer success, CSM, time-to-value, renewals | `cs-cco-advisor` |\n| training data, data rights, consent, data asset, warehouse, lakehouse, data mesh | `cs-cdo-advisor` |\n| model selection, eval, hallucination, AI risk, EU AI Act, fine-tune, build vs buy AI | `cs-caio-advisor` |\n| DORA, cycle time, deploy frequency, eng hiring funnel, team topology, delivery throughput | `cs-vpe-advisor` |\n| strategy, vision, board, M&A, raise, exit | `cs-ceo-advisor` |\n| **2+ signals from different roles** | `\u002Fcs:boardroom` |\n| **ambiguous** | `\u002Fcs:office-hours` first, then route |\n\n## Workflow\n\n1. Parse the question for role signals\n2. If exactly one role: invoke that cs-* agent directly\n3. If 2+ roles: build a brief via `\u002Fcs:brief` and trigger `\u002Fcs:boardroom`\n4. If ambiguous \u002F no signal match: trigger `\u002Fcs:office-hours` to force the founder to sharpen\n5. Log the routing decision (raw layer) via `decision-logger`\n\n## Output\n\nThe router emits one of three responses:\n\n### Single-role route\n```\n**Routing:** cs-cfo-advisor\n**Why:** Question hits burn rate and unit economics.\n**Next:** Invoking cs-cfo-advisor with company-context loaded.\n\n[Advisor's response follows]\n```\n\n### Multi-role route\n```\n**Routing:** \u002Fcs:boardroom\n**Why:** Question touches CFO + CMO + CPO (pricing change has finance, positioning, and product implications).\n**Next:** Building brief via \u002Fcs:brief, then running boardroom.\n\nBrief saved: ~\u002F.claude\u002Fbriefs\u002F2026-05-12-pricing-v3.md\nRun: \u002Fcs:boardroom ~\u002F.claude\u002Fbriefs\u002F2026-05-12-pricing-v3.md\n```\n\n### Ambiguous → office hours\n```\n**Routing:** \u002Fcs:office-hours\n**Why:** Question is too broad (\"should we grow faster?\"). Need framing before any advisor can help.\n**Next:** Six-question intake.\n\n[Office hours questions follow]\n```\n\n## Why This Is the Killer Command\n\ngstack requires the founder to know all 23 slash commands and pick the right one. That's a cognitive tax. `\u002Fcs:founder-mode` collapses that to one — the system picks. This is also where persistent memory pays off: with company-context.md + decision-logger, the router knows what's already been decided and won't re-litigate.\n\n## Examples\n\n```\n\u002Fcs:founder-mode \"should we raise a Series B now or wait 6 months?\"\n   → boardroom (CFO + CEO + CRO touched)\n\n\u002Fcs:founder-mode \"the win rate dropped 20% this month\"\n   → cs-cro-advisor\n\n\u002Fcs:founder-mode \"gross retention dropped 5 points this quarter\"\n   → cs-cco-advisor\n\n\u002Fcs:founder-mode \"let's hire a VP Marketing\"\n   → boardroom (CHRO + CMO + CFO touched)\n\n\u002Fcs:founder-mode \"should we be growing faster?\"\n   → \u002Fcs:office-hours (too ambiguous)\n```\n\n## Related\n\n- Agent: [`cs-chief-of-staff`](..\u002F..\u002Fagents\u002Fcs-chief-of-staff.md) — does the routing\n- Skill: [`chief-of-staff`](..\u002F..\u002F..\u002Fskills\u002Fchief-of-staff\u002FSKILL.md) — routing logic\n- Skill: [`context-engine`](..\u002F..\u002F..\u002Fskills\u002Fcontext-engine\u002FSKILL.md) — loads context\n\n---\n\n**Version:** 1.0.0\n",{"name":5,"description":7},"main","b4ebd6d8c3b36347a5d435bcb343a5fc1c6f08d1","skills-library\u002Fc-level-advisor\u002Fc-level-agents\u002Fskills\u002Ffounder-mode","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 founder-mode",{"tool":35,"command":36},"bunx","bunx skills add TehutiRaEl\u002FTHEHIVE --skill founder-mode",{"tool":38,"command":39},"pnpm","pnpm dlx skills add TehutiRaEl\u002FTHEHIVE --skill founder-mode","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fc-level-advisor\u002Fc-level-agents\u002Fskills\u002Ffounder-mode\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",[],[]]