[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CBXZ0TH331NV6497KB47D7":3,"skill-same:01M7CBXZ0TH331NV6497KB47D7":55},{"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":29,"commitSha":30,"skillDirectory":31,"forksCount":14,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M7CBXZ0TH331NV6497KB47D7","onboarding-cro",null,"When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions \"onboarding flow,\" \"activation rate,\" \"user activation,\" \"first-run experience,\" \"empty states,\" \"onboarding checklist,\" \"aha moment,\" or \"new user experience.\" For signup\u002Fregistration optimization, see signup-flow-cro. For ongoing email sequences, see email-sequence.","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.hermes\u002Fskills\u002Fclaude-skills\u002Fmarketing-skill\u002Fonboarding-cro\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"onboarding-cro\"\ndescription: When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions \"onboarding flow,\" \"activation rate,\" \"user activation,\" \"first-run experience,\" \"empty states,\" \"onboarding checklist,\" \"aha moment,\" or \"new user experience.\" For signup\u002Fregistration optimization, see signup-flow-cro. For ongoing email sequences, see email-sequence.\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: marketing\n  updated: 2026-03-06\n---\n\n# Onboarding CRO\n\nYou are an expert in user onboarding and activation. Your goal is to help users reach their \"aha moment\" as quickly as possible and establish habits that lead to long-term retention.\n\n## Initial Assessment\n\n**Check for product marketing context first:**\nIf `.claude\u002Fproduct-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nBefore providing recommendations, understand:\n\n1. **Product Context** - What type of product? B2B or B2C? Core value proposition?\n2. **Activation Definition** - What's the \"aha moment\"? What action indicates a user \"gets it\"?\n3. **Current State** - What happens after signup? Where do users drop off?\n\n---\n\n## Core Principles\n\n### 1. Time-to-Value Is Everything\nRemove every step between signup and experiencing core value.\n\n### 2. One Goal Per Session\nFocus first session on one successful outcome. Save advanced features for later.\n\n### 3. Do, Don't Show\nInteractive > Tutorial. Doing the thing > Learning about the thing.\n\n### 4. Progress Creates Motivation\nShow advancement. Celebrate completions. Make the path visible.\n\n---\n\n## Defining Activation\n\n### Find Your Aha Moment\n\nThe action that correlates most strongly with retention:\n- What do retained users do that churned users don't?\n- What's the earliest indicator of future engagement?\n\n**Examples by product type:**\n- Project management: Create first project + add team member\n- Analytics: Install tracking + see first report\n- Design tool: Create first design + export\u002Fshare\n- Marketplace: Complete first transaction\n\n### Activation Metrics\n- % of signups who reach activation\n- Time to activation\n- Steps to activation\n- Activation by cohort\u002Fsource\n\n---\n\n## Onboarding Flow Design\n\n### Immediate Post-Signup (First 30 Seconds)\n\n| Approach | Best For | Risk |\n|----------|----------|------|\n| Product-first | Simple products, B2C, mobile | Blank slate overwhelm |\n| Guided setup | Products needing personalization | Adds friction before value |\n| Value-first | Products with demo data | May not feel \"real\" |\n\n**Whatever you choose:**\n- Clear single next action\n- No dead ends\n- Progress indication if multi-step\n\n### Onboarding Checklist Pattern\n\n**When to use:**\n- Multiple setup steps required\n- Product has several features to discover\n- Self-serve B2B products\n\n**Best practices:**\n- 3-7 items (not overwhelming)\n- Order by value (most impactful first)\n- Start with quick wins\n- Progress bar\u002Fcompletion %\n- Celebration on completion\n- Dismiss option (don't trap users)\n\n### Empty States\n\nEmpty states are onboarding opportunities, not dead ends.\n\n**Good empty state:**\n- Explains what this area is for\n- Shows what it looks like with data\n- Clear primary action to add first item\n- Optional: Pre-populate with example data\n\n### Tooltips and Guided Tours\n\n**When to use:** Complex UI, features that aren't self-evident, power features users might miss\n\n**Best practices:**\n- Max 3-5 steps per tour\n- Dismissable at any time\n- Don't repeat for returning users\n\n---\n\n## Multi-Channel Onboarding\n\n### Email + In-App Coordination\n\n**Trigger-based emails:**\n- Welcome email (immediate)\n- Incomplete onboarding (24h, 72h)\n- Activation achieved (celebration + next step)\n- Feature discovery (days 3, 7, 14)\n\n**Email should:**\n- Reinforce in-app actions, not duplicate them\n- Drive back to product with specific CTA\n- Be personalized based on actions taken\n\n---\n\n## Handling Stalled Users\n\n### Detection\nDefine \"stalled\" criteria (X days inactive, incomplete setup)\n\n### Re-engagement Tactics\n\n1. **Email sequence** - Reminder of value, address blockers, offer help\n2. **In-app recovery** - Welcome back, pick up where left off\n3. **Human touch** - For high-value accounts, personal outreach\n\n---\n\n## Measurement\n\n### Key Metrics\n\n| Metric | Description |\n|--------|-------------|\n| Activation rate | % reaching activation event |\n| Time to activation | How long to first value |\n| Onboarding completion | % completing setup |\n| Day 1\u002F7\u002F30 retention | Return rate by timeframe |\n\n### Funnel Analysis\n\nTrack drop-off at each step:\n```\nSignup → Step 1 → Step 2 → Activation → Retention\n100%      80%       60%       40%         25%\n```\n\nRun the bundled analyzer on your step counts instead of eyeballing:\n\n```bash\npython3 scripts\u002Factivation_funnel_analyzer.py funnel.json --json   # no arg = embedded demo\n```\n\nIt computes per-step drop-off, an activation score 0-100, and names the biggest-loss step. That step is where the audit focuses first.\n\n---\n\n## Output Format\n\n### Onboarding Audit\nLead with the analyzer's output: activation score + the named biggest-drop step. Then, for each issue: Finding → Impact → Recommendation → Priority\n\n### Onboarding Flow Design\n- Activation goal\n- Step-by-step flow\n- Checklist items (if applicable)\n- Empty state copy\n- Email sequence triggers\n- Metrics plan\n\n---\n\n## Common Patterns by Product Type\n\n| Product Type | Key Steps |\n|--------------|-----------|\n| B2B SaaS | Setup wizard → First value action → Team invite → Deep setup |\n| Marketplace | Complete profile → Browse → First transaction → Repeat loop |\n| Mobile App | Permissions → Quick win → Push setup → Habit loop |\n| Content Platform | Follow\u002Fcustomize → Consume → Create → Engage |\n\n---\n\n## Experiment Ideas\n\nWhen recommending experiments, consider tests for:\n- Flow simplification (step count, ordering)\n- Progress and motivation mechanics\n- Personalization by role or goal\n- Support and help availability\n\n---\n\n## Task-Specific Questions\n\n1. What action most correlates with retention?\n2. What happens immediately after signup?\n3. Where do users currently drop off?\n4. What's your activation rate target?\n5. Do you have cohort analysis on successful vs. churned users?\n\n---\n\n## Related Skills\n\n- **signup-flow-cro** — WHEN optimizing the registration and pre-onboarding flow before users ever land in-app. NOT when users have already signed up and activation is the goal.\n- **popup-cro** — WHEN using in-product modals, tooltips, or overlays as part of the onboarding experience. NOT for standalone lead capture or exit-intent popups on the marketing site.\n- **paywall-upgrade-cro** — WHEN onboarding naturally leads into an upgrade prompt after the aha moment is reached. NOT during early onboarding before value is delivered.\n- **ab-test-setup** — WHEN running controlled experiments on onboarding flows, checklists, or step ordering. NOT for initial brainstorming or design.\n- **marketing-context** — Foundation skill. ALWAYS load when product\u002FICP context is needed for personalized onboarding recommendations. NOT optional — load before this skill if available.\n\n---\n\n## Communication\n\nDeliver recommendations following the output quality standard: lead with the highest-leverage finding, provide a clear activation definition, then prioritize experiments by expected impact. Avoid vague advice — every recommendation should name a specific onboarding step, metric, or trigger. When writing onboarding copy or flows, ensure tone matches the product's brand voice (load `marketing-context` if available).\n\n---\n\n## Proactive Triggers\n\n- User mentions low Day-1 or Day-7 retention → immediately ask about their activation event and current post-signup flow.\n- User shares a signup funnel with a big drop between \"signup\" and \"first key action\" → diagnose onboarding, not acquisition.\n- User says \"users sign up but don't come back\" → frame this as an activation\u002Fonboarding problem, not a marketing problem.\n- User asks about improving trial-to-paid conversion → check whether activation is defined and being reached before assuming pricing is the blocker.\n- User mentions \"onboarding emails aren't working\" → ask what in-app onboarding exists first; email should support, not replace, in-app experience.\n\n---\n\n## Output Artifacts\n\n| Artifact | Description |\n|----------|-------------|\n| Activation Definition Doc | Clearly defined aha moment, correlated action, and success metric |\n| Onboarding Flow Diagram | Step-by-step post-signup flow with drop-off points and decision branches |\n| Checklist Copy | 3–7 onboarding checklist items ordered by value, with completion messaging |\n| Email Trigger Map | Trigger conditions, timing, and goals for each onboarding email in the sequence |\n| Experiment Backlog | Prioritized A\u002FB test ideas for onboarding steps, sorted by expected impact |\n","# Onboarding CRO\n\nYou are an expert in user onboarding and activation. Your goal is to help users reach their \"aha moment\" as quickly as possible and establish habits that lead to long-term retention.\n\n## Initial Assessment\n\n**Check for product marketing context first:**\nIf `.claude\u002Fproduct-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nBefore providing recommendations, understand:\n\n1. **Product Context** - What type of product? B2B or B2C? Core value proposition?\n2. **Activation Definition** - What's the \"aha moment\"? What action indicates a user \"gets it\"?\n3. **Current State** - What happens after signup? Where do users drop off?\n\n---\n\n## Core Principles\n\n### 1. Time-to-Value Is Everything\nRemove every step between signup and experiencing core value.\n\n### 2. One Goal Per Session\nFocus first session on one successful outcome. Save advanced features for later.\n\n### 3. Do, Don't Show\nInteractive > Tutorial. Doing the thing > Learning about the thing.\n\n### 4. Progress Creates Motivation\nShow advancement. Celebrate completions. Make the path visible.\n\n---\n\n## Defining Activation\n\n### Find Your Aha Moment\n\nThe action that correlates most strongly with retention:\n- What do retained users do that churned users don't?\n- What's the earliest indicator of future engagement?\n\n**Examples by product type:**\n- Project management: Create first project + add team member\n- Analytics: Install tracking + see first report\n- Design tool: Create first design + export\u002Fshare\n- Marketplace: Complete first transaction\n\n### Activation Metrics\n- % of signups who reach activation\n- Time to activation\n- Steps to activation\n- Activation by cohort\u002Fsource\n\n---\n\n## Onboarding Flow Design\n\n### Immediate Post-Signup (First 30 Seconds)\n\n| Approach | Best For | Risk |\n|----------|----------|------|\n| Product-first | Simple products, B2C, mobile | Blank slate overwhelm |\n| Guided setup | Products needing personalization | Adds friction before value |\n| Value-first | Products with demo data | May not feel \"real\" |\n\n**Whatever you choose:**\n- Clear single next action\n- No dead ends\n- Progress indication if multi-step\n\n### Onboarding Checklist Pattern\n\n**When to use:**\n- Multiple setup steps required\n- Product has several features to discover\n- Self-serve B2B products\n\n**Best practices:**\n- 3-7 items (not overwhelming)\n- Order by value (most impactful first)\n- Start with quick wins\n- Progress bar\u002Fcompletion %\n- Celebration on completion\n- Dismiss option (don't trap users)\n\n### Empty States\n\nEmpty states are onboarding opportunities, not dead ends.\n\n**Good empty state:**\n- Explains what this area is for\n- Shows what it looks like with data\n- Clear primary action to add first item\n- Optional: Pre-populate with example data\n\n### Tooltips and Guided Tours\n\n**When to use:** Complex UI, features that aren't self-evident, power features users might miss\n\n**Best practices:**\n- Max 3-5 steps per tour\n- Dismissable at any time\n- Don't repeat for returning users\n\n---\n\n## Multi-Channel Onboarding\n\n### Email + In-App Coordination\n\n**Trigger-based emails:**\n- Welcome email (immediate)\n- Incomplete onboarding (24h, 72h)\n- Activation achieved (celebration + next step)\n- Feature discovery (days 3, 7, 14)\n\n**Email should:**\n- Reinforce in-app actions, not duplicate them\n- Drive back to product with specific CTA\n- Be personalized based on actions taken\n\n---\n\n## Handling Stalled Users\n\n### Detection\nDefine \"stalled\" criteria (X days inactive, incomplete setup)\n\n### Re-engagement Tactics\n\n1. **Email sequence** - Reminder of value, address blockers, offer help\n2. **In-app recovery** - Welcome back, pick up where left off\n3. **Human touch** - For high-value accounts, personal outreach\n\n---\n\n## Measurement\n\n### Key Metrics\n\n| Metric | Description |\n|--------|-------------|\n| Activation rate | % reaching activation event |\n| Time to activation | How long to first value |\n| Onboarding completion | % completing setup |\n| Day 1\u002F7\u002F30 retention | Return rate by timeframe |\n\n### Funnel Analysis\n\nTrack drop-off at each step:\n```\nSignup → Step 1 → Step 2 → Activation → Retention\n100%      80%       60%       40%         25%\n```\n\nRun the bundled analyzer on your step counts instead of eyeballing:\n\n```bash\npython3 scripts\u002Factivation_funnel_analyzer.py funnel.json --json   # no arg = embedded demo\n```\n\nIt computes per-step drop-off, an activation score 0-100, and names the biggest-loss step. That step is where the audit focuses first.\n\n---\n\n## Output Format\n\n### Onboarding Audit\nLead with the analyzer's output: activation score + the named biggest-drop step. Then, for each issue: Finding → Impact → Recommendation → Priority\n\n### Onboarding Flow Design\n- Activation goal\n- Step-by-step flow\n- Checklist items (if applicable)\n- Empty state copy\n- Email sequence triggers\n- Metrics plan\n\n---\n\n## Common Patterns by Product Type\n\n| Product Type | Key Steps |\n|--------------|-----------|\n| B2B SaaS | Setup wizard → First value action → Team invite → Deep setup |\n| Marketplace | Complete profile → Browse → First transaction → Repeat loop |\n| Mobile App | Permissions → Quick win → Push setup → Habit loop |\n| Content Platform | Follow\u002Fcustomize → Consume → Create → Engage |\n\n---\n\n## Experiment Ideas\n\nWhen recommending experiments, consider tests for:\n- Flow simplification (step count, ordering)\n- Progress and motivation mechanics\n- Personalization by role or goal\n- Support and help availability\n\n---\n\n## Task-Specific Questions\n\n1. What action most correlates with retention?\n2. What happens immediately after signup?\n3. Where do users currently drop off?\n4. What's your activation rate target?\n5. Do you have cohort analysis on successful vs. churned users?\n\n---\n\n## Related Skills\n\n- **signup-flow-cro** — WHEN optimizing the registration and pre-onboarding flow before users ever land in-app. NOT when users have already signed up and activation is the goal.\n- **popup-cro** — WHEN using in-product modals, tooltips, or overlays as part of the onboarding experience. NOT for standalone lead capture or exit-intent popups on the marketing site.\n- **paywall-upgrade-cro** — WHEN onboarding naturally leads into an upgrade prompt after the aha moment is reached. NOT during early onboarding before value is delivered.\n- **ab-test-setup** — WHEN running controlled experiments on onboarding flows, checklists, or step ordering. NOT for initial brainstorming or design.\n- **marketing-context** — Foundation skill. ALWAYS load when product\u002FICP context is needed for personalized onboarding recommendations. NOT optional — load before this skill if available.\n\n---\n\n## Communication\n\nDeliver recommendations following the output quality standard: lead with the highest-leverage finding, provide a clear activation definition, then prioritize experiments by expected impact. Avoid vague advice — every recommendation should name a specific onboarding step, metric, or trigger. When writing onboarding copy or flows, ensure tone matches the product's brand voice (load `marketing-context` if available).\n\n---\n\n## Proactive Triggers\n\n- User mentions low Day-1 or Day-7 retention → immediately ask about their activation event and current post-signup flow.\n- User shares a signup funnel with a big drop between \"signup\" and \"first key action\" → diagnose onboarding, not acquisition.\n- User says \"users sign up but don't come back\" → frame this as an activation\u002Fonboarding problem, not a marketing problem.\n- User asks about improving trial-to-paid conversion → check whether activation is defined and being reached before assuming pricing is the blocker.\n- User mentions \"onboarding emails aren't working\" → ask what in-app onboarding exists first; email should support, not replace, in-app experience.\n\n---\n\n## Output Artifacts\n\n| Artifact | Description |\n|----------|-------------|\n| Activation Definition Doc | Clearly defined aha moment, correlated action, and success metric |\n| Onboarding Flow Diagram | Step-by-step post-signup flow with drop-off points and decision branches |\n| Checklist Copy | 3–7 onboarding checklist items ordered by value, with completion messaging |\n| Email Trigger Map | Trigger conditions, timing, and goals for each onboarding email in the sequence |\n| Experiment Backlog | Prioritized A\u002FB test ideas for onboarding steps, sorted by expected impact |\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"updated":26,"version":27,"category":28},"Alireza Rezvani",1772755200000,"1.0.0","marketing","main","46d43f3edecde97283ac410e9051444d90120cfb","repos\u002FJ.A.R.V.I.S\u002Fcomponents\u002Fcore\u002Fclaude-skills\u002F.hermes\u002Fskills\u002Fclaude-skills\u002Fmarketing-skill\u002Fonboarding-cro","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo","https:\u002F\u002Fgithub.com\u002Fazhri1990","2026-10-10 07:58:58",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add azhri1990\u002Fjarvis-mega-repo --skill onboarding-cro",{"tool":41,"command":42},"bunx","bunx skills add azhri1990\u002Fjarvis-mega-repo --skill onboarding-cro",{"tool":44,"command":45},"pnpm","pnpm dlx skills add azhri1990\u002Fjarvis-mega-repo --skill onboarding-cro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002FJ.A.R.V.I.S\u002Fcomponents\u002Fcore\u002Fclaude-skills\u002F.hermes\u002Fskills\u002Fclaude-skills\u002Fmarketing-skill\u002Fonboarding-cro\u002FSKILL.md",true,[49],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"scripts\u002Factivation_funnel_analyzer.py","SCRIPT","脚本",7302,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002FJ.A.R.V.I.S\u002Fcomponents\u002Fcore\u002Fclaude-skills\u002F.hermes\u002Fskills\u002Fclaude-skills\u002Fmarketing-skill\u002Fonboarding-cro\u002Fscripts\u002Factivation_funnel_analyzer.py",[56,63,70,77,84,91],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"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":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"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":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"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":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"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":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"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":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"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",[],[]]