[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D7JGK8E59MTWM5CA60GCGD":3,"skill-same:01M7D7JGK8E59MTWM5CA60GCGD":45},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7D7JGK8E59MTWM5CA60GCGD","office-hours",null,"\u002Fcs:office-hours \u003Ctopic> — YC-style 6-question founder interrogation before any advice. Forces clarity on problem, customer, distribution, defensibility, capital, and founder fit.","Mabbit143\u002FClaude-SKills","Mabbit143","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F192994237?v=4","01M7D6X2W63K4T3N13CSVAKE3V","Mabbit Rountree","01M7D6X2WRPSZF8VMW9MW5ZP1X",0,"MIT","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fc-level-advisor\u002Fc-level-agents\u002Fskills\u002Foffice-hours\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"office-hours\"\ndescription: \"\u002Fcs:office-hours \u003Ctopic> — YC-style 6-question founder interrogation before any advice. Forces clarity on problem, customer, distribution, defensibility, capital, and founder fit.\"\n---\n\n# \u002Fcs:office-hours — Six-Question Founder Interrogation\n\n**Command:** `\u002Fcs:office-hours \u003Ctopic>`\n\nBefore any advice, the founder must answer six questions. Modeled on YC office hours: no analysis until the founder has done the thinking. This is the cognitive forcing function that prevents drift into solutionism.\n\n## When to Run\n\n- Before starting any major initiative\n- Before fundraising\n- Before a strategic pivot\n- When the founder is excited (excitement is a tell — pressure-test)\n- When the answer is \"obvious\" (the obvious answer is usually wrong)\n\n## The Six Questions\n\nThe founder must answer **all six** in writing before any C-role weighs in.\n\n### 1. Problem\n**Whose problem is this, and how do they describe it in their own words?**\n- Not your framing. Their words.\n- If you can't quote a customer, you don't have a problem worth solving.\n\n### 2. Customer\n**Who is the ICP? Name one real person who would buy this today.**\n- Real human. Real company. Real seat.\n- If you can't name one, the ICP isn't ready.\n\n### 3. Distribution\n**How does the customer first hear your name?**\n- Channel, intent, search query, friend, conference — name it.\n- If the answer is \"we'll figure out marketing later,\" the answer is no.\n\n### 4. Defensibility\n**If this works, what stops a competitor from copying it in 6 months?**\n- Network effects, switching costs, data moat, regulatory moat, brand — pick one.\n- \"We'll execute better\" is not a defense.\n\n### 5. Capital\n**What does this cost, when does it pay back, and what's the alternative use of the money?**\n- Total spend, payback months, opportunity cost.\n- If you don't know, don't approve it.\n\n### 6. Founder Fit\n**Why are you the right person to do this — and why does this matter enough to spend the next 3 years on it?**\n- Founder-market fit is the strongest predictor of survival.\n- If the answer is mercenary, the company will be too.\n\n## Output Format\n\nAfter the founder answers all six, this command produces a one-page brief:\n\n```markdown\n# Office Hours Brief: \u003Ctopic>\n**Date:** YYYY-MM-DD\n**Founder:** \u003Cname>\n\n## 1. Problem\n> [founder's verbatim answer]\n\n## 2. Customer\n> [founder's verbatim answer]\n\n## 3. Distribution\n> [founder's verbatim answer]\n\n## 4. Defensibility\n> [founder's verbatim answer]\n\n## 5. Capital\n> [founder's verbatim answer]\n\n## 6. Founder Fit\n> [founder's verbatim answer]\n\n---\n\n**Assessment** (one of):\n- 🟢 GREEN — ship the brief to \u002Fcs:boardroom\n- 🟡 YELLOW — sharpen Q[N] before proceeding\n- 🔴 RED — kill or redefine; do not proceed\n```\n\n## Routing\n\nAfter the brief is GREEN, route to:\n- Single-role question → corresponding `\u002Fcs:{role}-review`\n- Multi-role question → `\u002Fcs:brief` then `\u002Fcs:boardroom`\n\n## Why This Works\n\nMost bad decisions don't fail at execution — they fail at framing. Forcing six concrete answers surfaces the framing weaknesses before anyone burns time on analysis. The founder either fills the gaps or recognizes the question wasn't ready.\n\nThis is the YC `office hours` pattern adapted for Claude Code: the interrogation is the value.\n\n## Related Commands\n\n- `\u002Fcs:brief` — turn the answers into a one-page strategy brief\n- `\u002Fcs:boardroom` — multi-role deliberation\n- `\u002Fcs:founder-mode` — let the system pick the next step\n\n## Related Agents\n\n- All cs-* advisors consume the brief output\n- `cs-chief-of-staff` triggers `\u002Fcs:office-hours` when intake is unclear\n\n---\n\n**Version:** 1.0.0\n","# \u002Fcs:office-hours — Six-Question Founder Interrogation\n\n**Command:** `\u002Fcs:office-hours \u003Ctopic>`\n\nBefore any advice, the founder must answer six questions. Modeled on YC office hours: no analysis until the founder has done the thinking. This is the cognitive forcing function that prevents drift into solutionism.\n\n## When to Run\n\n- Before starting any major initiative\n- Before fundraising\n- Before a strategic pivot\n- When the founder is excited (excitement is a tell — pressure-test)\n- When the answer is \"obvious\" (the obvious answer is usually wrong)\n\n## The Six Questions\n\nThe founder must answer **all six** in writing before any C-role weighs in.\n\n### 1. Problem\n**Whose problem is this, and how do they describe it in their own words?**\n- Not your framing. Their words.\n- If you can't quote a customer, you don't have a problem worth solving.\n\n### 2. Customer\n**Who is the ICP? Name one real person who would buy this today.**\n- Real human. Real company. Real seat.\n- If you can't name one, the ICP isn't ready.\n\n### 3. Distribution\n**How does the customer first hear your name?**\n- Channel, intent, search query, friend, conference — name it.\n- If the answer is \"we'll figure out marketing later,\" the answer is no.\n\n### 4. Defensibility\n**If this works, what stops a competitor from copying it in 6 months?**\n- Network effects, switching costs, data moat, regulatory moat, brand — pick one.\n- \"We'll execute better\" is not a defense.\n\n### 5. Capital\n**What does this cost, when does it pay back, and what's the alternative use of the money?**\n- Total spend, payback months, opportunity cost.\n- If you don't know, don't approve it.\n\n### 6. Founder Fit\n**Why are you the right person to do this — and why does this matter enough to spend the next 3 years on it?**\n- Founder-market fit is the strongest predictor of survival.\n- If the answer is mercenary, the company will be too.\n\n## Output Format\n\nAfter the founder answers all six, this command produces a one-page brief:\n\n```markdown\n# Office Hours Brief: \u003Ctopic>\n**Date:** YYYY-MM-DD\n**Founder:** \u003Cname>\n\n## 1. Problem\n> [founder's verbatim answer]\n\n## 2. Customer\n> [founder's verbatim answer]\n\n## 3. Distribution\n> [founder's verbatim answer]\n\n## 4. Defensibility\n> [founder's verbatim answer]\n\n## 5. Capital\n> [founder's verbatim answer]\n\n## 6. Founder Fit\n> [founder's verbatim answer]\n\n---\n\n**Assessment** (one of):\n- 🟢 GREEN — ship the brief to \u002Fcs:boardroom\n- 🟡 YELLOW — sharpen Q[N] before proceeding\n- 🔴 RED — kill or redefine; do not proceed\n```\n\n## Routing\n\nAfter the brief is GREEN, route to:\n- Single-role question → corresponding `\u002Fcs:{role}-review`\n- Multi-role question → `\u002Fcs:brief` then `\u002Fcs:boardroom`\n\n## Why This Works\n\nMost bad decisions don't fail at execution — they fail at framing. Forcing six concrete answers surfaces the framing weaknesses before anyone burns time on analysis. The founder either fills the gaps or recognizes the question wasn't ready.\n\nThis is the YC `office hours` pattern adapted for Claude Code: the interrogation is the value.\n\n## Related Commands\n\n- `\u002Fcs:brief` — turn the answers into a one-page strategy brief\n- `\u002Fcs:boardroom` — multi-role deliberation\n- `\u002Fcs:founder-mode` — let the system pick the next step\n\n## Related Agents\n\n- All cs-* advisors consume the brief output\n- `cs-chief-of-staff` triggers `\u002Fcs:office-hours` when intake is unclear\n\n---\n\n**Version:** 1.0.0\n",{"name":5,"description":7},"claude\u002Fregistry-repo-7lRiv","44e1a5b2d387b250bcd0794f7eb5e1228223d1e2","c-level-advisor\u002Fc-level-agents\u002Fskills\u002Foffice-hours","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills","https:\u002F\u002Fgithub.com\u002FMabbit143","I’m edgy and fun, probably too serious, but I love an adventure.","2026-09-22 07:56:32",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add Mabbit143\u002FClaude-SKills --skill office-hours",{"tool":37,"command":38},"bunx","bunx skills add Mabbit143\u002FClaude-SKills --skill office-hours",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Mabbit143\u002FClaude-SKills --skill office-hours","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fc-level-advisor\u002Fc-level-agents\u002Fskills\u002Foffice-hours\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7D99ZA4F916M5CM3K2EQFE8","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. Triggers whenever a user uploads a syllabus, course outline, or curriculum document and wants supplementary readings. Also triggers on: 'syllabus reading list', 'find papers for my course', 'create a reading list from this syllabus', 'recent research for my class', 'supplementary readings', 'find journal articles for these topics', 'what recent papers cover this material', 'any new research on these course topics', 'update my syllabus with recent papers'. Even casual mentions when a syllabus is attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7D99ND4B38EG1BYQX722F5D","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. Triggers — \"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]\", or any research request that doesn't obviously match a more-specific specialist skill. Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7D999VS936SV9TX940A98AQ","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. Triggers: '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]', or any variation requesting multi-source recency intelligence on a topic. Also use for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7D98XBECS6368GEJNG8C1Z1","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. Triggers: 'prior art search for [invention]', 'patent search on [topic]', 'freedom to operate analysis', 'FTO for [product]', 'patent landscape for [field]', 'is [invention] novel', 'patents on [topic]', 'competitive patent analysis', 'prior art for litigation', 'patent diligence on [company]'. 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\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7D98N2R7CA7RM00PNP4VV6C","notebooklm","Browser automation skill for controlling Google's NotebookLM. Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio Overview, infographics, slide decks, study guides, briefing docs, mind maps, timelines, FAQs), and creating new notebooks. Triggers on any phrase involving NotebookLM — 'open NotebookLM', 'check my [name] notebook', 'pull info from NotebookLM', 'ask my notebook about X', 'add [source] to NotebookLM', 'create an infographic in NotebookLM', 'use NotebookLM Studio', 'generate a slide deck from my notebook', or any variation where the goal involves NotebookLM. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7D98B1SCTS4RAWZFCF9QJ5M","litreview","Academic literature orientation skill that searches papers via Consensus, builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a professionally formatted Word document (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — not a finished review, but an orientation guide that lets a researcher dive in confidently. Triggers: 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'. Do NOT trigger for single one-off paper searches where the user just wants a quick list — that's a plain Consensus search.","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[]]