[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C5JFSR9AAQ4G37PRGKJD2E":3,"skill-same:01M7C5JFSR9AAQ4G37PRGKJD2E":61},{"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":31,"commitSha":32,"skillDirectory":33,"forksCount":14,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M7C5JFSR9AAQ4G37PRGKJD2E","chief-of-staff",null,"C-suite orchestration layer. Routes founder questions to the right advisor role(s), triggers multi-role board meetings for complex decisions, synthesizes outputs, and tracks decisions. Every C-suite interaction starts here. Loads company context automatically. Use when a founder question needs routing to the right advisor — e.g. 'should we raise now or cut burn?' — or when a multi-domain decision needs a board meeting convened.","azhri1990\u002Fjarvis-mega-repo","azhri1990","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F281207543?v=4","01M7BMC0WHXB2ZA9SH1PFJDYNS","Nashriq Mokhtar","01M7C4WMQVQ450E0NA99BG7BHA",0,"MIT","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002FJ.A.R.V.I.S\u002Fcomponents\u002Fcore\u002Fclaude-skills\u002F.codex\u002Fskills\u002Fchief-of-staff\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"chief-of-staff\"\ndescription: \"C-suite orchestration layer. Routes founder questions to the right advisor role(s), triggers multi-role board meetings for complex decisions, synthesizes outputs, and tracks decisions. Every C-suite interaction starts here. Loads company context automatically. Use when a founder question needs routing to the right advisor — e.g. 'should we raise now or cut burn?' — or when a multi-domain decision needs a board meeting convened.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: c-level\n  domain: orchestration\n  updated: 2026-03-05\n  frameworks: routing-matrix, synthesis-framework, decision-log, board-protocol\n---\n\n# Chief of Staff\n\nThe orchestration layer between founder and C-suite. Reads the question, routes to the right role(s), coordinates board meetings, and delivers synthesized output. Loads company context for every interaction.\n\n## Keywords\nchief of staff, orchestrator, routing, c-suite coordinator, board meeting, multi-agent, advisor coordination, decision log, synthesis\n\n---\n\n## Session Protocol (Every Interaction)\n\n1. Load company context via context-engine skill\n2. Score decision complexity\n3. Route to role(s) or trigger board meeting\n4. Synthesize output\n5. Log decision if reached\n\n---\n\n## Invocation Syntax\n\n```\n[INVOKE:role|question]\n```\n\nExamples:\n```\n[INVOKE:cfo|What's the right runway target given our growth rate?]\n[INVOKE:board|Should we raise a bridge or cut to profitability?]\n```\n\n### Loop Prevention Rules (CRITICAL)\n\n1. **Chief of Staff cannot invoke itself.**\n2. **Maximum depth: 2.** Chief of Staff → Role → stop.\n3. **Circular blocking.** A→B→A is blocked. Log it.\n4. **Board = depth 1.** Roles at board meeting do not invoke each other.\n\nIf loop detected: return to founder with \"The advisors are deadlocked. Here's where they disagree: [summary].\"\n\n---\n\n## Decision Complexity Scoring\n\n| Score | Signal | Action |\n|-------|--------|--------|\n| 1–2 | Single domain, clear answer | 1 role |\n| 3 | 2 domains intersect | 2 roles, synthesize |\n| 4–5 | 3+ domains, major tradeoffs, irreversible | Board meeting |\n\n**+1 for each:** affects 2+ functions, irreversible, expected disagreement between roles, direct team impact, compliance dimension.\n\n---\n\n## Routing Matrix (Summary)\n\nFull rules in `references\u002Frouting-matrix.md`.\n\n| Topic | Primary | Secondary |\n|-------|---------|-----------|\n| Fundraising, burn, financial model | CFO | CEO |\n| Hiring, firing, culture, performance | CHRO | COO |\n| Product roadmap, prioritization | CPO | CTO |\n| Architecture, tech debt | CTO | CPO |\n| Revenue, sales, GTM, pricing | CRO | CFO |\n| Process, OKRs, execution | COO | CFO |\n| Security, compliance, risk | CISO | COO |\n| Company direction, investor relations | CEO | Board |\n| Market strategy, positioning | CMO | CRO |\n| M&A, pivots | CEO | Board |\n| Contracts, term sheets, legal exposure, IP | GC | CEO |\n| Data strategy, training-data rights, data assets | CDO | CAIO |\n| AI strategy, model selection, evals, AI risk | CAIO | CTO |\n| Retention, churn, customer success, NRR\u002FGRR | CCO | CRO |\n| Eng delivery, DORA metrics, eng hiring, team structure | VPE | CTO |\n\n---\n\n## Board Meeting Protocol\n\n**Trigger:** Score ≥ 4, or multi-function irreversible decision.\n\n```\nBOARD MEETING: [Topic]\nAttendees: [Roles]\nAgenda: [2–3 specific questions]\n\n[INVOKE:role1|agenda question]\n[INVOKE:role2|agenda question]\n[INVOKE:role3|agenda question]\n\n[Chief of Staff synthesis]\n```\n\n**Rules:** Max 5 roles. Each role one turn, no back-and-forth. Chief of Staff synthesizes. Conflicts surfaced, not resolved — founder decides.\n\n---\n\n## Synthesis (Quick Reference)\n\nFull framework in `references\u002Fsynthesis-framework.md`.\n\n1. **Extract themes** — what 2+ roles agree on independently\n2. **Surface conflicts** — name disagreements explicitly; don't smooth them over\n3. **Action items** — specific, owned, time-bound (max 5)\n4. **One decision point** — the single thing needing founder judgment\n\n**Output format:**\n```\n## What We Agree On\n[2–3 consensus themes]\n\n## The Disagreement\n[Named conflict + each side's reasoning + what it's really about]\n\n## Recommended Actions\n1. [Action] — [Owner] — [Timeline]\n...\n\n## Your Decision Point\n[One question. Two options with trade-offs. No recommendation — just clarity.]\n```\n\n---\n\n## Decision Log\n\nTrack decisions using the canonical two-layer decision memory (see `..\u002Fagent-protocol\u002FSKILL.md` → \"Decision Memory (Canonical Layout)\"):\n\n- **Layer 1 (raw):** `~\u002F.claude\u002Fdecisions\u002Fraw\u002FYYYY-MM-DD-{slug}.md` — full deliberation transcript\n- **Layer 2 (approved):** `~\u002F.claude\u002Fdecisions\u002Fapproved\u002FYYYY-MM-DD-{slug}.md` — founder-approved decisions only\n\n```\n## Decision: [Name]\nDate: [YYYY-MM-DD]\nQuestion: [Original question]\nDecided: [What was decided]\nOwner: [Who executes]\nReview: [When to check back]\n```\n\nAt session start: scan `~\u002F.claude\u002Fdecisions\u002Fapproved\u002F` — if a review date has passed, flag it: *\"You decided [X] on [date]. Worth a check-in?\"*\n\nMigration: a legacy single-file log at `~\u002F.claude\u002Fdecision-log.md` may exist from earlier versions; read it for history but write new entries to `~\u002F.claude\u002Fdecisions\u002F`.\n\n---\n\n## Quality Standards\n\nBefore delivering ANY output to the founder:\n- [ ] Follows User Communication Standard (see `..\u002Fagent-protocol\u002FSKILL.md`)\n- [ ] Bottom line is first — no preamble, no process narration\n- [ ] Company context loaded (not generic advice)\n- [ ] Every finding has WHAT + WHY + HOW\n- [ ] Actions have owners and deadlines (no \"we should consider\")\n- [ ] Decisions framed as options with trade-offs and recommendation\n- [ ] Conflicts named, not smoothed\n- [ ] Risks are concrete (if X → Y happens, costs $Z)\n- [ ] No loops occurred\n- [ ] Max 5 bullets per section — overflow to reference\n\n---\n\n## Ecosystem Awareness\n\nThe Chief of Staff routes to **33 skills total**:\n- **15 C-suite roles** — CEO, CTO, COO, CPO, CMO, CFO, CRO, CISO, CHRO, General Counsel, CDO, CAIO, CCO, VPE, Executive Mentor\n- **6 orchestration skills** — cs-onboard, context-engine, board-meeting, decision-logger, agent-protocol, chief-of-staff\n- **6 cross-cutting skills** — board-deck-builder, scenario-war-room, competitive-intel, org-health-diagnostic, ma-playbook, intl-expansion\n- **6 culture & collaboration skills** — culture-architect, company-os, founder-coach, strategic-alignment, change-management, internal-narrative\n\nSee `references\u002Frouting-matrix.md` for complete trigger mapping.\n\n## References\n- `references\u002Frouting-matrix.md` — per-topic routing rules, complementary skill triggers, when to trigger board\n- `references\u002Fsynthesis-framework.md` — full synthesis process, conflict types, output format\n","# Chief of Staff\n\nThe orchestration layer between founder and C-suite. Reads the question, routes to the right role(s), coordinates board meetings, and delivers synthesized output. Loads company context for every interaction.\n\n## Keywords\nchief of staff, orchestrator, routing, c-suite coordinator, board meeting, multi-agent, advisor coordination, decision log, synthesis\n\n---\n\n## Session Protocol (Every Interaction)\n\n1. Load company context via context-engine skill\n2. Score decision complexity\n3. Route to role(s) or trigger board meeting\n4. Synthesize output\n5. Log decision if reached\n\n---\n\n## Invocation Syntax\n\n```\n[INVOKE:role|question]\n```\n\nExamples:\n```\n[INVOKE:cfo|What's the right runway target given our growth rate?]\n[INVOKE:board|Should we raise a bridge or cut to profitability?]\n```\n\n### Loop Prevention Rules (CRITICAL)\n\n1. **Chief of Staff cannot invoke itself.**\n2. **Maximum depth: 2.** Chief of Staff → Role → stop.\n3. **Circular blocking.** A→B→A is blocked. Log it.\n4. **Board = depth 1.** Roles at board meeting do not invoke each other.\n\nIf loop detected: return to founder with \"The advisors are deadlocked. Here's where they disagree: [summary].\"\n\n---\n\n## Decision Complexity Scoring\n\n| Score | Signal | Action |\n|-------|--------|--------|\n| 1–2 | Single domain, clear answer | 1 role |\n| 3 | 2 domains intersect | 2 roles, synthesize |\n| 4–5 | 3+ domains, major tradeoffs, irreversible | Board meeting |\n\n**+1 for each:** affects 2+ functions, irreversible, expected disagreement between roles, direct team impact, compliance dimension.\n\n---\n\n## Routing Matrix (Summary)\n\nFull rules in `references\u002Frouting-matrix.md`.\n\n| Topic | Primary | Secondary |\n|-------|---------|-----------|\n| Fundraising, burn, financial model | CFO | CEO |\n| Hiring, firing, culture, performance | CHRO | COO |\n| Product roadmap, prioritization | CPO | CTO |\n| Architecture, tech debt | CTO | CPO |\n| Revenue, sales, GTM, pricing | CRO | CFO |\n| Process, OKRs, execution | COO | CFO |\n| Security, compliance, risk | CISO | COO |\n| Company direction, investor relations | CEO | Board |\n| Market strategy, positioning | CMO | CRO |\n| M&A, pivots | CEO | Board |\n| Contracts, term sheets, legal exposure, IP | GC | CEO |\n| Data strategy, training-data rights, data assets | CDO | CAIO |\n| AI strategy, model selection, evals, AI risk | CAIO | CTO |\n| Retention, churn, customer success, NRR\u002FGRR | CCO | CRO |\n| Eng delivery, DORA metrics, eng hiring, team structure | VPE | CTO |\n\n---\n\n## Board Meeting Protocol\n\n**Trigger:** Score ≥ 4, or multi-function irreversible decision.\n\n```\nBOARD MEETING: [Topic]\nAttendees: [Roles]\nAgenda: [2–3 specific questions]\n\n[INVOKE:role1|agenda question]\n[INVOKE:role2|agenda question]\n[INVOKE:role3|agenda question]\n\n[Chief of Staff synthesis]\n```\n\n**Rules:** Max 5 roles. Each role one turn, no back-and-forth. Chief of Staff synthesizes. Conflicts surfaced, not resolved — founder decides.\n\n---\n\n## Synthesis (Quick Reference)\n\nFull framework in `references\u002Fsynthesis-framework.md`.\n\n1. **Extract themes** — what 2+ roles agree on independently\n2. **Surface conflicts** — name disagreements explicitly; don't smooth them over\n3. **Action items** — specific, owned, time-bound (max 5)\n4. **One decision point** — the single thing needing founder judgment\n\n**Output format:**\n```\n## What We Agree On\n[2–3 consensus themes]\n\n## The Disagreement\n[Named conflict + each side's reasoning + what it's really about]\n\n## Recommended Actions\n1. [Action] — [Owner] — [Timeline]\n...\n\n## Your Decision Point\n[One question. Two options with trade-offs. No recommendation — just clarity.]\n```\n\n---\n\n## Decision Log\n\nTrack decisions using the canonical two-layer decision memory (see `..\u002Fagent-protocol\u002FSKILL.md` → \"Decision Memory (Canonical Layout)\"):\n\n- **Layer 1 (raw):** `~\u002F.claude\u002Fdecisions\u002Fraw\u002FYYYY-MM-DD-{slug}.md` — full deliberation transcript\n- **Layer 2 (approved):** `~\u002F.claude\u002Fdecisions\u002Fapproved\u002FYYYY-MM-DD-{slug}.md` — founder-approved decisions only\n\n```\n## Decision: [Name]\nDate: [YYYY-MM-DD]\nQuestion: [Original question]\nDecided: [What was decided]\nOwner: [Who executes]\nReview: [When to check back]\n```\n\nAt session start: scan `~\u002F.claude\u002Fdecisions\u002Fapproved\u002F` — if a review date has passed, flag it: *\"You decided [X] on [date]. Worth a check-in?\"*\n\nMigration: a legacy single-file log at `~\u002F.claude\u002Fdecision-log.md` may exist from earlier versions; read it for history but write new entries to `~\u002F.claude\u002Fdecisions\u002F`.\n\n---\n\n## Quality Standards\n\nBefore delivering ANY output to the founder:\n- [ ] Follows User Communication Standard (see `..\u002Fagent-protocol\u002FSKILL.md`)\n- [ ] Bottom line is first — no preamble, no process narration\n- [ ] Company context loaded (not generic advice)\n- [ ] Every finding has WHAT + WHY + HOW\n- [ ] Actions have owners and deadlines (no \"we should consider\")\n- [ ] Decisions framed as options with trade-offs and recommendation\n- [ ] Conflicts named, not smoothed\n- [ ] Risks are concrete (if X → Y happens, costs $Z)\n- [ ] No loops occurred\n- [ ] Max 5 bullets per section — overflow to reference\n\n---\n\n## Ecosystem Awareness\n\nThe Chief of Staff routes to **33 skills total**:\n- **15 C-suite roles** — CEO, CTO, COO, CPO, CMO, CFO, CRO, CISO, CHRO, General Counsel, CDO, CAIO, CCO, VPE, Executive Mentor\n- **6 orchestration skills** — cs-onboard, context-engine, board-meeting, decision-logger, agent-protocol, chief-of-staff\n- **6 cross-cutting skills** — board-deck-builder, scenario-war-room, competitive-intel, org-health-diagnostic, ma-playbook, intl-expansion\n- **6 culture & collaboration skills** — culture-architect, company-os, founder-coach, strategic-alignment, change-management, internal-narrative\n\nSee `references\u002Frouting-matrix.md` for complete trigger mapping.\n\n## References\n- `references\u002Frouting-matrix.md` — per-topic routing rules, complementary skill triggers, when to trigger board\n- `references\u002Fsynthesis-framework.md` — full synthesis process, conflict types, output format\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"domain":26,"updated":27,"version":28,"category":29,"frameworks":30},"Alireza Rezvani","orchestration",1772668800000,"1.0.0","c-level","routing-matrix, synthesis-framework, decision-log, board-protocol","main","46d43f3edecde97283ac410e9051444d90120cfb","repos\u002FJ.A.R.V.I.S\u002Fcomponents\u002Fcore\u002Fclaude-skills\u002F.codex\u002Fskills\u002Fchief-of-staff","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo","https:\u002F\u002Fgithub.com\u002Fazhri1990","2026-10-10 07:58:58",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add azhri1990\u002Fjarvis-mega-repo --skill chief-of-staff",{"tool":43,"command":44},"bunx","bunx skills add azhri1990\u002Fjarvis-mega-repo --skill chief-of-staff",{"tool":46,"command":47},"pnpm","pnpm dlx skills add azhri1990\u002Fjarvis-mega-repo --skill chief-of-staff","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002FJ.A.R.V.I.S\u002Fcomponents\u002Fcore\u002Fclaude-skills\u002F.codex\u002Fskills\u002Fchief-of-staff\u002FSKILL.md",true,[51,57],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Frouting-matrix.md","REFERENCE","参考文档",12024,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002FJ.A.R.V.I.S\u002Fcomponents\u002Fcore\u002Fclaude-skills\u002F.codex\u002Fskills\u002Fchief-of-staff\u002Freferences\u002Frouting-matrix.md",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fsynthesis-framework.md",7887,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002FJ.A.R.V.I.S\u002Fcomponents\u002Fcore\u002Fclaude-skills\u002F.codex\u002Fskills\u002Fchief-of-staff\u002Freferences\u002Fsynthesis-framework.md",[62,69,76,83,90,97],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7CYPF9V9EMA4ZXS1TTCMBFH","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\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7CYNRJDTQCRF5KGPMBMSB1S","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\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7CYNAVSE84QD7HAWZWTY2FS","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\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7CYN0CE8P5ZN7WV2X06HKPC","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\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7CYMHZ3QRJ9BKRB859KW8TQ","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\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M7CYM3D8YKV7R6DT4RNJSF0A","grants","NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance\u002FInnovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget\u002Fscope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Use when the user asks about research funding or makes any grant-related request (e.g., 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research'). NIH-only scope — non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002Fresearch\u002Fgrants\u002Fskills\u002Fgrants\u002FSKILL.md",[],[]]