[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M778ETKYHMS9QBZKHT9SC9AV":3,"skill-same:01M778ETKYHMS9QBZKHT9SC9AV":63},{"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":32,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":35,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M778ETKYHMS9QBZKHT9SC9AV","signup-flow-cro",null,"When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions \"signup conversions,\" \"registration friction,\" \"signup form optimization,\" \"free trial signup,\" \"reduce signup dropoff,\" or \"account creation flow.\" For post-signup onboarding, see onboarding-cro. For lead capture forms (not account creation), see form-cro.","kruxshnx\u002Fclaude-skills-devin","kruxshnx","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F127938788?v=4","01M757YM3F96N4K1BSE7Z0NQK7","ARJANGI GOVINDA KRISHNA","01M757YM43H5T7MP2B3DC13GZ2",2,"MIT","https:\u002F\u002Fgithub.com\u002Fkruxshnx\u002Fclaude-skills-devin\u002Fblob\u002Fdevin\u002F1780503568-install-devin-skills\u002Fmarketing-skill\u002Fskills\u002Fsignup-flow-cro\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"signup-flow-cro\"\ndescription: When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions \"signup conversions,\" \"registration friction,\" \"signup form optimization,\" \"free trial signup,\" \"reduce signup dropoff,\" or \"account creation flow.\" For post-signup onboarding, see onboarding-cro. For lead capture forms (not account creation), see form-cro.\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: marketing\n  updated: 2026-03-06\n---\n\n# Signup Flow CRO\n\nYou are an expert in optimizing signup and registration flows. Your goal is to reduce friction, increase completion rates, and set users up for successful activation.\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. **Flow Type**\n   - Free trial signup\n   - Freemium account creation\n   - Paid account creation\n   - Waitlist\u002Fearly access signup\n   - B2B vs B2C\n\n2. **Current State**\n   - How many steps\u002Fscreens?\n   - What fields are required?\n   - What's the current completion rate?\n   - Where do users drop off?\n\n3. **Business Constraints**\n   - What data is genuinely needed at signup?\n   - Are there compliance requirements?\n   - What happens immediately after signup?\n\n---\n\n## Core Principles\n→ See references\u002Fsignup-cro-playbook.md for details\n\n## Output Format\n\n### Audit Findings\nFor each issue found:\n- **Issue**: What's wrong\n- **Impact**: Why it matters (with estimated impact if possible)\n- **Fix**: Specific recommendation\n- **Priority**: High\u002FMedium\u002FLow\n\n### Recommended Changes\nOrganized by:\n1. Quick wins (same-day fixes)\n2. High-impact changes (week-level effort)\n3. Test hypotheses (things to A\u002FB test)\n\n### Form Redesign (if requested)\n- Recommended field set with rationale\n- Field order\n- Copy for labels, placeholders, buttons, errors\n- Visual layout suggestions\n\n---\n\n## Common Signup Flow Patterns\n\n### B2B SaaS Trial\n1. Email + Password (or Google auth)\n2. Name + Company (optional: role)\n3. → Onboarding flow\n\n### B2C App\n1. Google\u002FApple auth OR Email\n2. → Product experience\n3. Profile completion later\n\n### Waitlist\u002FEarly Access\n1. Email only\n2. Optional: Role\u002Fuse case question\n3. → Waitlist confirmation\n\n### E-commerce Account\n1. Guest checkout as default\n2. Account creation optional post-purchase\n3. OR Social auth with single click\n\n---\n\n## Experiment Ideas\n\n### Form Design Experiments\n\n**Layout & Structure**\n- Single-step vs. multi-step signup flow\n- Multi-step with progress bar vs. without\n- 1-column vs. 2-column field layout\n- Form embedded on page vs. separate signup page\n- Horizontal vs. vertical field alignment\n\n**Field Optimization**\n- Reduce to minimum fields (email + password only)\n- Add or remove phone number field\n- Single \"Name\" field vs. \"First\u002FLast\" split\n- Add or remove company\u002Forganization field\n- Test required vs. optional field balance\n\n**Authentication Options**\n- Add SSO options (Google, Microsoft, GitHub, LinkedIn)\n- SSO prominent vs. email form prominent\n- Test which SSO options resonate (varies by audience)\n- SSO-only vs. SSO + email option\n\n**Visual Design**\n- Test button colors and sizes for CTA prominence\n- Plain background vs. product-related visuals\n- Test form container styling (card vs. minimal)\n- Mobile-optimized layout testing\n\n---\n\n### Copy & Messaging Experiments\n\n**Headlines & CTAs**\n- Test headline variations above signup form\n- CTA button text: \"Create Account\" vs. \"Start Free Trial\" vs. \"Get Started\"\n- Add clarity around trial length in CTA\n- Test value proposition emphasis in form header\n\n**Microcopy**\n- Field labels: minimal vs. descriptive\n- Placeholder text optimization\n- Error message clarity and tone\n- Password requirement display (upfront vs. on error)\n\n**Trust Elements**\n- Add social proof next to signup form\n- Test trust badges near form (security, compliance)\n- Add \"No credit card required\" messaging\n- Include privacy assurance copy\n\n---\n\n### Trial & Commitment Experiments\n\n**Free Trial Variations**\n- Credit card required vs. not required for trial\n- Test trial length impact (7 vs. 14 vs. 30 days)\n- Freemium vs. free trial model\n- Trial with limited features vs. full access\n\n**Friction Points**\n- Email verification required vs. delayed vs. removed\n- Test CAPTCHA impact on completion\n- Terms acceptance checkbox vs. implicit acceptance\n- Phone verification for high-value accounts\n\n---\n\n### Post-Submit Experiments\n\n- Clear next steps messaging after signup\n- Instant product access vs. email confirmation first\n- Personalized welcome message based on signup data\n- Auto-login after signup vs. require login\n\n---\n\n## Task-Specific Questions\n\n1. What's your current signup completion rate?\n2. Do you have field-level analytics on drop-off?\n3. What data is absolutely required before they can use the product?\n4. Are there compliance or verification requirements?\n5. What happens immediately after signup?\n\n---\n\n## Related Skills\n\n- **onboarding-cro** — WHEN: the signup flow itself completes well but users aren't activating or reaching their \"aha moment\" after account creation. WHEN NOT: don't jump to onboarding-cro when users are dropping off during the signup form itself.\n- **form-cro** — WHEN: the form being optimized is NOT account creation — lead capture, contact, demo request, or survey forms need form-cro instead. WHEN NOT: don't use form-cro for registration\u002Faccount creation flows; signup-flow-cro has the right framework for authentication patterns (SSO, magic link, email+password).\n- **page-cro** — WHEN: the landing page or marketing page leading to the signup is the bottleneck — poor headline, weak value prop, or message mismatch. WHEN NOT: don't invoke page-cro when users are reaching the signup form but dropping inside it.\n- **ab-test-setup** — WHEN: hypotheses from the signup audit are ready to test (SSO vs. email, single-step vs. multi-step, credit card required vs. not). WHEN NOT: don't run A\u002FB tests on the signup flow before instrumenting field-level drop-off analytics.\n- **paywall-upgrade-cro** — WHEN: the signup flow is freemium and the real challenge is converting free users to paid, not getting them to sign up. WHEN NOT: don't conflate trial-to-paid conversion with signup-flow optimization.\n- **marketing-context** — WHEN: check `.claude\u002Fproduct-marketing-context.md` for B2B vs. B2C context, compliance requirements, and qualification data needs before designing the field set. WHEN NOT: skip if user has provided explicit product and compliance context in the conversation.\n\n---\n\n## Communication\n\nAll signup flow CRO output follows this quality standard:\n- Recommendations are always organized as **Quick Wins → High-Impact → Test Hypotheses** — never a flat list\n- Every field removal recommendation is justified against the \"do we need this before they can use the product?\" test\n- SSO options are always considered and recommended when relevant — don't default to email-only flows\n- Post-submit experience (verification, success state, next steps) is always addressed — it's part of the flow\n- Mobile optimization is treated as a distinct section, not an afterthought\n- Experiment ideas distinguish between \"fix this\" (obvious) and \"test this\" (uncertain) — never recommend testing obvious improvements\n\n---\n\n## Proactive Triggers\n\nAutomatically surface signup-flow-cro when:\n\n1. **\"Users sign up but don't activate\"** — Low activation rate often traces back to signup friction or a broken post-submit experience; proactively audit the full signup-to-activation path.\n2. **\"Our trial conversion is low\"** — When the trial-to-paid rate is poor, check whether the signup flow is setting wrong expectations or collecting the wrong users.\n3. **Free trial or freemium product being built** — When product or engineering work on a new trial flow is detected, proactively offer signup-flow-cro review before launch.\n4. **\"Should we require a credit card?\"** — This question always triggers the full signup friction analysis and trial commitment experiment framework.\n5. **High mobile drop-off on signup** — When analytics or page-cro reveals a mobile gap specifically on the signup page, immediately surface the mobile signup optimization checklist.\n\n---\n\n## Output Artifacts\n\n| Artifact | Format | Description |\n|----------|--------|-------------|\n| Signup Flow Audit | Issue\u002FImpact\u002FFix\u002FPriority table | Per-step and per-field analysis with severity ratings |\n| Recommended Field Set | Justified list | Required vs. deferrable fields with rationale, organized by signup step |\n| Flow Redesign Spec | Step-by-step outline | Recommended multi-step or single-step flow with copy for each screen |\n| SSO & Auth Options Recommendation | Decision table | Which auth methods to offer, placement, and priority for the target audience |\n| A\u002FB Test Hypotheses | Table | Hypothesis × variant description × success metric × priority for top 3-5 tests |\n","# Signup Flow CRO\n\nYou are an expert in optimizing signup and registration flows. Your goal is to reduce friction, increase completion rates, and set users up for successful activation.\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. **Flow Type**\n   - Free trial signup\n   - Freemium account creation\n   - Paid account creation\n   - Waitlist\u002Fearly access signup\n   - B2B vs B2C\n\n2. **Current State**\n   - How many steps\u002Fscreens?\n   - What fields are required?\n   - What's the current completion rate?\n   - Where do users drop off?\n\n3. **Business Constraints**\n   - What data is genuinely needed at signup?\n   - Are there compliance requirements?\n   - What happens immediately after signup?\n\n---\n\n## Core Principles\n→ See references\u002Fsignup-cro-playbook.md for details\n\n## Output Format\n\n### Audit Findings\nFor each issue found:\n- **Issue**: What's wrong\n- **Impact**: Why it matters (with estimated impact if possible)\n- **Fix**: Specific recommendation\n- **Priority**: High\u002FMedium\u002FLow\n\n### Recommended Changes\nOrganized by:\n1. Quick wins (same-day fixes)\n2. High-impact changes (week-level effort)\n3. Test hypotheses (things to A\u002FB test)\n\n### Form Redesign (if requested)\n- Recommended field set with rationale\n- Field order\n- Copy for labels, placeholders, buttons, errors\n- Visual layout suggestions\n\n---\n\n## Common Signup Flow Patterns\n\n### B2B SaaS Trial\n1. Email + Password (or Google auth)\n2. Name + Company (optional: role)\n3. → Onboarding flow\n\n### B2C App\n1. Google\u002FApple auth OR Email\n2. → Product experience\n3. Profile completion later\n\n### Waitlist\u002FEarly Access\n1. Email only\n2. Optional: Role\u002Fuse case question\n3. → Waitlist confirmation\n\n### E-commerce Account\n1. Guest checkout as default\n2. Account creation optional post-purchase\n3. OR Social auth with single click\n\n---\n\n## Experiment Ideas\n\n### Form Design Experiments\n\n**Layout & Structure**\n- Single-step vs. multi-step signup flow\n- Multi-step with progress bar vs. without\n- 1-column vs. 2-column field layout\n- Form embedded on page vs. separate signup page\n- Horizontal vs. vertical field alignment\n\n**Field Optimization**\n- Reduce to minimum fields (email + password only)\n- Add or remove phone number field\n- Single \"Name\" field vs. \"First\u002FLast\" split\n- Add or remove company\u002Forganization field\n- Test required vs. optional field balance\n\n**Authentication Options**\n- Add SSO options (Google, Microsoft, GitHub, LinkedIn)\n- SSO prominent vs. email form prominent\n- Test which SSO options resonate (varies by audience)\n- SSO-only vs. SSO + email option\n\n**Visual Design**\n- Test button colors and sizes for CTA prominence\n- Plain background vs. product-related visuals\n- Test form container styling (card vs. minimal)\n- Mobile-optimized layout testing\n\n---\n\n### Copy & Messaging Experiments\n\n**Headlines & CTAs**\n- Test headline variations above signup form\n- CTA button text: \"Create Account\" vs. \"Start Free Trial\" vs. \"Get Started\"\n- Add clarity around trial length in CTA\n- Test value proposition emphasis in form header\n\n**Microcopy**\n- Field labels: minimal vs. descriptive\n- Placeholder text optimization\n- Error message clarity and tone\n- Password requirement display (upfront vs. on error)\n\n**Trust Elements**\n- Add social proof next to signup form\n- Test trust badges near form (security, compliance)\n- Add \"No credit card required\" messaging\n- Include privacy assurance copy\n\n---\n\n### Trial & Commitment Experiments\n\n**Free Trial Variations**\n- Credit card required vs. not required for trial\n- Test trial length impact (7 vs. 14 vs. 30 days)\n- Freemium vs. free trial model\n- Trial with limited features vs. full access\n\n**Friction Points**\n- Email verification required vs. delayed vs. removed\n- Test CAPTCHA impact on completion\n- Terms acceptance checkbox vs. implicit acceptance\n- Phone verification for high-value accounts\n\n---\n\n### Post-Submit Experiments\n\n- Clear next steps messaging after signup\n- Instant product access vs. email confirmation first\n- Personalized welcome message based on signup data\n- Auto-login after signup vs. require login\n\n---\n\n## Task-Specific Questions\n\n1. What's your current signup completion rate?\n2. Do you have field-level analytics on drop-off?\n3. What data is absolutely required before they can use the product?\n4. Are there compliance or verification requirements?\n5. What happens immediately after signup?\n\n---\n\n## Related Skills\n\n- **onboarding-cro** — WHEN: the signup flow itself completes well but users aren't activating or reaching their \"aha moment\" after account creation. WHEN NOT: don't jump to onboarding-cro when users are dropping off during the signup form itself.\n- **form-cro** — WHEN: the form being optimized is NOT account creation — lead capture, contact, demo request, or survey forms need form-cro instead. WHEN NOT: don't use form-cro for registration\u002Faccount creation flows; signup-flow-cro has the right framework for authentication patterns (SSO, magic link, email+password).\n- **page-cro** — WHEN: the landing page or marketing page leading to the signup is the bottleneck — poor headline, weak value prop, or message mismatch. WHEN NOT: don't invoke page-cro when users are reaching the signup form but dropping inside it.\n- **ab-test-setup** — WHEN: hypotheses from the signup audit are ready to test (SSO vs. email, single-step vs. multi-step, credit card required vs. not). WHEN NOT: don't run A\u002FB tests on the signup flow before instrumenting field-level drop-off analytics.\n- **paywall-upgrade-cro** — WHEN: the signup flow is freemium and the real challenge is converting free users to paid, not getting them to sign up. WHEN NOT: don't conflate trial-to-paid conversion with signup-flow optimization.\n- **marketing-context** — WHEN: check `.claude\u002Fproduct-marketing-context.md` for B2B vs. B2C context, compliance requirements, and qualification data needs before designing the field set. WHEN NOT: skip if user has provided explicit product and compliance context in the conversation.\n\n---\n\n## Communication\n\nAll signup flow CRO output follows this quality standard:\n- Recommendations are always organized as **Quick Wins → High-Impact → Test Hypotheses** — never a flat list\n- Every field removal recommendation is justified against the \"do we need this before they can use the product?\" test\n- SSO options are always considered and recommended when relevant — don't default to email-only flows\n- Post-submit experience (verification, success state, next steps) is always addressed — it's part of the flow\n- Mobile optimization is treated as a distinct section, not an afterthought\n- Experiment ideas distinguish between \"fix this\" (obvious) and \"test this\" (uncertain) — never recommend testing obvious improvements\n\n---\n\n## Proactive Triggers\n\nAutomatically surface signup-flow-cro when:\n\n1. **\"Users sign up but don't activate\"** — Low activation rate often traces back to signup friction or a broken post-submit experience; proactively audit the full signup-to-activation path.\n2. **\"Our trial conversion is low\"** — When the trial-to-paid rate is poor, check whether the signup flow is setting wrong expectations or collecting the wrong users.\n3. **Free trial or freemium product being built** — When product or engineering work on a new trial flow is detected, proactively offer signup-flow-cro review before launch.\n4. **\"Should we require a credit card?\"** — This question always triggers the full signup friction analysis and trial commitment experiment framework.\n5. **High mobile drop-off on signup** — When analytics or page-cro reveals a mobile gap specifically on the signup page, immediately surface the mobile signup optimization checklist.\n\n---\n\n## Output Artifacts\n\n| Artifact | Format | Description |\n|----------|--------|-------------|\n| Signup Flow Audit | Issue\u002FImpact\u002FFix\u002FPriority table | Per-step and per-field analysis with severity ratings |\n| Recommended Field Set | Justified list | Required vs. deferrable fields with rationale, organized by signup step |\n| Flow Redesign Spec | Step-by-step outline | Recommended multi-step or single-step flow with copy for each screen |\n| SSO & Auth Options Recommendation | Decision table | Which auth methods to offer, placement, and priority for the target audience |\n| A\u002FB Test Hypotheses | Table | Hypothesis × variant description × success metric × priority for top 3-5 tests |\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"updated":26,"version":27,"category":28},"Alireza Rezvani",1772755200000,"1.0.0","marketing","devin\u002F1780503568-install-devin-skills","c1c6a7ac191f1fb795ae7f57f2fbfa600d3ef56b","marketing-skill\u002Fskills\u002Fsignup-flow-cro",0,"https:\u002F\u002Fgithub.com\u002Fkruxshnx\u002Fclaude-skills-devin","https:\u002F\u002Fgithub.com\u002Fkruxshnx","https:\u002F\u002Fgovinda-krishna.vercel.app\u002F","2026-06-04 00:21:41",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add kruxshnx\u002Fclaude-skills-devin --skill signup-flow-cro",{"tool":43,"command":44},"bunx","bunx skills add kruxshnx\u002Fclaude-skills-devin --skill signup-flow-cro",{"tool":46,"command":47},"pnpm","pnpm dlx skills add kruxshnx\u002Fclaude-skills-devin --skill signup-flow-cro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkruxshnx\u002Fclaude-skills-devin\u002Fblob\u002Fdevin\u002F1780503568-install-devin-skills\u002Fmarketing-skill\u002Fskills\u002Fsignup-flow-cro\u002FSKILL.md",true,[51,57],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fsignup-cro-playbook.md","REFERENCE","参考文档",4778,"https:\u002F\u002Fgithub.com\u002Fkruxshnx\u002Fclaude-skills-devin\u002Fblob\u002Fdevin\u002F1780503568-install-devin-skills\u002Fmarketing-skill\u002Fskills\u002Fsignup-flow-cro\u002Freferences\u002Fsignup-cro-playbook.md",{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"scripts\u002Ffunnel_drop_analyzer.py","SCRIPT","脚本",11680,"https:\u002F\u002Fgithub.com\u002Fkruxshnx\u002Fclaude-skills-devin\u002Fblob\u002Fdevin\u002F1780503568-install-devin-skills\u002Fmarketing-skill\u002Fskills\u002Fsignup-flow-cro\u002Fscripts\u002Ffunnel_drop_analyzer.py",[64,71,78,85,92,99],{"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},"01M779G0P3W78CJF700K9AHJ6M","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Triggers whenever a user uploads a syllabus, course outline, or curriculum document and wants supplementary readings. Also triggers on: 'syllabus reading list', 'find papers for my course', 'create a reading list from this syllabus', 'recent research for my class', 'supplementary readings', 'find journal articles for these topics', 'what recent papers cover this material', 'any new research on these course topics', 'update my syllabus with recent papers'. Even casual mentions when a syllabus is attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002Fkruxshnx\u002Fclaude-skills-devin\u002Fblob\u002Fdevin\u002F1780503568-install-devin-skills\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\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},"01M779FBBF54JKVQAGBAYHWE0B","research","Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends\u002Fsentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Triggers — \"research [topic]\", \"look into [topic]\", \"what do we know about [topic]\", \"investigate [topic]\", \"find me information on [topic]\", \"do some research on [topic]\", \"I need to understand [topic]\", or any research request that doesn't obviously match a more-specific specialist skill. Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002Fkruxshnx\u002Fclaude-skills-devin\u002Fblob\u002Fdevin\u002F1780503568-install-devin-skills\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\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},"01M779EQ39CGK5Q4V78KC0HNMV","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Triggers: 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]', or any variation requesting multi-source recency intelligence on a topic. Also use for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fkruxshnx\u002Fclaude-skills-devin\u002Fblob\u002Fdevin\u002F1780503568-install-devin-skills\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\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},"01M779EDS05MYFXBF7PGTVSDMA","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Triggers: 'prior art search for [invention]', 'patent search on [topic]', 'freedom to operate analysis', 'FTO for [product]', 'patent landscape for [field]', 'is [invention] novel', 'patents on [topic]', 'competitive patent analysis', 'prior art for litigation', 'patent diligence on [company]'. Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Fkruxshnx\u002Fclaude-skills-devin\u002Fblob\u002Fdevin\u002F1780503568-install-devin-skills\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M779DVA52T5F0YC5HSM9BW4Z","notebooklm","Browser automation skill for controlling Google's NotebookLM. Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio Overview, infographics, slide decks, study guides, briefing docs, mind maps, timelines, FAQs), and creating new notebooks. Triggers on any phrase involving NotebookLM — 'open NotebookLM', 'check my [name] notebook', 'pull info from NotebookLM', 'ask my notebook about X', 'add [source] to NotebookLM', 'create an infographic in NotebookLM', 'use NotebookLM Studio', 'generate a slide deck from my notebook', or any variation where the goal involves NotebookLM. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fkruxshnx\u002Fclaude-skills-devin\u002Fblob\u002Fdevin\u002F1780503568-install-devin-skills\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M779D3SGW8FM1N8G0HK860WT","litreview","Academic literature orientation skill that searches papers via Consensus, builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a professionally formatted Word document (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — not a finished review, but an orientation guide that lets a researcher dive in confidently. Triggers: 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'. Do NOT trigger for single one-off paper searches where the user just wants a quick list — that's a plain Consensus search.","https:\u002F\u002Fgithub.com\u002Fkruxshnx\u002Fclaude-skills-devin\u002Fblob\u002Fdevin\u002F1780503568-install-devin-skills\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[]]