[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AE3QG4XVM1W91WB35WT0WB":3,"skill-same:01M6AE3QG4XVM1W91WB35WT0WB":75},{"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":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M6AE3QG4XVM1W91WB35WT0WB","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.","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\u002Fsignup-flow-cro\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"flow","signup flow cro","cro","signup","lead","onboarding","when","lead capture","reduce","for","flows","account creation","form","free","creation","forms","optimize","registration","activation","use","Optimization","2026-11-10 10:12:30",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.\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\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\n### 1. Minimize Required Fields\nEvery field reduces conversion. For each field, ask:\n- Do we absolutely need this before they can use the product?\n- Can we collect this later through progressive profiling?\n- Can we infer this from other data?\n\n**Typical field priority:**\n- Essential: Email (or phone), Password\n- Often needed: Name\n- Usually deferrable: Company, Role, Team size, Phone, Address\n\n### 2. Show Value Before Asking for Commitment\n- What can you show\u002Fgive before requiring signup?\n- Can they experience the product before creating an account?\n- Reverse the order: value first, signup second\n\n### 3. Reduce Perceived Effort\n- Show progress if multi-step\n- Group related fields\n- Use smart defaults\n- Pre-fill when possible\n\n### 4. Remove Uncertainty\n- Clear expectations (\"Takes 30 seconds\")\n- Show what happens after signup\n- No surprises (hidden requirements, unexpected steps)\n\n---\n\n## Field-by-Field Optimization\n\n### Email Field\n- Single field (no email confirmation field)\n- Inline validation for format\n- Check for common typos (gmial.com → gmail.com)\n- Clear error messages\n\n### Password Field\n- Show password toggle (eye icon)\n- Show requirements upfront, not after failure\n- Consider passphrase hints for strength\n- Update requirement indicators in real-time\n\n**Better password UX:**\n- Allow paste (don't disable)\n- Show strength meter instead of rigid rules\n- Consider passwordless options\n\n### Name Field\n- Single \"Full name\" field vs. First\u002FLast split (test this)\n- Only require if immediately used (personalization)\n- Consider making optional\n\n### Social Auth Options\n- Place prominently (often higher conversion than email)\n- Show most relevant options for your audience\n  - B2C: Google, Apple, Facebook\n  - B2B: Google, Microsoft, SSO\n- Clear visual separation from email signup\n- Consider \"Sign up with Google\" as primary\n\n### Phone Number\n- Defer unless essential (SMS verification, calling leads)\n- If required, explain why\n- Use proper input type with country code handling\n- Format as they type\n\n### Company\u002FOrganization\n- Defer if possible\n- Auto-suggest as they type\n- Infer from email domain when possible\n\n### Use Case \u002F Role Questions\n- Defer to onboarding if possible\n- If needed at signup, keep to one question\n- Use progressive disclosure (don't show all options at once)\n\n---\n\n## Single-Step vs. Multi-Step\n\n### Single-Step Works When:\n- 3 or fewer fields\n- Simple B2C products\n- High-intent visitors (from ads, waitlist)\n\n### Multi-Step Works When:\n- More than 3-4 fields needed\n- Complex B2B products needing segmentation\n- You need to collect different types of info\n\n### Multi-Step Best Practices\n- Show progress indicator\n- Lead with easy questions (name, email)\n- Put harder questions later (after psychological commitment)\n- Each step should feel completable in seconds\n- Allow back navigation\n- Save progress (don't lose data on refresh)\n\n**Progressive commitment pattern:**\n1. Email only (lowest barrier)\n2. Password + name\n3. Customization questions (optional)\n\n---\n\n## Trust and Friction Reduction\n\n### At the Form Level\n- \"No credit card required\" (if true)\n- \"Free forever\" or \"14-day free trial\"\n- Privacy note: \"We'll never share your email\"\n- Security badges if relevant\n- Testimonial near signup form\n\n### Error Handling\n- Inline validation (not just on submit)\n- Specific error messages (\"Email already registered\" + recovery path)\n- Don't clear the form on error\n- Focus on the problem field\n\n### Microcopy\n- Placeholder text: Use for examples, not labels\n- Labels: Always visible (not just placeholders)\n- Help text: Only when needed, placed close to field\n\n---\n\n## Mobile Signup Optimization\n\n- Larger touch targets (44px+ height)\n- Appropriate keyboard types (email, tel, etc.)\n- Autofill support\n- Reduce typing (social auth, pre-fill)\n- Single column layout\n- Sticky CTA button\n- Test with actual devices\n\n---\n\n## Post-Submit Experience\n\n### Success State\n- Clear confirmation\n- Immediate next step\n- If email verification required:\n  - Explain what to do\n  - Easy resend option\n  - Check spam reminder\n  - Option to change email if wrong\n\n### Verification Flows\n- Consider delaying verification until necessary\n- Magic link as alternative to password\n- Let users explore while awaiting verification\n- Clear re-engagement if verification stalls\n\n---\n\n## Measurement\n\n### Key Metrics\n- Form start rate (landed → started filling)\n- Form completion rate (started → submitted)\n- Field-level drop-off (which fields lose people)\n- Time to complete\n- Error rate by field\n- Mobile vs. desktop completion\n\n### What to Track\n- Each field interaction (focus, blur, error)\n- Step progression in multi-step\n- Social auth vs. email signup ratio\n- Time between steps\n\n---\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## Questions to Ask\n\nIf you need more context:\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**: For optimizing what happens after signup\n- **form-cro**: For non-signup forms (lead capture, contact)\n- **page-cro**: For the landing page leading to signup\n- **ab-test-setup**: For testing signup flow changes\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\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\n### 1. Minimize Required Fields\nEvery field reduces conversion. For each field, ask:\n- Do we absolutely need this before they can use the product?\n- Can we collect this later through progressive profiling?\n- Can we infer this from other data?\n\n**Typical field priority:**\n- Essential: Email (or phone), Password\n- Often needed: Name\n- Usually deferrable: Company, Role, Team size, Phone, Address\n\n### 2. Show Value Before Asking for Commitment\n- What can you show\u002Fgive before requiring signup?\n- Can they experience the product before creating an account?\n- Reverse the order: value first, signup second\n\n### 3. Reduce Perceived Effort\n- Show progress if multi-step\n- Group related fields\n- Use smart defaults\n- Pre-fill when possible\n\n### 4. Remove Uncertainty\n- Clear expectations (\"Takes 30 seconds\")\n- Show what happens after signup\n- No surprises (hidden requirements, unexpected steps)\n\n---\n\n## Field-by-Field Optimization\n\n### Email Field\n- Single field (no email confirmation field)\n- Inline validation for format\n- Check for common typos (gmial.com → gmail.com)\n- Clear error messages\n\n### Password Field\n- Show password toggle (eye icon)\n- Show requirements upfront, not after failure\n- Consider passphrase hints for strength\n- Update requirement indicators in real-time\n\n**Better password UX:**\n- Allow paste (don't disable)\n- Show strength meter instead of rigid rules\n- Consider passwordless options\n\n### Name Field\n- Single \"Full name\" field vs. First\u002FLast split (test this)\n- Only require if immediately used (personalization)\n- Consider making optional\n\n### Social Auth Options\n- Place prominently (often higher conversion than email)\n- Show most relevant options for your audience\n  - B2C: Google, Apple, Facebook\n  - B2B: Google, Microsoft, SSO\n- Clear visual separation from email signup\n- Consider \"Sign up with Google\" as primary\n\n### Phone Number\n- Defer unless essential (SMS verification, calling leads)\n- If required, explain why\n- Use proper input type with country code handling\n- Format as they type\n\n### Company\u002FOrganization\n- Defer if possible\n- Auto-suggest as they type\n- Infer from email domain when possible\n\n### Use Case \u002F Role Questions\n- Defer to onboarding if possible\n- If needed at signup, keep to one question\n- Use progressive disclosure (don't show all options at once)\n\n---\n\n## Single-Step vs. Multi-Step\n\n### Single-Step Works When:\n- 3 or fewer fields\n- Simple B2C products\n- High-intent visitors (from ads, waitlist)\n\n### Multi-Step Works When:\n- More than 3-4 fields needed\n- Complex B2B products needing segmentation\n- You need to collect different types of info\n\n### Multi-Step Best Practices\n- Show progress indicator\n- Lead with easy questions (name, email)\n- Put harder questions later (after psychological commitment)\n- Each step should feel completable in seconds\n- Allow back navigation\n- Save progress (don't lose data on refresh)\n\n**Progressive commitment pattern:**\n1. Email only (lowest barrier)\n2. Password + name\n3. Customization questions (optional)\n\n---\n\n## Trust and Friction Reduction\n\n### At the Form Level\n- \"No credit card required\" (if true)\n- \"Free forever\" or \"14-day free trial\"\n- Privacy note: \"We'll never share your email\"\n- Security badges if relevant\n- Testimonial near signup form\n\n### Error Handling\n- Inline validation (not just on submit)\n- Specific error messages (\"Email already registered\" + recovery path)\n- Don't clear the form on error\n- Focus on the problem field\n\n### Microcopy\n- Placeholder text: Use for examples, not labels\n- Labels: Always visible (not just placeholders)\n- Help text: Only when needed, placed close to field\n\n---\n\n## Mobile Signup Optimization\n\n- Larger touch targets (44px+ height)\n- Appropriate keyboard types (email, tel, etc.)\n- Autofill support\n- Reduce typing (social auth, pre-fill)\n- Single column layout\n- Sticky CTA button\n- Test with actual devices\n\n---\n\n## Post-Submit Experience\n\n### Success State\n- Clear confirmation\n- Immediate next step\n- If email verification required:\n  - Explain what to do\n  - Easy resend option\n  - Check spam reminder\n  - Option to change email if wrong\n\n### Verification Flows\n- Consider delaying verification until necessary\n- Magic link as alternative to password\n- Let users explore while awaiting verification\n- Clear re-engagement if verification stalls\n\n---\n\n## Measurement\n\n### Key Metrics\n- Form start rate (landed → started filling)\n- Form completion rate (started → submitted)\n- Field-level drop-off (which fields lose people)\n- Time to complete\n- Error rate by field\n- Mobile vs. desktop completion\n\n### What to Track\n- Each field interaction (focus, blur, error)\n- Step progression in multi-step\n- Social auth vs. email signup ratio\n- Time between steps\n\n---\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## Questions to Ask\n\nIf you need more context:\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**: For optimizing what happens after signup\n- **form-cro**: For non-signup forms (lead capture, contact)\n- **page-cro**: For the landing page leading to signup\n- **ab-test-setup**: For testing signup flow changes\n",{"name":5,"description":7},"main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fbusiness-marketing\u002Fsignup-flow-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":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add davila7\u002Fclaude-code-templates --skill signup-flow-cro",{"tool":61,"command":62},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill signup-flow-cro",{"tool":64,"command":65},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill signup-flow-cro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fbusiness-marketing\u002Fsignup-flow-cro\u002FSKILL.md",true,[69],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"resources\u002Fimplementation-playbook.md","REFERENCE","参考文档",11944,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdebugging-strategies\u002Fresources\u002Fimplementation-playbook.md",[76,104,131,164,199,223],{"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":87,"publishedAt":40},"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",[82],{"categoryNo":83,"categoryName":84,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[88,89,90,91,92,28,93,94,38,25,27,95,96,97,98,99,100,101,102,103],"scoring","pool","wealthville pool scoring","liquidity","which","exit","now","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":111,"publishedAt":40},"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",[110],{"categoryNo":83,"categoryName":84,"taxonomyType":85,"taxonomyTypeDesc":86},[112,113,114,115,116,117,118,119,120,121,122,25,123,124,125,126,127,128,129,130],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":146,"publishedAt":40},"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",[137,140,141],{"categoryNo":138,"categoryName":139,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":83,"categoryName":84,"taxonomyType":85,"taxonomyTypeDesc":86},{"categoryNo":142,"categoryName":143,"taxonomyType":144,"taxonomyTypeDesc":145},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[147,148,149,150,151,152,153,28,154,155,156,157,158,159,160,38,161,162,25,163],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":168,"licenseFileUrl":169,"sourceHtmlUrl":170,"categories":171,"keywords":175,"publishedAt":40},"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",[172],{"categoryNo":173,"categoryName":174,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000009","前端开发",[176,177,178,179,180,181,182,183,184,185,186,187,188,189,190,191,192,193,194,195,196,197,28,198],"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":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":168,"licenseFileUrl":203,"sourceHtmlUrl":204,"categories":205,"keywords":210,"publishedAt":40},"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",[206,209],{"categoryNo":207,"categoryName":208,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":173,"categoryName":174,"taxonomyType":85,"taxonomyTypeDesc":86},[211,212,213,214,215,177,216,186,187,217,218,219,220,28,221,95,222],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":224,"name":225,"nameZh":6,"description":226,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":168,"licenseFileUrl":227,"sourceHtmlUrl":228,"categories":229,"keywords":237,"publishedAt":40},"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",[230,233,234],{"categoryNo":231,"categoryName":232,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":83,"categoryName":84,"taxonomyType":85,"taxonomyTypeDesc":86},{"categoryNo":235,"categoryName":236,"taxonomyType":144,"taxonomyTypeDesc":145},"01JBSEEDCAT000000000000036","内容创作者",[238,239,240,241,242,243,244,245,179,246,189,123,247,248,249,250,251,159,252,25,253,254,255,256,257,101,258],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]