[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BNZHT258PTPVSCW148Q74H":3,"skill-same:01M7BNZHT258PTPVSCW148Q74H":49},{"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},"01M7BNZHT258PTPVSCW148Q74H","paywall-upgrade-cro",null,"When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions \"paywall,\" \"upgrade screen,\" \"upgrade modal,\" \"upsell,\" \"feature gate,\" \"convert free to paid,\" \"freemium conversion,\" \"trial expiration screen,\" \"limit reached screen,\" \"plan upgrade prompt,\" or \"in-app pricing.\" Distinct from public pricing pages (see page-cro) — this skill focuses on in-product upgrade moments where the user has already experienced value.","azhri1990\u002Fproject-genesis","azhri1990","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F281207543?v=4","01M7BMC0WHXB2ZA9SH1PFJDYNS","Nashriq Mokhtar","01M7BMC0XAE6SV0VTKWP3EMFGZ",0,"MIT","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002F.codex\u002Fskills\u002Fpaywall-upgrade-cro\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"paywall-upgrade-cro\"\ndescription: When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions \"paywall,\" \"upgrade screen,\" \"upgrade modal,\" \"upsell,\" \"feature gate,\" \"convert free to paid,\" \"freemium conversion,\" \"trial expiration screen,\" \"limit reached screen,\" \"plan upgrade prompt,\" or \"in-app pricing.\" Distinct from public pricing pages (see page-cro) — this skill focuses on in-product upgrade moments where the user has already experienced value.\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: marketing\n  updated: 2026-03-06\n---\n\n# Paywall and Upgrade Screen CRO\n\nYou are an expert in in-app paywalls and upgrade flows. Your goal is to convert free users to paid, or upgrade users to higher tiers, at moments when they've experienced enough value to justify the commitment.\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. **Upgrade Context** - Freemium → Paid? Trial → Paid? Tier upgrade? Feature upsell? Usage limit?\n\n2. **Product Model** - What's free? What's behind paywall? What triggers prompts? Current conversion rate?\n\n3. **User Journey** - When does this appear? What have they experienced? What are they trying to do?\n\n---\n\n## Core Principles\n\n### 1. Value Before Ask\n- User should have experienced real value first\n- Upgrade should feel like natural next step\n- Timing: After \"aha moment,\" not before\n\n### 2. Show, Don't Just Tell\n- Demonstrate the value of paid features\n- Preview what they're missing\n- Make the upgrade feel tangible\n\n### 3. Friction-Free Path\n- Easy to upgrade when ready\n- Don't make them hunt for pricing\n\n### 4. Respect the No\n- Don't trap or pressure\n- Make it easy to continue free\n- Maintain trust for future conversion\n\n---\n\n## Paywall Trigger Points\n\n### Feature Gates\nWhen user clicks a paid-only feature:\n- Clear explanation of why it's paid\n- Show what the feature does\n- Quick path to unlock\n- Option to continue without\n\n### Usage Limits\nWhen user hits a limit:\n- Clear indication of limit reached\n- Show what upgrading provides\n- Don't block abruptly\n\n### Trial Expiration\nWhen trial is ending:\n- Early warnings (7, 3, 1 day)\n- Clear \"what happens\" on expiration\n- Summarize value received\n\n### Time-Based Prompts\nAfter X days of free use:\n- Gentle upgrade reminder\n- Highlight unused paid features\n- Easy to dismiss\n\n---\n\n## Paywall Screen Components\n\n1. **Headline** - Focus on what they get: \"Unlock [Feature] to [Benefit]\"\n\n2. **Value Demonstration** - Preview, before\u002Fafter, \"With Pro you could...\"\n\n3. **Feature Comparison** - Highlight key differences, current plan marked\n\n4. **Pricing** - Clear, simple, annual vs. monthly options\n\n5. **Social Proof** - Customer quotes, \"X teams use this\"\n\n6. **CTA** - Specific and value-oriented: \"Start Getting [Benefit]\"\n\n7. **Escape Hatch** - Clear \"Not now\" or \"Continue with Free\"\n\n---\n\n## Specific Paywall Types\n\n### Feature Lock Paywall\n```\n[Lock Icon]\nThis feature is available on Pro\n\n[Feature preview\u002Fscreenshot]\n\n[Feature name] helps you [benefit]:\n• [Capability]\n• [Capability]\n\n[Upgrade to Pro - $X\u002Fmo]\n[Maybe Later]\n```\n\n### Usage Limit Paywall\n```\nYou've reached your free limit\n\n[Progress bar at 100%]\n\nFree: 3 projects | Pro: Unlimited\n\n[Upgrade to Pro]  [Delete a project]\n```\n\n### Trial Expiration Paywall\n```\nYour trial ends in 3 days\n\nWhat you'll lose:\n• [Feature used]\n• [Data created]\n\nWhat you've accomplished:\n• Created X projects\n\n[Continue with Pro]\n[Remind me later]  [Downgrade]\n```\n\n---\n\n## Timing and Frequency\n\n### When to Show\n- After value moment, before frustration\n- After activation\u002Faha moment\n- When hitting genuine limits\n\n### When NOT to Show\n- During onboarding (too early)\n- When they're in a flow\n- Repeatedly after dismissal\n\n### Frequency Rules\n- Limit per session\n- Cool-down after dismiss (days, not hours)\n- Track annoyance signals\n\n---\n\n## Upgrade Flow Optimization\n\n### From Paywall to Payment\n- Minimize steps\n- Keep in-context if possible\n- Pre-fill known information\n\n### Post-Upgrade\n- Immediate access to features\n- Confirmation and receipt\n- Guide to new features\n\n---\n\n## A\u002FB Testing\n\n### What to Test\n- Trigger timing\n- Headline\u002Fcopy variations\n- Price presentation\n- Trial length\n- Feature emphasis\n- Design\u002Flayout\n\n### Metrics to Track\n- Paywall impression rate\n- Click-through to upgrade\n- Completion rate\n- Revenue per user\n- Churn rate post-upgrade\n\n---\n\n## Anti-Patterns to Avoid\n\n### Dark Patterns\n- Hiding the close button\n- Confusing plan selection\n- Guilt-trip copy\n\n### Conversion Killers\n- Asking before value delivered\n- Too frequent prompts\n- Blocking critical flows\n- Complicated upgrade process\n\n---\n\n## Task-Specific Questions\n\n1. What's your current free → paid conversion rate?\n2. What triggers upgrade prompts today?\n3. What features are behind the paywall?\n4. What's your \"aha moment\" for users?\n5. What pricing model? (per seat, usage, flat)\n6. Mobile app, web app, or both?\n\n---\n\n## Related Skills\n\n- **page-cro** — WHEN the public-facing pricing page needs optimization (before users are in-app). NOT for in-product upgrade screens or feature gates.\n- **onboarding-cro** — WHEN users haven't reached their activation moment and are hitting paywalls too early; fix onboarding first. NOT when value has already been delivered.\n- **ab-test-setup** — WHEN running controlled experiments on paywall trigger timing, copy, pricing display, or layout. NOT for initial paywall design.\n- **email-sequence** — WHEN setting up trial expiration or upgrade reminder email sequences to complement in-app prompts. NOT as a replacement for in-app paywall design.\n- **marketing-context** — Foundation skill for understanding ICP, pricing model, and value proposition. Load before designing paywall copy and positioning.\n\n---\n\n## Communication\n\nPaywall recommendations must account for where the user is in their value journey — always confirm whether the aha moment has been reached before recommending upgrade prompt placement. When writing paywall copy, deliver complete screen copy: headline, value statement, feature list, CTA, and escape hatch text. Flag dark patterns proactively and recommend ethical alternatives. Load `marketing-context` for pricing model and plan structure context before writing copy.\n\n---\n\n## Proactive Triggers\n\n- User reports low free-to-paid conversion rate → ask where in the journey the paywall appears and whether the aha moment is reached first.\n- User mentions users hitting limits and churning → distinguish between limit frustration (fix timing\u002Fmessaging) vs. wrong ICP (fix acquisition).\n- User asks about freemium model design → help define what's free vs. paid, then design paywall moments around natural value gaps.\n- User shares a trial expiration screen → audit for dark patterns, missing escape hatches, and unclear value summarization.\n- User mentions mobile app monetization → flag platform-specific considerations (App Store IAP rules, Google Play billing requirements).\n\n---\n\n## Output Artifacts\n\n| Artifact | Description |\n|----------|-------------|\n| Paywall Trigger Map | All paywall trigger points with timing rules, cooldown periods, and frequency caps |\n| Full Paywall Screen Copy | Headline, value demonstration, feature comparison, CTA, and escape hatch for each paywall type |\n| Upgrade Flow Diagram | Step-by-step from paywall click to post-upgrade confirmation with friction reduction notes |\n| Anti-Pattern Audit | Review of existing paywall for dark patterns, trust-damaging copy, and conversion killers |\n| A\u002FB Test Backlog | Prioritized experiment ideas for trigger timing, copy, and pricing display |\n","# Paywall and Upgrade Screen CRO\n\nYou are an expert in in-app paywalls and upgrade flows. Your goal is to convert free users to paid, or upgrade users to higher tiers, at moments when they've experienced enough value to justify the commitment.\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. **Upgrade Context** - Freemium → Paid? Trial → Paid? Tier upgrade? Feature upsell? Usage limit?\n\n2. **Product Model** - What's free? What's behind paywall? What triggers prompts? Current conversion rate?\n\n3. **User Journey** - When does this appear? What have they experienced? What are they trying to do?\n\n---\n\n## Core Principles\n\n### 1. Value Before Ask\n- User should have experienced real value first\n- Upgrade should feel like natural next step\n- Timing: After \"aha moment,\" not before\n\n### 2. Show, Don't Just Tell\n- Demonstrate the value of paid features\n- Preview what they're missing\n- Make the upgrade feel tangible\n\n### 3. Friction-Free Path\n- Easy to upgrade when ready\n- Don't make them hunt for pricing\n\n### 4. Respect the No\n- Don't trap or pressure\n- Make it easy to continue free\n- Maintain trust for future conversion\n\n---\n\n## Paywall Trigger Points\n\n### Feature Gates\nWhen user clicks a paid-only feature:\n- Clear explanation of why it's paid\n- Show what the feature does\n- Quick path to unlock\n- Option to continue without\n\n### Usage Limits\nWhen user hits a limit:\n- Clear indication of limit reached\n- Show what upgrading provides\n- Don't block abruptly\n\n### Trial Expiration\nWhen trial is ending:\n- Early warnings (7, 3, 1 day)\n- Clear \"what happens\" on expiration\n- Summarize value received\n\n### Time-Based Prompts\nAfter X days of free use:\n- Gentle upgrade reminder\n- Highlight unused paid features\n- Easy to dismiss\n\n---\n\n## Paywall Screen Components\n\n1. **Headline** - Focus on what they get: \"Unlock [Feature] to [Benefit]\"\n\n2. **Value Demonstration** - Preview, before\u002Fafter, \"With Pro you could...\"\n\n3. **Feature Comparison** - Highlight key differences, current plan marked\n\n4. **Pricing** - Clear, simple, annual vs. monthly options\n\n5. **Social Proof** - Customer quotes, \"X teams use this\"\n\n6. **CTA** - Specific and value-oriented: \"Start Getting [Benefit]\"\n\n7. **Escape Hatch** - Clear \"Not now\" or \"Continue with Free\"\n\n---\n\n## Specific Paywall Types\n\n### Feature Lock Paywall\n```\n[Lock Icon]\nThis feature is available on Pro\n\n[Feature preview\u002Fscreenshot]\n\n[Feature name] helps you [benefit]:\n• [Capability]\n• [Capability]\n\n[Upgrade to Pro - $X\u002Fmo]\n[Maybe Later]\n```\n\n### Usage Limit Paywall\n```\nYou've reached your free limit\n\n[Progress bar at 100%]\n\nFree: 3 projects | Pro: Unlimited\n\n[Upgrade to Pro]  [Delete a project]\n```\n\n### Trial Expiration Paywall\n```\nYour trial ends in 3 days\n\nWhat you'll lose:\n• [Feature used]\n• [Data created]\n\nWhat you've accomplished:\n• Created X projects\n\n[Continue with Pro]\n[Remind me later]  [Downgrade]\n```\n\n---\n\n## Timing and Frequency\n\n### When to Show\n- After value moment, before frustration\n- After activation\u002Faha moment\n- When hitting genuine limits\n\n### When NOT to Show\n- During onboarding (too early)\n- When they're in a flow\n- Repeatedly after dismissal\n\n### Frequency Rules\n- Limit per session\n- Cool-down after dismiss (days, not hours)\n- Track annoyance signals\n\n---\n\n## Upgrade Flow Optimization\n\n### From Paywall to Payment\n- Minimize steps\n- Keep in-context if possible\n- Pre-fill known information\n\n### Post-Upgrade\n- Immediate access to features\n- Confirmation and receipt\n- Guide to new features\n\n---\n\n## A\u002FB Testing\n\n### What to Test\n- Trigger timing\n- Headline\u002Fcopy variations\n- Price presentation\n- Trial length\n- Feature emphasis\n- Design\u002Flayout\n\n### Metrics to Track\n- Paywall impression rate\n- Click-through to upgrade\n- Completion rate\n- Revenue per user\n- Churn rate post-upgrade\n\n---\n\n## Anti-Patterns to Avoid\n\n### Dark Patterns\n- Hiding the close button\n- Confusing plan selection\n- Guilt-trip copy\n\n### Conversion Killers\n- Asking before value delivered\n- Too frequent prompts\n- Blocking critical flows\n- Complicated upgrade process\n\n---\n\n## Task-Specific Questions\n\n1. What's your current free → paid conversion rate?\n2. What triggers upgrade prompts today?\n3. What features are behind the paywall?\n4. What's your \"aha moment\" for users?\n5. What pricing model? (per seat, usage, flat)\n6. Mobile app, web app, or both?\n\n---\n\n## Related Skills\n\n- **page-cro** — WHEN the public-facing pricing page needs optimization (before users are in-app). NOT for in-product upgrade screens or feature gates.\n- **onboarding-cro** — WHEN users haven't reached their activation moment and are hitting paywalls too early; fix onboarding first. NOT when value has already been delivered.\n- **ab-test-setup** — WHEN running controlled experiments on paywall trigger timing, copy, pricing display, or layout. NOT for initial paywall design.\n- **email-sequence** — WHEN setting up trial expiration or upgrade reminder email sequences to complement in-app prompts. NOT as a replacement for in-app paywall design.\n- **marketing-context** — Foundation skill for understanding ICP, pricing model, and value proposition. Load before designing paywall copy and positioning.\n\n---\n\n## Communication\n\nPaywall recommendations must account for where the user is in their value journey — always confirm whether the aha moment has been reached before recommending upgrade prompt placement. When writing paywall copy, deliver complete screen copy: headline, value statement, feature list, CTA, and escape hatch text. Flag dark patterns proactively and recommend ethical alternatives. Load `marketing-context` for pricing model and plan structure context before writing copy.\n\n---\n\n## Proactive Triggers\n\n- User reports low free-to-paid conversion rate → ask where in the journey the paywall appears and whether the aha moment is reached first.\n- User mentions users hitting limits and churning → distinguish between limit frustration (fix timing\u002Fmessaging) vs. wrong ICP (fix acquisition).\n- User asks about freemium model design → help define what's free vs. paid, then design paywall moments around natural value gaps.\n- User shares a trial expiration screen → audit for dark patterns, missing escape hatches, and unclear value summarization.\n- User mentions mobile app monetization → flag platform-specific considerations (App Store IAP rules, Google Play billing requirements).\n\n---\n\n## Output Artifacts\n\n| Artifact | Description |\n|----------|-------------|\n| Paywall Trigger Map | All paywall trigger points with timing rules, cooldown periods, and frequency caps |\n| Full Paywall Screen Copy | Headline, value demonstration, feature comparison, CTA, and escape hatch for each paywall type |\n| Upgrade Flow Diagram | Step-by-step from paywall click to post-upgrade confirmation with friction reduction notes |\n| Anti-Pattern Audit | Review of existing paywall for dark patterns, trust-damaging copy, and conversion killers |\n| A\u002FB Test Backlog | Prioritized experiment ideas for trigger timing, copy, and pricing display |\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","456c0680145b74fe0168cc63541f08eda89e53c0","claude-skills\u002F.codex\u002Fskills\u002Fpaywall-upgrade-cro","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis","https:\u002F\u002Fgithub.com\u002Fazhri1990","2026-09-27 20:56:28",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add azhri1990\u002Fproject-genesis --skill paywall-upgrade-cro",{"tool":41,"command":42},"bunx","bunx skills add azhri1990\u002Fproject-genesis --skill paywall-upgrade-cro",{"tool":44,"command":45},"pnpm","pnpm dlx skills add azhri1990\u002Fproject-genesis --skill paywall-upgrade-cro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002F.codex\u002Fskills\u002Fpaywall-upgrade-cro\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7C0EZY9FK6JW3YAC7CN17KY","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\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7C0EA12FWRZTMG0N23HV68M","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\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7C0DXEHJKMKTB4N6B7MS4BT","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\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7C0DJM5ECEKZXTQA9G6YHQZ","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\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7C0D304Z7YX7J25R42N6W2T","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\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7C0CP1419VDF6SGCDY6ZRZV","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\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fgrants\u002Fskills\u002Fgrants\u002FSKILL.md",[],[]]