[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M783AYNXEVC5B2B83VS2RYGF":3,"skill-same:01M783AYNXEVC5B2B83VS2RYGF":44},{"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":6,"updatedAt":29,"install":30,"resources":43},"01M783AYNXEVC5B2B83VS2RYGF","board-prep",null,"Board meeting preparation for the adversarial scenario, not the friendly one. Forces numbers-cold mastery, anticipates hard questions, builds a narrative that acknowledges weakness without losing the room. Use when preparing for a board meeting, an investor update, fundraising presentation, or any high-stakes adversarial review where every number must live in your head not just on a slide.","motivatedc-creator\u002FSaafy","motivatedc-creator","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F250662783?v=4","01M782H2D8C7XJGXMJC3YHQAWK","Happy Haris","01M782H2ERMBYEM1NSPPPC06S0",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fexecutive-mentor\u002Fskills\u002Fboard-prep\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"board-prep\"\ndescription: \"Board meeting preparation for the adversarial scenario, not the friendly one. Forces numbers-cold mastery, anticipates hard questions, builds a narrative that acknowledges weakness without losing the room. Use when preparing for a board meeting, an investor update, fundraising presentation, or any high-stakes adversarial review where every number must live in your head not just on a slide.\"\n---\n\n# \u002Fem:board-prep — Board Meeting Preparation\n\n**Command:** `\u002Fem:board-prep \u003Cagenda>`\n\nPrepare for the adversarial version of your board, not the friendly one. Every hard question they'll ask. Every number you need cold. The narrative that acknowledges weakness without losing the room.\n\n---\n\n## The Reality of Board Meetings\n\nYour board members have seen 50+ companies. They've watched founders flinch at their own numbers, spin bad news as \"learning opportunities,\" and present sanitized decks that hide what's actually happening.\n\nThey know when you're not being straight with them. The question isn't whether they'll ask the hard questions — it's whether you're ready for them.\n\nThe best board meetings aren't the ones where everything looks good. They're the ones where the CEO demonstrates they see reality clearly, have a plan, and can execute under pressure.\n\n---\n\n## The Preparation Framework\n\n### Phase 1: Numbers Cold\n\nBefore the meeting, every number in your deck should live in your head, not just the slide.\n\n**The numbers you must know without looking:**\n- Current MRR \u002F ARR and month-over-month growth rate\n- Burn rate (monthly) and runway (months at current burn)\n- Headcount by department\n- CAC and LTV by channel \u002F segment\n- Net Revenue Retention\n- Pipeline: value, conversion rate, average sales cycle\n- Churn: rate, top reasons, top churned accounts\n- Gross margin (product), net margin (company)\n- Key hiring positions open and time-to-fill\n\n**Stress test yourself:** Can you answer \"what's your burn?\" without hesitation? \"What's your churn rate by segment?\" If you pause, you don't know it.\n\n### Phase 2: Anticipate the Hard Questions\n\nFor every item on the agenda, generate the adversarial version of the question.\n\n**Standard adversarial questions by topic:**\n\n*Revenue performance:*\n- \"You missed revenue by 20% this quarter. What specifically failed?\"\n- \"Is this a pipeline problem, a conversion problem, or a capacity problem?\"\n- \"If you missed because of one big deal, how dependent is your model on individual deals?\"\n- \"When do you project recovery and what are the leading indicators you're right?\"\n\n*Runway \u002F burn:*\n- \"At current burn you have N months. What's your plan if the next round takes 9 months?\"\n- \"What would you cut first if you had to extend runway by 6 months today?\"\n- \"Is there a scenario where you don't raise another round?\"\n\n*Product \u002F roadmap:*\n- \"You shipped X. What did customers actually do with it?\"\n- \"What did you kill this quarter and why?\"\n- \"Where are you behind on roadmap? What's slipping?\"\n\n*Team:*\n- \"Who's at risk of leaving? How would that affect execution?\"\n- \"You've had 3 VP-level hires not work out. What pattern do you see?\"\n- \"Is the team the right team for this stage?\"\n\n*Competition:*\n- \"Competitor Y just raised $50M. How does that change your position?\"\n- \"If they copy your best feature in 90 days, what's your moat?\"\n\n### Phase 3: Build the Narrative\n\nThe board meeting isn't a status update. It's a leadership demonstration.\n\n**The structure that works:**\n\n1. **Where we are (honest)** — Current state of business, the real number, not the smoothed one\n2. **What we learned** — What the data is telling us that we didn't know 90 days ago\n3. **What we got wrong** — Name it directly. Don't make them ask.\n4. **What we're doing about it** — Specific, dated, owned actions\n5. **What we need from this room** — Concrete ask. Not \"support\" — specific introductions, decisions, resources.\n\n**The rule on bad news:** Never let the board be surprised. If a quarter went badly, they should know before the deck. A 5-sentence email 3 days before: \"Revenue came in at $X vs $Y target. Here's what happened, here's what I'm doing, here's what I need from you.\"\n\n### Phase 4: Adversarial Preparation\n\nDo a mock board meeting. Have someone play the hardest director you have.\n\n**The simulation:**\n- Present your deck as you would\n- The mock director asks every uncomfortable question\n- You answer without referring to the deck\n- After: note every question that made you pause or feel defensive\n\n**The questions that made you defensive = the questions you need to prepare for.**\n\n### Phase 5: Director-by-Director Prep\n\nNot all board members want the same thing from a meeting.\n\n**For each director, know:**\n- Their primary concern right now (usually tied to their investment thesis)\n- The metric they watch most closely\n- What would make them lose confidence in you\n- What they've said in the last meeting that you should address\n\n**Common director types:**\n- **The operator** — wants to know what's breaking and who owns fixing it\n- **The financial investor** — focused on path to profitability or next raise\n- **The strategic investor** — worried about competitive position and moat\n- **The independent** — watching governance, team dynamics, and your judgment\n\n---\n\n## Pre-Meeting Checklist\n\n**48 hours before:**\n- [ ] All numbers verified against source systems (not last week's export)\n- [ ] Deck reviewed for internal consistency\n- [ ] Pre-read sent to board (deck + 1-page brief on key topics)\n- [ ] One-on-ones done with any director likely to have concerns\n- [ ] 3 hardest questions you expect — rehearsed out loud\n\n**Day of meeting:**\n- [ ] Agenda with time allocations distributed\n- [ ] Know the ask for each agenda item (decision needed, input wanted, FYI)\n- [ ] Materials to leave behind prepared\n- [ ] Follow-up action template ready\n\n---\n\n## During the Meeting\n\n**What the board is watching:**\n- Do you own the bad news or deflect it?\n- Are you defending a narrative or sharing reality?\n- Do you know your numbers or do you look things up?\n- When challenged, do you get defensive or engage?\n- Do you know what you don't know?\n\n**The single best thing you can do:** Name the hard thing before they do. \"I want to address the revenue miss directly. Here's what happened, here's what I should have caught earlier, here's what changes.\"\n\n---\n\n## After the Meeting\n\nWithin 24 hours:\n- Send action items with owners and dates\n- Send any data you promised but didn't have\n- Note the questions that came up you weren't ready for\n- Schedule follow-up with any director who seemed unsatisfied\n\nThe next board prep starts now.\n","# \u002Fem:board-prep — Board Meeting Preparation\n\n**Command:** `\u002Fem:board-prep \u003Cagenda>`\n\nPrepare for the adversarial version of your board, not the friendly one. Every hard question they'll ask. Every number you need cold. The narrative that acknowledges weakness without losing the room.\n\n---\n\n## The Reality of Board Meetings\n\nYour board members have seen 50+ companies. They've watched founders flinch at their own numbers, spin bad news as \"learning opportunities,\" and present sanitized decks that hide what's actually happening.\n\nThey know when you're not being straight with them. The question isn't whether they'll ask the hard questions — it's whether you're ready for them.\n\nThe best board meetings aren't the ones where everything looks good. They're the ones where the CEO demonstrates they see reality clearly, have a plan, and can execute under pressure.\n\n---\n\n## The Preparation Framework\n\n### Phase 1: Numbers Cold\n\nBefore the meeting, every number in your deck should live in your head, not just the slide.\n\n**The numbers you must know without looking:**\n- Current MRR \u002F ARR and month-over-month growth rate\n- Burn rate (monthly) and runway (months at current burn)\n- Headcount by department\n- CAC and LTV by channel \u002F segment\n- Net Revenue Retention\n- Pipeline: value, conversion rate, average sales cycle\n- Churn: rate, top reasons, top churned accounts\n- Gross margin (product), net margin (company)\n- Key hiring positions open and time-to-fill\n\n**Stress test yourself:** Can you answer \"what's your burn?\" without hesitation? \"What's your churn rate by segment?\" If you pause, you don't know it.\n\n### Phase 2: Anticipate the Hard Questions\n\nFor every item on the agenda, generate the adversarial version of the question.\n\n**Standard adversarial questions by topic:**\n\n*Revenue performance:*\n- \"You missed revenue by 20% this quarter. What specifically failed?\"\n- \"Is this a pipeline problem, a conversion problem, or a capacity problem?\"\n- \"If you missed because of one big deal, how dependent is your model on individual deals?\"\n- \"When do you project recovery and what are the leading indicators you're right?\"\n\n*Runway \u002F burn:*\n- \"At current burn you have N months. What's your plan if the next round takes 9 months?\"\n- \"What would you cut first if you had to extend runway by 6 months today?\"\n- \"Is there a scenario where you don't raise another round?\"\n\n*Product \u002F roadmap:*\n- \"You shipped X. What did customers actually do with it?\"\n- \"What did you kill this quarter and why?\"\n- \"Where are you behind on roadmap? What's slipping?\"\n\n*Team:*\n- \"Who's at risk of leaving? How would that affect execution?\"\n- \"You've had 3 VP-level hires not work out. What pattern do you see?\"\n- \"Is the team the right team for this stage?\"\n\n*Competition:*\n- \"Competitor Y just raised $50M. How does that change your position?\"\n- \"If they copy your best feature in 90 days, what's your moat?\"\n\n### Phase 3: Build the Narrative\n\nThe board meeting isn't a status update. It's a leadership demonstration.\n\n**The structure that works:**\n\n1. **Where we are (honest)** — Current state of business, the real number, not the smoothed one\n2. **What we learned** — What the data is telling us that we didn't know 90 days ago\n3. **What we got wrong** — Name it directly. Don't make them ask.\n4. **What we're doing about it** — Specific, dated, owned actions\n5. **What we need from this room** — Concrete ask. Not \"support\" — specific introductions, decisions, resources.\n\n**The rule on bad news:** Never let the board be surprised. If a quarter went badly, they should know before the deck. A 5-sentence email 3 days before: \"Revenue came in at $X vs $Y target. Here's what happened, here's what I'm doing, here's what I need from you.\"\n\n### Phase 4: Adversarial Preparation\n\nDo a mock board meeting. Have someone play the hardest director you have.\n\n**The simulation:**\n- Present your deck as you would\n- The mock director asks every uncomfortable question\n- You answer without referring to the deck\n- After: note every question that made you pause or feel defensive\n\n**The questions that made you defensive = the questions you need to prepare for.**\n\n### Phase 5: Director-by-Director Prep\n\nNot all board members want the same thing from a meeting.\n\n**For each director, know:**\n- Their primary concern right now (usually tied to their investment thesis)\n- The metric they watch most closely\n- What would make them lose confidence in you\n- What they've said in the last meeting that you should address\n\n**Common director types:**\n- **The operator** — wants to know what's breaking and who owns fixing it\n- **The financial investor** — focused on path to profitability or next raise\n- **The strategic investor** — worried about competitive position and moat\n- **The independent** — watching governance, team dynamics, and your judgment\n\n---\n\n## Pre-Meeting Checklist\n\n**48 hours before:**\n- [ ] All numbers verified against source systems (not last week's export)\n- [ ] Deck reviewed for internal consistency\n- [ ] Pre-read sent to board (deck + 1-page brief on key topics)\n- [ ] One-on-ones done with any director likely to have concerns\n- [ ] 3 hardest questions you expect — rehearsed out loud\n\n**Day of meeting:**\n- [ ] Agenda with time allocations distributed\n- [ ] Know the ask for each agenda item (decision needed, input wanted, FYI)\n- [ ] Materials to leave behind prepared\n- [ ] Follow-up action template ready\n\n---\n\n## During the Meeting\n\n**What the board is watching:**\n- Do you own the bad news or deflect it?\n- Are you defending a narrative or sharing reality?\n- Do you know your numbers or do you look things up?\n- When challenged, do you get defensive or engage?\n- Do you know what you don't know?\n\n**The single best thing you can do:** Name the hard thing before they do. \"I want to address the revenue miss directly. Here's what happened, here's what I should have caught earlier, here's what changes.\"\n\n---\n\n## After the Meeting\n\nWithin 24 hours:\n- Send action items with owners and dates\n- Send any data you promised but didn't have\n- Note the questions that came up you weren't ready for\n- Schedule follow-up with any director who seemed unsatisfied\n\nThe next board prep starts now.\n",{"name":5,"description":7},"main","55ae24ca5523c0499dd70b2874ef674a0e66a85b","c-level-advisor\u002Fexecutive-mentor\u002Fskills\u002Fboard-prep","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator","2026-07-04 02:45:55",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add motivatedc-creator\u002FSaafy --skill board-prep",{"tool":36,"command":37},"bunx","bunx skills add motivatedc-creator\u002FSaafy --skill board-prep",{"tool":39,"command":40},"pnpm","pnpm dlx skills add motivatedc-creator\u002FSaafy --skill board-prep","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fexecutive-mentor\u002Fskills\u002Fboard-prep\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":19},"01M78558T3RQ22S1B5H0FJAY1Y","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\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7854YEAAV883M2PKS04TQEK","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\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7854NCGDBQ6Q0QG2YY4VHSX","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\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M78549YZMPYGC1F6S7ZJ4VF8","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\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M78541PWEQMBPN91PEZZK8H7","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7853P7CWJNW5G0Z99YB6H5D","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.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' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., '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 use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[]]