[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AE1KB5CZN1T6PPH9AR0GCS":3,"skill-same:01M6AE1KB5CZN1T6PPH9AR0GCS":102},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":49,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M6AE1KB5CZN1T6PPH9AR0GCS","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.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33481,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fbusiness-marketing\u002Fform-cro\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"form cro","cro","form","signup","lead","when","lead capture","request","rate","for","checkout","popups","demo","forms","optimize","registration","survey","use","flow","Optimization","2026-11-10 10:12:30",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.\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\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\n### 1. Every Field Has a Cost\nEach field reduces completion rate. Rule of thumb:\n- 3 fields: Baseline\n- 4-6 fields: 10-25% reduction\n- 7+ fields: 25-50%+ reduction\n\nFor each field, ask:\n- Is this absolutely necessary before we can help them?\n- Can we get this information another way?\n- Can we ask this later?\n\n### 2. Value Must Exceed Effort\n- Clear value proposition above form\n- Make what they get obvious\n- Reduce perceived effort (field count, labels)\n\n### 3. Reduce Cognitive Load\n- One question per field\n- Clear, conversational labels\n- Logical grouping and order\n- Smart defaults where possible\n\n---\n\n## Field-by-Field Optimization\n\n### Email Field\n- Single field, no confirmation\n- Inline validation\n- Typo detection (did you mean gmail.com?)\n- Proper mobile keyboard\n\n### Name Fields\n- Single \"Name\" vs. First\u002FLast — test this\n- Single field reduces friction\n- Split needed only if personalization requires it\n\n### Phone Number\n- Make optional if possible\n- If required, explain why\n- Auto-format as they type\n- Country code handling\n\n### Company\u002FOrganization\n- Auto-suggest for faster entry\n- Enrichment after submission (Clearbit, etc.)\n- Consider inferring from email domain\n\n### Job Title\u002FRole\n- Dropdown if categories matter\n- Free text if wide variation\n- Consider making optional\n\n### Message\u002FComments (Free Text)\n- Make optional\n- Reasonable character guidance\n- Expand on focus\n\n### Dropdown Selects\n- \"Select one...\" placeholder\n- Searchable if many options\n- Consider radio buttons if \u003C 5 options\n- \"Other\" option with text field\n\n### Checkboxes (Multi-select)\n- Clear, parallel labels\n- Reasonable number of options\n- Consider \"Select all that apply\" instruction\n\n---\n\n## Form Layout Optimization\n\n### Field Order\n1. Start with easiest fields (name, email)\n2. Build commitment before asking more\n3. Sensitive fields last (phone, company size)\n4. Logical grouping if many fields\n\n### Labels and Placeholders\n- Labels: Always visible (not just placeholder)\n- Placeholders: Examples, not labels\n- Help text: Only when genuinely helpful\n\n**Good:**\n```\nEmail\n[name@company.com]\n```\n\n**Bad:**\n```\n[Enter your email address]  ← Disappears on focus\n```\n\n### Visual Design\n- Sufficient spacing between fields\n- Clear visual hierarchy\n- CTA button stands out\n- Mobile-friendly tap targets (44px+)\n\n### Single Column vs. Multi-Column\n- Single column: Higher completion, mobile-friendly\n- Multi-column: Only for short related fields (First\u002FLast name)\n- When in doubt, single column\n\n---\n\n## Multi-Step Forms\n\n### When to Use Multi-Step\n- More than 5-6 fields\n- Logically distinct sections\n- Conditional paths based on answers\n- Complex forms (applications, quotes)\n\n### Multi-Step Best Practices\n- Progress indicator (step X of Y)\n- Start with easy, end with sensitive\n- One topic per step\n- Allow back navigation\n- Save progress (don't lose data on refresh)\n- Clear indication of required vs. optional\n\n### Progressive Commitment Pattern\n1. Low-friction start (just email)\n2. More detail (name, company)\n3. Qualifying questions\n4. Contact preferences\n\n---\n\n## Error Handling\n\n### Inline Validation\n- Validate as they move to next field\n- Don't validate too aggressively while typing\n- Clear visual indicators (green check, red border)\n\n### Error Messages\n- Specific to the problem\n- Suggest how to fix\n- Positioned near the field\n- Don't clear their input\n\n**Good:** \"Please enter a valid email address (e.g., name@company.com)\"\n**Bad:** \"Invalid input\"\n\n### On Submit\n- Focus on first error field\n- Summarize errors if multiple\n- Preserve all entered data\n- Don't clear form on error\n\n---\n\n## Submit Button Optimization\n\n### Button Copy\nWeak: \"Submit\" | \"Send\"\nStrong: \"[Action] + [What they get]\"\n\nExamples:\n- \"Get My Free Quote\"\n- \"Download the Guide\"\n- \"Request Demo\"\n- \"Send Message\"\n- \"Start Free Trial\"\n\n### Button Placement\n- Immediately after last field\n- Left-aligned with fields\n- Sufficient size and contrast\n- Mobile: Sticky or clearly visible\n\n### Post-Submit States\n- Loading state (disable button, show spinner)\n- Success confirmation (clear next steps)\n- Error handling (clear message, focus on issue)\n\n---\n\n## Trust and Friction Reduction\n\n### Near the Form\n- Privacy statement: \"We'll never share your info\"\n- Security badges if collecting sensitive data\n- Testimonial or social proof\n- Expected response time\n\n### Reducing Perceived Effort\n- \"Takes 30 seconds\"\n- Field count indicator\n- Remove visual clutter\n- Generous white space\n\n### Addressing Objections\n- \"No spam, unsubscribe anytime\"\n- \"We won't share your number\"\n- \"No credit card required\"\n\n---\n\n## Form Types: Specific Guidance\n\n### Lead Capture (Gated Content)\n- Minimum viable fields (often just email)\n- Clear value proposition for what they get\n- Consider asking enrichment questions post-download\n- Test email-only vs. email + name\n\n### Contact Form\n- Essential: Email\u002FName + Message\n- Phone optional\n- Set response time expectations\n- Offer alternatives (chat, phone)\n\n### Demo Request\n- Name, Email, Company required\n- Phone: Optional with \"preferred contact\" choice\n- Use case\u002Fgoal question helps personalize\n- Calendar embed can increase show rate\n\n### Quote\u002FEstimate Request\n- Multi-step often works well\n- Start with easy questions\n- Technical details later\n- Save progress for complex forms\n\n### Survey Forms\n- Progress bar essential\n- One question per screen for engagement\n- Skip logic for relevance\n- Consider incentive for completion\n\n---\n\n## Mobile Optimization\n\n- Larger touch targets (44px minimum height)\n- Appropriate keyboard types (email, tel, number)\n- Autofill support\n- Single column only\n- Sticky submit button\n- Minimal typing (dropdowns, buttons)\n\n---\n\n## Measurement\n\n### Key Metrics\n- **Form start rate**: Page views → Started form\n- **Completion rate**: Started → Submitted\n- **Field drop-off**: Which fields lose people\n- **Error rate**: By field\n- **Time to complete**: Total and by field\n- **Mobile vs. desktop**: Completion by device\n\n### What to Track\n- Form views\n- First field focus\n- Each field completion\n- Errors by field\n- Submit attempts\n- Successful submissions\n\n---\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## Questions to Ask\n\nIf you need more context:\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**: For account creation forms\n- **popup-cro**: For forms inside popups\u002Fmodals\n- **page-cro**: For the page containing the form\n- **ab-test-setup**: For testing form changes\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\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\n### 1. Every Field Has a Cost\nEach field reduces completion rate. Rule of thumb:\n- 3 fields: Baseline\n- 4-6 fields: 10-25% reduction\n- 7+ fields: 25-50%+ reduction\n\nFor each field, ask:\n- Is this absolutely necessary before we can help them?\n- Can we get this information another way?\n- Can we ask this later?\n\n### 2. Value Must Exceed Effort\n- Clear value proposition above form\n- Make what they get obvious\n- Reduce perceived effort (field count, labels)\n\n### 3. Reduce Cognitive Load\n- One question per field\n- Clear, conversational labels\n- Logical grouping and order\n- Smart defaults where possible\n\n---\n\n## Field-by-Field Optimization\n\n### Email Field\n- Single field, no confirmation\n- Inline validation\n- Typo detection (did you mean gmail.com?)\n- Proper mobile keyboard\n\n### Name Fields\n- Single \"Name\" vs. First\u002FLast — test this\n- Single field reduces friction\n- Split needed only if personalization requires it\n\n### Phone Number\n- Make optional if possible\n- If required, explain why\n- Auto-format as they type\n- Country code handling\n\n### Company\u002FOrganization\n- Auto-suggest for faster entry\n- Enrichment after submission (Clearbit, etc.)\n- Consider inferring from email domain\n\n### Job Title\u002FRole\n- Dropdown if categories matter\n- Free text if wide variation\n- Consider making optional\n\n### Message\u002FComments (Free Text)\n- Make optional\n- Reasonable character guidance\n- Expand on focus\n\n### Dropdown Selects\n- \"Select one...\" placeholder\n- Searchable if many options\n- Consider radio buttons if \u003C 5 options\n- \"Other\" option with text field\n\n### Checkboxes (Multi-select)\n- Clear, parallel labels\n- Reasonable number of options\n- Consider \"Select all that apply\" instruction\n\n---\n\n## Form Layout Optimization\n\n### Field Order\n1. Start with easiest fields (name, email)\n2. Build commitment before asking more\n3. Sensitive fields last (phone, company size)\n4. Logical grouping if many fields\n\n### Labels and Placeholders\n- Labels: Always visible (not just placeholder)\n- Placeholders: Examples, not labels\n- Help text: Only when genuinely helpful\n\n**Good:**\n```\nEmail\n[name@company.com]\n```\n\n**Bad:**\n```\n[Enter your email address]  ← Disappears on focus\n```\n\n### Visual Design\n- Sufficient spacing between fields\n- Clear visual hierarchy\n- CTA button stands out\n- Mobile-friendly tap targets (44px+)\n\n### Single Column vs. Multi-Column\n- Single column: Higher completion, mobile-friendly\n- Multi-column: Only for short related fields (First\u002FLast name)\n- When in doubt, single column\n\n---\n\n## Multi-Step Forms\n\n### When to Use Multi-Step\n- More than 5-6 fields\n- Logically distinct sections\n- Conditional paths based on answers\n- Complex forms (applications, quotes)\n\n### Multi-Step Best Practices\n- Progress indicator (step X of Y)\n- Start with easy, end with sensitive\n- One topic per step\n- Allow back navigation\n- Save progress (don't lose data on refresh)\n- Clear indication of required vs. optional\n\n### Progressive Commitment Pattern\n1. Low-friction start (just email)\n2. More detail (name, company)\n3. Qualifying questions\n4. Contact preferences\n\n---\n\n## Error Handling\n\n### Inline Validation\n- Validate as they move to next field\n- Don't validate too aggressively while typing\n- Clear visual indicators (green check, red border)\n\n### Error Messages\n- Specific to the problem\n- Suggest how to fix\n- Positioned near the field\n- Don't clear their input\n\n**Good:** \"Please enter a valid email address (e.g., name@company.com)\"\n**Bad:** \"Invalid input\"\n\n### On Submit\n- Focus on first error field\n- Summarize errors if multiple\n- Preserve all entered data\n- Don't clear form on error\n\n---\n\n## Submit Button Optimization\n\n### Button Copy\nWeak: \"Submit\" | \"Send\"\nStrong: \"[Action] + [What they get]\"\n\nExamples:\n- \"Get My Free Quote\"\n- \"Download the Guide\"\n- \"Request Demo\"\n- \"Send Message\"\n- \"Start Free Trial\"\n\n### Button Placement\n- Immediately after last field\n- Left-aligned with fields\n- Sufficient size and contrast\n- Mobile: Sticky or clearly visible\n\n### Post-Submit States\n- Loading state (disable button, show spinner)\n- Success confirmation (clear next steps)\n- Error handling (clear message, focus on issue)\n\n---\n\n## Trust and Friction Reduction\n\n### Near the Form\n- Privacy statement: \"We'll never share your info\"\n- Security badges if collecting sensitive data\n- Testimonial or social proof\n- Expected response time\n\n### Reducing Perceived Effort\n- \"Takes 30 seconds\"\n- Field count indicator\n- Remove visual clutter\n- Generous white space\n\n### Addressing Objections\n- \"No spam, unsubscribe anytime\"\n- \"We won't share your number\"\n- \"No credit card required\"\n\n---\n\n## Form Types: Specific Guidance\n\n### Lead Capture (Gated Content)\n- Minimum viable fields (often just email)\n- Clear value proposition for what they get\n- Consider asking enrichment questions post-download\n- Test email-only vs. email + name\n\n### Contact Form\n- Essential: Email\u002FName + Message\n- Phone optional\n- Set response time expectations\n- Offer alternatives (chat, phone)\n\n### Demo Request\n- Name, Email, Company required\n- Phone: Optional with \"preferred contact\" choice\n- Use case\u002Fgoal question helps personalize\n- Calendar embed can increase show rate\n\n### Quote\u002FEstimate Request\n- Multi-step often works well\n- Start with easy questions\n- Technical details later\n- Save progress for complex forms\n\n### Survey Forms\n- Progress bar essential\n- One question per screen for engagement\n- Skip logic for relevance\n- Consider incentive for completion\n\n---\n\n## Mobile Optimization\n\n- Larger touch targets (44px minimum height)\n- Appropriate keyboard types (email, tel, number)\n- Autofill support\n- Single column only\n- Sticky submit button\n- Minimal typing (dropdowns, buttons)\n\n---\n\n## Measurement\n\n### Key Metrics\n- **Form start rate**: Page views → Started form\n- **Completion rate**: Started → Submitted\n- **Field drop-off**: Which fields lose people\n- **Error rate**: By field\n- **Time to complete**: Total and by field\n- **Mobile vs. desktop**: Completion by device\n\n### What to Track\n- Form views\n- First field focus\n- Each field completion\n- Errors by field\n- Submit attempts\n- Successful submissions\n\n---\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## Questions to Ask\n\nIf you need more context:\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**: For account creation forms\n- **popup-cro**: For forms inside popups\u002Fmodals\n- **page-cro**: For the page containing the form\n- **ab-test-setup**: For testing form changes\n",{"name":5,"description":7},"main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fbusiness-marketing\u002Fform-cro",3931,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates","https:\u002F\u002Faitmpl.com","https:\u002F\u002Fgithub.com\u002Fdavila7","https:\u002F\u002Fdanielavila.me","Building AI dev tools with LLMs","2026-11-14 06:14:46",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add davila7\u002Fclaude-code-templates --skill form-cro",{"tool":60,"command":61},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill form-cro",{"tool":63,"command":64},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill form-cro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fbusiness-marketing\u002Fform-cro\u002FSKILL.md",true,[68,74,78,82,86,90,94,98],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Flark-calendar-agenda.md","REFERENCE","参考文档",2313,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Flark-calendar\u002Freferences\u002Flark-calendar-agenda.md",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Flark-calendar-create.md",5155,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Flark-calendar\u002Freferences\u002Flark-calendar-create.md",{"path":79,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Flark-calendar-freebusy.md",3855,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Flark-calendar\u002Freferences\u002Flark-calendar-freebusy.md",{"path":83,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Flark-calendar-room-find.md",9279,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Flark-calendar\u002Freferences\u002Flark-calendar-room-find.md",{"path":87,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Flark-calendar-rsvp.md",1358,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Flark-calendar\u002Freferences\u002Flark-calendar-rsvp.md",{"path":91,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Flark-calendar-schedule-meeting.md",18837,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Flark-calendar\u002Freferences\u002Flark-calendar-schedule-meeting.md",{"path":95,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Flark-calendar-suggestion.md",7196,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Flark-calendar\u002Freferences\u002Flark-calendar-suggestion.md",{"path":99,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Flark-calendar-update.md",6483,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Flark-calendar\u002Freferences\u002Flark-calendar-update.md",[103,132,159,192,227,251],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":114,"publishedAt":39},"01M70NHBTQ8BV0A2SCAZXEPHCX","wealthville-pool-scoring","Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter\u002FHold\u002FExit\u002FReduce\u002FAvoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fwealthville-pool-scoring\u002FSKILL.md",[109],{"categoryNo":110,"categoryName":111,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[115,116,117,118,119,28,120,121,36,24,122,123,124,125,126,127,128,129,130,131],"scoring","pool","wealthville pool scoring","liquidity","which","exit","now","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":139,"publishedAt":39},"01M70MB6VR8ERJ4EM8D5KHBMEV","technical-debt-auditor","Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO\u002FFIXME\u002FHACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like \"where should I focus refactoring\", \"find code smells\", \"audit my codebase\", \"what technical debt do we have\", \"prioritize cleanup work\", or asks about code quality metrics. Also trigger when the user mentions \"code rot\", \"legacy cleanup\", \"refactoring priorities\", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say \"technical debt\" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftechnical-debt-auditor\u002FSKILL.md",[138],{"categoryNo":110,"categoryName":111,"taxonomyType":112,"taxonomyTypeDesc":113},[140,141,142,143,144,145,146,147,148,149,150,24,151,152,153,154,155,156,157,158],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":174,"publishedAt":39},"01M70KPYH9QNHCNME5GJQGE22K","readonly-sql-guard","Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production\u002FERP\u002Fanalytics database (a \"query\" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write\u002FDDL\u002Fside-effect\u002Ftransaction-escape risks. Checks what a statement CALLS, not just its shape.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdatabase\u002Freadonly-sql-guard\u002FSKILL.md",[165,168,169],{"categoryNo":166,"categoryName":167,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":110,"categoryName":111,"taxonomyType":112,"taxonomyTypeDesc":113},{"categoryNo":170,"categoryName":171,"taxonomyType":172,"taxonomyTypeDesc":173},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[175,176,177,178,179,180,181,28,182,183,184,185,186,187,188,36,189,190,24,191],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":196,"licenseFileUrl":197,"sourceHtmlUrl":198,"categories":199,"keywords":203,"publishedAt":39},"01M6AFY6F7CC2BBZP1QD6VTNVC","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[200],{"categoryNo":201,"categoryName":202,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000009","前端开发",[204,205,206,207,208,209,210,211,212,213,214,215,216,217,218,219,220,221,222,223,224,225,28,226],"artifacts builder","web","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","file","components","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":228,"name":229,"nameZh":6,"description":230,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":196,"licenseFileUrl":231,"sourceHtmlUrl":232,"categories":233,"keywords":238,"publishedAt":39},"01M6AFWF33SFV9Z3SF4PEEE4BF","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[234,237],{"categoryNo":235,"categoryName":236,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":201,"categoryName":202,"taxonomyType":112,"taxonomyTypeDesc":113},[239,240,241,242,243,205,244,214,215,245,246,247,248,28,249,123,250],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":252,"name":253,"nameZh":6,"description":254,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":196,"licenseFileUrl":255,"sourceHtmlUrl":256,"categories":257,"keywords":265,"publishedAt":39},"01M6AF67Q67JJJ5V51JR2P52KA","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FSKILL.md",[258,261,262],{"categoryNo":259,"categoryName":260,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":110,"categoryName":111,"taxonomyType":112,"taxonomyTypeDesc":113},{"categoryNo":263,"categoryName":264,"taxonomyType":172,"taxonomyTypeDesc":173},"01JBSEEDCAT000000000000036","内容创作者",[266,267,268,269,270,271,272,273,207,274,217,151,275,276,277,278,279,187,280,24,281,282,283,284,285,129,286],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]