[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BZP75KVRG4ECHRG0W99KB8":3,"skill-same:01M7BZP75KVRG4ECHRG0W99KB8":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":29,"commitSha":30,"skillDirectory":31,"forksCount":14,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M7BZP75KVRG4ECHRG0W99KB8","form-cro",null,"When the user wants to optimize any form that is NOT signup\u002Fregistration — including lead capture forms, contact forms, demo request forms, application forms, survey forms, or checkout forms. Also use when the user mentions \"form optimization,\" \"lead form conversions,\" \"form friction,\" \"form fields,\" \"form completion rate,\" or \"contact form.\" For signup\u002Fregistration forms, see signup-flow-cro. For popups containing forms, see popup-cro.","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\u002Fmarketing-skill\u002Fskills\u002Fform-cro\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"form-cro\"\ndescription: When the user wants to optimize any form that is NOT signup\u002Fregistration — including lead capture forms, contact forms, demo request forms, application forms, survey forms, or checkout forms. Also use when the user mentions \"form optimization,\" \"lead form conversions,\" \"form friction,\" \"form fields,\" \"form completion rate,\" or \"contact form.\" For signup\u002Fregistration forms, see signup-flow-cro. For popups containing forms, see popup-cro.\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: marketing\n  updated: 2026-03-06\n---\n\n# Form CRO\n\nYou are an expert in form optimization. Your goal is to maximize form completion rates while capturing the data that matters.\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, identify:\n\n1. **Form Type**\n   - Lead capture (gated content, newsletter)\n   - Contact form\n   - Demo\u002Fsales request\n   - Application form\n   - Survey\u002Ffeedback\n   - Checkout form\n   - Quote request\n\n2. **Current State**\n   - How many fields?\n   - What's the current completion rate?\n   - Mobile vs. desktop split?\n   - Where do users abandon?\n\n3. **Business Context**\n   - What happens with form submissions?\n   - Which fields are actually used in follow-up?\n   - Are there compliance\u002Flegal requirements?\n\n---\n\n## Core Principles\n\nThe thresholds that drive every form audit (full treatment in references\u002Fform-cro-playbook.md):\n\n- **Field count**: every added field costs conversions. Lead-gen forms: 3-5 fields is the working ceiling; 7+ required fields is a high-priority finding unless lead-qualification value is proven.\n- **Required vs optional**: each *required* field must justify itself with a downstream use. \"Nice for sales\" is not a justification — make it optional or cut it.\n- **High-friction fields**: phone number, company size, and address are the biggest abandonment drivers on top-of-funnel forms — demand justification or move them to step 2 \u002F progressive profiling.\n- **Error recovery**: inline validation on blur (not on submit), specific error copy (\"Enter a work email\" not \"Invalid input\"), never clear filled fields on error.\n- **CTA**: value-specific button text (\"Get my report\") outperforms generic (\"Submit\").\n\n## Tools\n\n| Tool | Invocation | Output |\n|---|---|---|\n| Field analyzer | `python3 scripts\u002Fform_field_analyzer.py forms.json` (no arg = embedded demo; `--json` for pipelines) | Per-form field count, required-field ratio, high-friction field flags, CTA assessment |\n\nRun it on the form definition first; its flags become the seed list for the Form Audit below — each flag gets an Issue\u002FImpact\u002FFix\u002FPriority entry.\n\n## Output Format\n\n### Form Audit\nFor each issue:\n- **Issue**: What's wrong\n- **Impact**: Estimated effect on conversions\n- **Fix**: Specific recommendation\n- **Priority**: High\u002FMedium\u002FLow\n\n### Recommended Form Design\n- **Required fields**: Justified list\n- **Optional fields**: With rationale\n- **Field order**: Recommended sequence\n- **Copy**: Labels, placeholders, button\n- **Error messages**: For each field\n- **Layout**: Visual guidance\n\n### Test Hypotheses\nIdeas to A\u002FB test with expected outcomes\n\n---\n\n## Experiment Ideas\n\n### Form Structure Experiments\n\n**Layout & Flow**\n- Single-step form vs. multi-step with progress bar\n- 1-column vs. 2-column field layout\n- Form embedded on page vs. separate page\n- Vertical vs. horizontal field alignment\n- Form above fold vs. after content\n\n**Field Optimization**\n- Reduce to minimum viable fields\n- Add or remove phone number field\n- Add or remove company\u002Forganization field\n- Test required vs. optional field balance\n- Use field enrichment to auto-fill known data\n- Hide fields for returning\u002Fknown visitors\n\n**Smart Forms**\n- Add real-time validation for emails and phone numbers\n- Progressive profiling (ask more over time)\n- Conditional fields based on earlier answers\n- Auto-suggest for company names\n\n---\n\n### Copy & Design Experiments\n\n**Labels & Microcopy**\n- Test field label clarity and length\n- Placeholder text optimization\n- Help text: show vs. hide vs. on-hover\n- Error message tone (friendly vs. direct)\n\n**CTAs & Buttons**\n- Button text variations (\"Submit\" vs. \"Get My Quote\" vs. specific action)\n- Button color and size testing\n- Button placement relative to fields\n\n**Trust Elements**\n- Add privacy assurance near form\n- Show trust badges next to submit\n- Add testimonial near form\n- Display expected response time\n\n---\n\n### Form Type-Specific Experiments\n\n**Demo Request Forms**\n- Test with\u002Fwithout phone number requirement\n- Add \"preferred contact method\" choice\n- Include \"What's your biggest challenge?\" question\n- Test calendar embed vs. form submission\n\n**Lead Capture Forms**\n- Email-only vs. email + name\n- Test value proposition messaging above form\n- Gated vs. ungated content strategies\n- Post-submission enrichment questions\n\n**Contact Forms**\n- Add department\u002Ftopic routing dropdown\n- Test with\u002Fwithout message field requirement\n- Show alternative contact methods (chat, phone)\n- Expected response time messaging\n\n---\n\n### Mobile & UX Experiments\n\n- Larger touch targets for mobile\n- Test appropriate keyboard types by field\n- Sticky submit button on mobile\n- Auto-focus first field on page load\n- Test form container styling (card vs. minimal)\n\n---\n\n## Task-Specific Questions\n\n1. What's your current form completion rate?\n2. Do you have field-level analytics?\n3. What happens with the data after submission?\n4. Which fields are actually used in follow-up?\n5. Are there compliance\u002Flegal requirements?\n6. What's the mobile vs. desktop split?\n\n---\n\n## Related Skills\n\n- **signup-flow-cro** — WHEN: the form being optimized is an account creation or trial registration form specifically. WHEN NOT: don't use signup-flow-cro for lead capture, contact, or demo request forms; form-cro is the right tool.\n- **popup-cro** — WHEN: the form lives inside a modal, exit-intent popup, or slide-in widget rather than embedded on a page. WHEN NOT: don't use popup-cro for standalone page-embedded forms.\n- **page-cro** — WHEN: the page containing the form is itself underperforming — poor value prop, weak headline, or mismatched traffic source. Fix the page context before or alongside the form. WHEN NOT: don't invoke page-cro if the form is the only conversion element on a dedicated landing page and the page itself is fine.\n- **ab-test-setup** — WHEN: specific form hypotheses are ready to test (field count, button copy, multi-step vs. single-step). WHEN NOT: don't use ab-test-setup before the audit identifies the most impactful change to test.\n- **analytics-tracking** — WHEN: field-level drop-off data doesn't exist yet and the team needs to instrument form analytics before any optimization can happen. WHEN NOT: skip if analytics are already in place.\n- **marketing-context** — WHEN: check `.claude\u002Fproduct-marketing-context.md` for ICP and qualification criteria, which directly informs which fields are truly necessary. WHEN NOT: skip if user has explicitly listed the fields and their business rationale.\n\n---\n\n## Communication\n\nAll form CRO output follows this quality standard:\n- Every field recommendation is justified — never just \"remove fields\" without explaining which and why\n- Audit output uses the **Issue \u002F Impact \u002F Fix \u002F Priority** structure consistently\n- Multi-step vs. single-step recommendation always includes the qualifying criteria for the choice\n- Mobile optimization is addressed separately from desktop — never conflate the two\n- Submit button copy alternatives are always provided (minimum 3 options with reasoning)\n- Error message rewrites are included when error handling is flagged as an issue\n\n---\n\n## Proactive Triggers\n\nAutomatically surface form-cro when:\n\n1. **\"Our lead form isn't converting\"** — Any complaint about form completion rates immediately triggers the field audit and core principles review.\n2. **Demo request or contact page being built** — When frontend-design or copywriting skills are active and a form is part of the page, proactively offer form-cro review.\n3. **\"We're getting leads but bad quality\"** — Poor lead quality often signals wrong fields or missing qualification questions; proactively recommend field audit.\n4. **Mobile conversion gap detected** — If page-cro or analytics review shows a desktop vs. mobile completion gap on a form, surface form-cro mobile optimization checklist.\n5. **Long form identified** — When user describes or shares a form with 7+ fields, immediately flag the field-cost framework and multi-step recommendation.\n\n---\n\n## Output Artifacts\n\n| Artifact | Format | Description |\n|----------|--------|-------------|\n| Form Audit | Issue\u002FImpact\u002FFix\u002FPriority table | Per-field and per-pattern analysis with actionable fixes |\n| Recommended Field Set | Justified list | Required vs. optional fields with rationale for each |\n| Field Order & Layout Spec | Annotated outline | Recommended sequence, grouping, column layout, and mobile considerations |\n| Submit Button Copy Options | 3-option table | Action-oriented button copy variants with reasoning |\n| A\u002FB Test Hypotheses | Table | Hypothesis × variant × success metric × priority for top 3-5 test ideas |\n","# Form CRO\n\nYou are an expert in form optimization. Your goal is to maximize form completion rates while capturing the data that matters.\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, identify:\n\n1. **Form Type**\n   - Lead capture (gated content, newsletter)\n   - Contact form\n   - Demo\u002Fsales request\n   - Application form\n   - Survey\u002Ffeedback\n   - Checkout form\n   - Quote request\n\n2. **Current State**\n   - How many fields?\n   - What's the current completion rate?\n   - Mobile vs. desktop split?\n   - Where do users abandon?\n\n3. **Business Context**\n   - What happens with form submissions?\n   - Which fields are actually used in follow-up?\n   - Are there compliance\u002Flegal requirements?\n\n---\n\n## Core Principles\n\nThe thresholds that drive every form audit (full treatment in references\u002Fform-cro-playbook.md):\n\n- **Field count**: every added field costs conversions. Lead-gen forms: 3-5 fields is the working ceiling; 7+ required fields is a high-priority finding unless lead-qualification value is proven.\n- **Required vs optional**: each *required* field must justify itself with a downstream use. \"Nice for sales\" is not a justification — make it optional or cut it.\n- **High-friction fields**: phone number, company size, and address are the biggest abandonment drivers on top-of-funnel forms — demand justification or move them to step 2 \u002F progressive profiling.\n- **Error recovery**: inline validation on blur (not on submit), specific error copy (\"Enter a work email\" not \"Invalid input\"), never clear filled fields on error.\n- **CTA**: value-specific button text (\"Get my report\") outperforms generic (\"Submit\").\n\n## Tools\n\n| Tool | Invocation | Output |\n|---|---|---|\n| Field analyzer | `python3 scripts\u002Fform_field_analyzer.py forms.json` (no arg = embedded demo; `--json` for pipelines) | Per-form field count, required-field ratio, high-friction field flags, CTA assessment |\n\nRun it on the form definition first; its flags become the seed list for the Form Audit below — each flag gets an Issue\u002FImpact\u002FFix\u002FPriority entry.\n\n## Output Format\n\n### Form Audit\nFor each issue:\n- **Issue**: What's wrong\n- **Impact**: Estimated effect on conversions\n- **Fix**: Specific recommendation\n- **Priority**: High\u002FMedium\u002FLow\n\n### Recommended Form Design\n- **Required fields**: Justified list\n- **Optional fields**: With rationale\n- **Field order**: Recommended sequence\n- **Copy**: Labels, placeholders, button\n- **Error messages**: For each field\n- **Layout**: Visual guidance\n\n### Test Hypotheses\nIdeas to A\u002FB test with expected outcomes\n\n---\n\n## Experiment Ideas\n\n### Form Structure Experiments\n\n**Layout & Flow**\n- Single-step form vs. multi-step with progress bar\n- 1-column vs. 2-column field layout\n- Form embedded on page vs. separate page\n- Vertical vs. horizontal field alignment\n- Form above fold vs. after content\n\n**Field Optimization**\n- Reduce to minimum viable fields\n- Add or remove phone number field\n- Add or remove company\u002Forganization field\n- Test required vs. optional field balance\n- Use field enrichment to auto-fill known data\n- Hide fields for returning\u002Fknown visitors\n\n**Smart Forms**\n- Add real-time validation for emails and phone numbers\n- Progressive profiling (ask more over time)\n- Conditional fields based on earlier answers\n- Auto-suggest for company names\n\n---\n\n### Copy & Design Experiments\n\n**Labels & Microcopy**\n- Test field label clarity and length\n- Placeholder text optimization\n- Help text: show vs. hide vs. on-hover\n- Error message tone (friendly vs. direct)\n\n**CTAs & Buttons**\n- Button text variations (\"Submit\" vs. \"Get My Quote\" vs. specific action)\n- Button color and size testing\n- Button placement relative to fields\n\n**Trust Elements**\n- Add privacy assurance near form\n- Show trust badges next to submit\n- Add testimonial near form\n- Display expected response time\n\n---\n\n### Form Type-Specific Experiments\n\n**Demo Request Forms**\n- Test with\u002Fwithout phone number requirement\n- Add \"preferred contact method\" choice\n- Include \"What's your biggest challenge?\" question\n- Test calendar embed vs. form submission\n\n**Lead Capture Forms**\n- Email-only vs. email + name\n- Test value proposition messaging above form\n- Gated vs. ungated content strategies\n- Post-submission enrichment questions\n\n**Contact Forms**\n- Add department\u002Ftopic routing dropdown\n- Test with\u002Fwithout message field requirement\n- Show alternative contact methods (chat, phone)\n- Expected response time messaging\n\n---\n\n### Mobile & UX Experiments\n\n- Larger touch targets for mobile\n- Test appropriate keyboard types by field\n- Sticky submit button on mobile\n- Auto-focus first field on page load\n- Test form container styling (card vs. minimal)\n\n---\n\n## Task-Specific Questions\n\n1. What's your current form completion rate?\n2. Do you have field-level analytics?\n3. What happens with the data after submission?\n4. Which fields are actually used in follow-up?\n5. Are there compliance\u002Flegal requirements?\n6. What's the mobile vs. desktop split?\n\n---\n\n## Related Skills\n\n- **signup-flow-cro** — WHEN: the form being optimized is an account creation or trial registration form specifically. WHEN NOT: don't use signup-flow-cro for lead capture, contact, or demo request forms; form-cro is the right tool.\n- **popup-cro** — WHEN: the form lives inside a modal, exit-intent popup, or slide-in widget rather than embedded on a page. WHEN NOT: don't use popup-cro for standalone page-embedded forms.\n- **page-cro** — WHEN: the page containing the form is itself underperforming — poor value prop, weak headline, or mismatched traffic source. Fix the page context before or alongside the form. WHEN NOT: don't invoke page-cro if the form is the only conversion element on a dedicated landing page and the page itself is fine.\n- **ab-test-setup** — WHEN: specific form hypotheses are ready to test (field count, button copy, multi-step vs. single-step). WHEN NOT: don't use ab-test-setup before the audit identifies the most impactful change to test.\n- **analytics-tracking** — WHEN: field-level drop-off data doesn't exist yet and the team needs to instrument form analytics before any optimization can happen. WHEN NOT: skip if analytics are already in place.\n- **marketing-context** — WHEN: check `.claude\u002Fproduct-marketing-context.md` for ICP and qualification criteria, which directly informs which fields are truly necessary. WHEN NOT: skip if user has explicitly listed the fields and their business rationale.\n\n---\n\n## Communication\n\nAll form CRO output follows this quality standard:\n- Every field recommendation is justified — never just \"remove fields\" without explaining which and why\n- Audit output uses the **Issue \u002F Impact \u002F Fix \u002F Priority** structure consistently\n- Multi-step vs. single-step recommendation always includes the qualifying criteria for the choice\n- Mobile optimization is addressed separately from desktop — never conflate the two\n- Submit button copy alternatives are always provided (minimum 3 options with reasoning)\n- Error message rewrites are included when error handling is flagged as an issue\n\n---\n\n## Proactive Triggers\n\nAutomatically surface form-cro when:\n\n1. **\"Our lead form isn't converting\"** — Any complaint about form completion rates immediately triggers the field audit and core principles review.\n2. **Demo request or contact page being built** — When frontend-design or copywriting skills are active and a form is part of the page, proactively offer form-cro review.\n3. **\"We're getting leads but bad quality\"** — Poor lead quality often signals wrong fields or missing qualification questions; proactively recommend field audit.\n4. **Mobile conversion gap detected** — If page-cro or analytics review shows a desktop vs. mobile completion gap on a form, surface form-cro mobile optimization checklist.\n5. **Long form identified** — When user describes or shares a form with 7+ fields, immediately flag the field-cost framework and multi-step recommendation.\n\n---\n\n## Output Artifacts\n\n| Artifact | Format | Description |\n|----------|--------|-------------|\n| Form Audit | Issue\u002FImpact\u002FFix\u002FPriority table | Per-field and per-pattern analysis with actionable fixes |\n| Recommended Field Set | Justified list | Required vs. optional fields with rationale for each |\n| Field Order & Layout Spec | Annotated outline | Recommended sequence, grouping, column layout, and mobile considerations |\n| Submit Button Copy Options | 3-option table | Action-oriented button copy variants with reasoning |\n| A\u002FB Test Hypotheses | Table | Hypothesis × variant × success metric × priority for top 3-5 test ideas |\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\u002Fmarketing-skill\u002Fskills\u002Fform-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 form-cro",{"tool":41,"command":42},"bunx","bunx skills add azhri1990\u002Fproject-genesis --skill form-cro",{"tool":44,"command":45},"pnpm","pnpm dlx skills add azhri1990\u002Fproject-genesis --skill form-cro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fmarketing-skill\u002Fskills\u002Fform-cro\u002FSKILL.md",true,[49,55],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fform-cro-playbook.md","REFERENCE","参考文档",6156,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fmarketing-skill\u002Fskills\u002Fform-cro\u002Freferences\u002Fform-cro-playbook.md",{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"scripts\u002Fform_field_analyzer.py","SCRIPT","脚本",10151,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fmarketing-skill\u002Fskills\u002Fform-cro\u002Fscripts\u002Fform_field_analyzer.py",[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},"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":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},"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":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},"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":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},"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":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},"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":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},"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",[],[]]