[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AE4SG6NMHC55HARNF771W7":3,"skill-same:01M6AE4SG6NMHC55HARNF771W7":73},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M6AE4SG6NMHC55HARNF771W7","resume-ats-optimizer",null,"Optimize resumes for Applicant Tracking Systems, check ATS compatibility, and analyze keyword match. Use when the user mentions ATS, applicant tracking, keyword optimization, parsing, or getting past resume screening software.","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\u002Fcareer\u002Fresume-ats-optimizer\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"resume ats optimizer","ats","resume","optimizer","optimize","when","for","past","screening","match","software","systems","resume screening","compatibility","use","tracking","check","analyze","parsing","Optimization","2026-11-10 10:12:30",false,"---\nname: resume-ats-optimizer\ndescription: Optimize resumes for Applicant Tracking Systems, check ATS compatibility, and analyze keyword match. Use when the user mentions ATS, applicant tracking, keyword optimization, parsing, or getting past resume screening software.\n---\n\n# Resume ATS Optimizer\n\n## When to Use This Skill\n\nUse this skill when the user wants to:\n- Optimize their resume for Applicant Tracking Systems (ATS)\n- Check if their resume will pass automated screening\n- Understand why their applications aren't getting responses\n- Mentions keywords like: \"ATS\", \"not getting interviews\", \"resume not working\", \"optimize resume\", \"keyword optimization\"\n\nAlso use when the user provides a resume file and mentions they're applying to jobs.\n\n## Core Capabilities\n\n- Parse resume and test ATS compatibility\n- Extract and analyze keywords against job descriptions\n- Identify formatting issues that break ATS parsers\n- Calculate match scores between resume and job postings\n- Suggest keyword additions and placements\n- Generate ATS-friendly formatting recommendations\n\n## The ATS Problem\n\n75% of resumes are rejected by Applicant Tracking Systems before a human ever sees them. Companies use ATS to:\n- Filter out unqualified candidates automatically\n- Search for specific keywords from job requirements\n- Parse resumes into structured data\n- Rank candidates by keyword match percentage\n\nCommon reasons resumes fail ATS:\n1. Poor formatting (tables, columns, headers\u002Ffooters)\n2. Missing keywords from job description\n3. Inconsistent section headers\n4. Non-standard fonts or special characters\n5. Text embedded in images\n6. Incorrect file format\n\n## ATS Compatibility Checklist\n\n### File Format\n- ✅ Use .docx or .pdf (not .pages, .odt)\n- ✅ PDF must be text-based, not scanned image\n- ✅ File name: \"FirstName_LastName_Resume.pdf\"\n\n### Font & Formatting\n- ✅ Standard fonts: Arial, Calibri, Georgia, Times New Roman\n- ✅ Font size: 10-12pt for body, 14-16pt for headers\n- ✅ No text boxes, tables, or columns\n- ✅ No headers\u002Ffooters (put contact info in body)\n- ✅ No images, graphics, or charts\n- ✅ Consistent date formats (MM\u002FYYYY)\n- ✅ Standard bullet points (•, -, *)\n\n### Section Headers\nUse standard, recognizable headers:\n- ✅ \"Professional Experience\" or \"Work Experience\" (not \"Where I've Been\")\n- ✅ \"Education\" (not \"Academic Background\")\n- ✅ \"Skills\" (not \"Core Competencies\")\n- ✅ \"Summary\" or \"Professional Summary\"\n\n### Contact Information\n```\nJohn Smith\nemail@example.com | (555) 123-4567 | LinkedIn: linkedin.com\u002Fin\u002Fjohnsmith\nSan Francisco, CA\n```\n\nNOT in header\u002Ffooter, and avoid:\n- ❌ Tables for contact info\n- ❌ Special characters in email\n- ❌ Multiple phone numbers\n- ❌ Full mailing address (city\u002Fstate is enough)\n\n## Keyword Optimization Process\n\n### Step 1: Extract Job Description Keywords\n\nIdentify three types of keywords:\n\n**Hard Skills (Technical)**\n- Programming languages (Python, Java, SQL)\n- Tools and platforms (Salesforce, AWS, Excel)\n- Certifications (PMP, CPA, CFA)\n- Methodologies (Agile, Six Sigma, SDLC)\n\n**Soft Skills**\n- Leadership, collaboration, communication\n- Problem-solving, analytical thinking\n- Project management, stakeholder management\n\n**Industry Terms**\n- B2B, SaaS, e-commerce\n- Enterprise, SMB, mid-market\n- ARR, MRR, churn rate\n\n### Step 2: Match Analysis\n\nFor each keyword in job description:\n1. Check if exact phrase appears in resume\n2. Check for synonyms or variations\n3. Count frequency of mention\n4. Note location (summary, experience, skills)\n\n### Step 3: Calculate Match Score\n\n```\nMatch Score = (Keywords Matched \u002F Total Required Keywords) × 100\n\nExample:\nJob has 20 required keywords\nYour resume has 15 of them\nMatch Score = 75%\n\nTarget: 80%+ for strong match\n```\n\n### Step 4: Keyword Placement Strategy\n\n**Priority 1: Professional Summary (Top of Resume)**\n- Include 5-8 most important keywords\n- Use naturally in 3-4 sentence paragraph\n- Example: \"Data Scientist with 5+ years using Python, SQL, and machine learning to drive business insights...\"\n\n**Priority 2: Skills Section**\n- List keywords explicitly\n- Group by category if needed\n- Use exact phrasing from job description\n\n**Priority 3: Experience Bullets**\n- Incorporate keywords into achievement statements\n- Don't force keywords unnaturally\n- Use variations throughout\n\n**Keyword Density Guidelines:**\n- Critical keywords: Appear 2-4 times throughout resume\n- Important keywords: Appear 1-2 times\n- Don't keyword stuff - keep it natural\n- Vary phrasing (e.g., \"led team\" and \"team leadership\")\n\n## Analysis Output Format\n\nWhen analyzing a resume, provide this structured report:\n\n```markdown\n# ATS COMPATIBILITY REPORT\n\n## Overall Score: [X]\u002F100\n\n### File Format Check ✅\u002F❌\n- Format: [DOCX\u002FPDF]\n- Text extraction: [Success\u002FFailed]\n- File size: [X KB\u002FMB]\n\n### Formatting Issues\n✅ No tables or columns detected\n❌ Contact info in header (move to body)\n⚠️  Two different font sizes in skills section\n\n### Keyword Analysis\n\nJOB REQUIREMENTS vs YOUR RESUME:\n\n**Critical Keywords (Must Have):**\n✅ Project Management - Found 3x\n✅ Agile\u002FScrum - Found 2x\n❌ Stakeholder Management - MISSING (mentioned 5x in JD)\n❌ Budget Management - MISSING (mentioned 3x in JD)\n\n**Important Keywords:**\n✅ Cross-functional teams - Found 1x\n⚠️  \"Risk management\" - You have \"risk mitigation\" (close but not exact match)\n✅ Process improvement - Found 2x\n\n**Match Score: 65%**\nTarget: 80%+ recommended\n\n### Recommended Changes\n\n**1. Add Missing Keywords:**\n\nIn Professional Summary, change:\n\"Experienced project manager with proven track record...\"\n\nTo:\n\"Experienced project manager with proven track record in stakeholder management and budget oversight...\"\n\nIn Experience section, add bullet:\n\"Managed stakeholder communication across 3 departments and executive leadership team\"\n\"Directed budget management for $2.5M project portfolio\"\n\n**2. Fix Formatting:**\n- Move contact information from header to body of resume\n- Make all skill section items same font size (currently 10pt and 11pt mixed)\n\n**3. Strengthen Existing Keywords:**\nChange \"risk mitigation\" to \"risk management\" for exact match\n\n### Estimated New Match Score: 85%\n```\n\n## Common ATS Failure Patterns\n\n### Pattern 1: Creative Formatting\n```\n❌ PROBLEM:\n[Two-column layout with graphics]\n[Skill bars and proficiency charts]\n[Text in colored boxes]\n\n✅ SOLUTION:\n- Single column layout\n- Text-only skills list\n- Simple bullet points\n```\n\n### Pattern 2: Unconventional Section Names\n```\n❌ PROBLEM:\n\"My Journey\" (instead of Experience)\n\"What I Bring to the Table\" (instead of Skills)\n\"Academic Pursuits\" (instead of Education)\n\n✅ SOLUTION:\nUse standard headers ATS recognizes\n```\n\n### Pattern 3: Missing Keywords\n```\n❌ PROBLEM:\nJob requires: \"Python, SQL, Data Visualization\"\nResume says: \"Programming, databases, making charts\"\n\n✅ SOLUTION:\nUse exact terminology from job description\n```\n\n### Pattern 4: Keyword Stuffing\n```\n❌ PROBLEM:\nSkills: Python, Python programming, Python developer, Python expert, Python specialist, Advanced Python...\n\n✅ SOLUTION:\nSkills: Python, SQL, JavaScript, React, Node.js\n(Then incorporate naturally in bullets)\n```\n\n## Industry-Specific Considerations\n\n### Tech Resumes\n- Emphasize programming languages and frameworks\n- Include GitHub, portfolio links in Skills section (not header)\n- Certifications and courses matter highly\n\n### Business\u002FFinance\n- Focus on software proficiency (Excel, SAP, Salesforce)\n- Certifications critical (CPA, CFA, PMP)\n- Industry keywords (P&L, ROI, KPI)\n\n### Healthcare\n- Licenses and certifications required\n- Specific systems (Epic, Cerner, MEDITECH)\n- Compliance keywords (HIPAA, Joint Commission)\n\n### Marketing\n- Platform expertise (HubSpot, Salesforce, Google Analytics)\n- Channel keywords (SEO, PPC, email marketing)\n- Metrics and results-driven language\n\n## Edge Cases & Special Situations\n\n### Career Changers\n- Focus on transferable skills\n- Use keywords from TARGET industry, not just current\n- May need two resume versions for ATS\n\n### Recent Graduates\n- Education section becomes priority for keywords\n- Include relevant coursework, projects\n- Internships count as experience - use those keywords\n\n### Executive Level\n- ATS still matters for senior roles\n- Focus on strategic keywords\n- Include board experience, P&L size, team size\n\n### Gaps in Employment\n- Use years only (not months) if it helps\n- Include freelance\u002Fconsulting with keywords\n- Volunteer work can include relevant keywords\n\n## Implementation Checklist\n\nWhen helping user optimize for ATS:\n\n1. ✅ Scan current resume for ATS compatibility issues\n2. ✅ Analyze job description for required keywords\n3. ✅ Calculate current match score\n4. ✅ Identify specific missing keywords\n5. ✅ Suggest exact placements for new keywords\n6. ✅ Flag formatting problems\n7. ✅ Provide before\u002Fafter examples\n8. ✅ Re-score after suggested changes\n9. ✅ Verify file format and naming\n10. ✅ Test with ATS simulator if possible\n\n## Success Metrics\n\nAfter optimization, the resume should:\n- Score 80%+ match for target job descriptions\n- Pass ATS parsing test (all sections recognized)\n- Have zero formatting errors\n- Include all critical keywords 2-4x each\n- Read naturally (not keyword-stuffed)\n- Be ready to submit immediately\n","# Resume ATS Optimizer\n\n## When to Use This Skill\n\nUse this skill when the user wants to:\n- Optimize their resume for Applicant Tracking Systems (ATS)\n- Check if their resume will pass automated screening\n- Understand why their applications aren't getting responses\n- Mentions keywords like: \"ATS\", \"not getting interviews\", \"resume not working\", \"optimize resume\", \"keyword optimization\"\n\nAlso use when the user provides a resume file and mentions they're applying to jobs.\n\n## Core Capabilities\n\n- Parse resume and test ATS compatibility\n- Extract and analyze keywords against job descriptions\n- Identify formatting issues that break ATS parsers\n- Calculate match scores between resume and job postings\n- Suggest keyword additions and placements\n- Generate ATS-friendly formatting recommendations\n\n## The ATS Problem\n\n75% of resumes are rejected by Applicant Tracking Systems before a human ever sees them. Companies use ATS to:\n- Filter out unqualified candidates automatically\n- Search for specific keywords from job requirements\n- Parse resumes into structured data\n- Rank candidates by keyword match percentage\n\nCommon reasons resumes fail ATS:\n1. Poor formatting (tables, columns, headers\u002Ffooters)\n2. Missing keywords from job description\n3. Inconsistent section headers\n4. Non-standard fonts or special characters\n5. Text embedded in images\n6. Incorrect file format\n\n## ATS Compatibility Checklist\n\n### File Format\n- ✅ Use .docx or .pdf (not .pages, .odt)\n- ✅ PDF must be text-based, not scanned image\n- ✅ File name: \"FirstName_LastName_Resume.pdf\"\n\n### Font & Formatting\n- ✅ Standard fonts: Arial, Calibri, Georgia, Times New Roman\n- ✅ Font size: 10-12pt for body, 14-16pt for headers\n- ✅ No text boxes, tables, or columns\n- ✅ No headers\u002Ffooters (put contact info in body)\n- ✅ No images, graphics, or charts\n- ✅ Consistent date formats (MM\u002FYYYY)\n- ✅ Standard bullet points (•, -, *)\n\n### Section Headers\nUse standard, recognizable headers:\n- ✅ \"Professional Experience\" or \"Work Experience\" (not \"Where I've Been\")\n- ✅ \"Education\" (not \"Academic Background\")\n- ✅ \"Skills\" (not \"Core Competencies\")\n- ✅ \"Summary\" or \"Professional Summary\"\n\n### Contact Information\n```\nJohn Smith\nemail@example.com | (555) 123-4567 | LinkedIn: linkedin.com\u002Fin\u002Fjohnsmith\nSan Francisco, CA\n```\n\nNOT in header\u002Ffooter, and avoid:\n- ❌ Tables for contact info\n- ❌ Special characters in email\n- ❌ Multiple phone numbers\n- ❌ Full mailing address (city\u002Fstate is enough)\n\n## Keyword Optimization Process\n\n### Step 1: Extract Job Description Keywords\n\nIdentify three types of keywords:\n\n**Hard Skills (Technical)**\n- Programming languages (Python, Java, SQL)\n- Tools and platforms (Salesforce, AWS, Excel)\n- Certifications (PMP, CPA, CFA)\n- Methodologies (Agile, Six Sigma, SDLC)\n\n**Soft Skills**\n- Leadership, collaboration, communication\n- Problem-solving, analytical thinking\n- Project management, stakeholder management\n\n**Industry Terms**\n- B2B, SaaS, e-commerce\n- Enterprise, SMB, mid-market\n- ARR, MRR, churn rate\n\n### Step 2: Match Analysis\n\nFor each keyword in job description:\n1. Check if exact phrase appears in resume\n2. Check for synonyms or variations\n3. Count frequency of mention\n4. Note location (summary, experience, skills)\n\n### Step 3: Calculate Match Score\n\n```\nMatch Score = (Keywords Matched \u002F Total Required Keywords) × 100\n\nExample:\nJob has 20 required keywords\nYour resume has 15 of them\nMatch Score = 75%\n\nTarget: 80%+ for strong match\n```\n\n### Step 4: Keyword Placement Strategy\n\n**Priority 1: Professional Summary (Top of Resume)**\n- Include 5-8 most important keywords\n- Use naturally in 3-4 sentence paragraph\n- Example: \"Data Scientist with 5+ years using Python, SQL, and machine learning to drive business insights...\"\n\n**Priority 2: Skills Section**\n- List keywords explicitly\n- Group by category if needed\n- Use exact phrasing from job description\n\n**Priority 3: Experience Bullets**\n- Incorporate keywords into achievement statements\n- Don't force keywords unnaturally\n- Use variations throughout\n\n**Keyword Density Guidelines:**\n- Critical keywords: Appear 2-4 times throughout resume\n- Important keywords: Appear 1-2 times\n- Don't keyword stuff - keep it natural\n- Vary phrasing (e.g., \"led team\" and \"team leadership\")\n\n## Analysis Output Format\n\nWhen analyzing a resume, provide this structured report:\n\n```markdown\n# ATS COMPATIBILITY REPORT\n\n## Overall Score: [X]\u002F100\n\n### File Format Check ✅\u002F❌\n- Format: [DOCX\u002FPDF]\n- Text extraction: [Success\u002FFailed]\n- File size: [X KB\u002FMB]\n\n### Formatting Issues\n✅ No tables or columns detected\n❌ Contact info in header (move to body)\n⚠️  Two different font sizes in skills section\n\n### Keyword Analysis\n\nJOB REQUIREMENTS vs YOUR RESUME:\n\n**Critical Keywords (Must Have):**\n✅ Project Management - Found 3x\n✅ Agile\u002FScrum - Found 2x\n❌ Stakeholder Management - MISSING (mentioned 5x in JD)\n❌ Budget Management - MISSING (mentioned 3x in JD)\n\n**Important Keywords:**\n✅ Cross-functional teams - Found 1x\n⚠️  \"Risk management\" - You have \"risk mitigation\" (close but not exact match)\n✅ Process improvement - Found 2x\n\n**Match Score: 65%**\nTarget: 80%+ recommended\n\n### Recommended Changes\n\n**1. Add Missing Keywords:**\n\nIn Professional Summary, change:\n\"Experienced project manager with proven track record...\"\n\nTo:\n\"Experienced project manager with proven track record in stakeholder management and budget oversight...\"\n\nIn Experience section, add bullet:\n\"Managed stakeholder communication across 3 departments and executive leadership team\"\n\"Directed budget management for $2.5M project portfolio\"\n\n**2. Fix Formatting:**\n- Move contact information from header to body of resume\n- Make all skill section items same font size (currently 10pt and 11pt mixed)\n\n**3. Strengthen Existing Keywords:**\nChange \"risk mitigation\" to \"risk management\" for exact match\n\n### Estimated New Match Score: 85%\n```\n\n## Common ATS Failure Patterns\n\n### Pattern 1: Creative Formatting\n```\n❌ PROBLEM:\n[Two-column layout with graphics]\n[Skill bars and proficiency charts]\n[Text in colored boxes]\n\n✅ SOLUTION:\n- Single column layout\n- Text-only skills list\n- Simple bullet points\n```\n\n### Pattern 2: Unconventional Section Names\n```\n❌ PROBLEM:\n\"My Journey\" (instead of Experience)\n\"What I Bring to the Table\" (instead of Skills)\n\"Academic Pursuits\" (instead of Education)\n\n✅ SOLUTION:\nUse standard headers ATS recognizes\n```\n\n### Pattern 3: Missing Keywords\n```\n❌ PROBLEM:\nJob requires: \"Python, SQL, Data Visualization\"\nResume says: \"Programming, databases, making charts\"\n\n✅ SOLUTION:\nUse exact terminology from job description\n```\n\n### Pattern 4: Keyword Stuffing\n```\n❌ PROBLEM:\nSkills: Python, Python programming, Python developer, Python expert, Python specialist, Advanced Python...\n\n✅ SOLUTION:\nSkills: Python, SQL, JavaScript, React, Node.js\n(Then incorporate naturally in bullets)\n```\n\n## Industry-Specific Considerations\n\n### Tech Resumes\n- Emphasize programming languages and frameworks\n- Include GitHub, portfolio links in Skills section (not header)\n- Certifications and courses matter highly\n\n### Business\u002FFinance\n- Focus on software proficiency (Excel, SAP, Salesforce)\n- Certifications critical (CPA, CFA, PMP)\n- Industry keywords (P&L, ROI, KPI)\n\n### Healthcare\n- Licenses and certifications required\n- Specific systems (Epic, Cerner, MEDITECH)\n- Compliance keywords (HIPAA, Joint Commission)\n\n### Marketing\n- Platform expertise (HubSpot, Salesforce, Google Analytics)\n- Channel keywords (SEO, PPC, email marketing)\n- Metrics and results-driven language\n\n## Edge Cases & Special Situations\n\n### Career Changers\n- Focus on transferable skills\n- Use keywords from TARGET industry, not just current\n- May need two resume versions for ATS\n\n### Recent Graduates\n- Education section becomes priority for keywords\n- Include relevant coursework, projects\n- Internships count as experience - use those keywords\n\n### Executive Level\n- ATS still matters for senior roles\n- Focus on strategic keywords\n- Include board experience, P&L size, team size\n\n### Gaps in Employment\n- Use years only (not months) if it helps\n- Include freelance\u002Fconsulting with keywords\n- Volunteer work can include relevant keywords\n\n## Implementation Checklist\n\nWhen helping user optimize for ATS:\n\n1. ✅ Scan current resume for ATS compatibility issues\n2. ✅ Analyze job description for required keywords\n3. ✅ Calculate current match score\n4. ✅ Identify specific missing keywords\n5. ✅ Suggest exact placements for new keywords\n6. ✅ Flag formatting problems\n7. ✅ Provide before\u002Fafter examples\n8. ✅ Re-score after suggested changes\n9. ✅ Verify file format and naming\n10. ✅ Test with ATS simulator if possible\n\n## Success Metrics\n\nAfter optimization, the resume should:\n- Score 80%+ match for target job descriptions\n- Pass ATS parsing test (all sections recognized)\n- Have zero formatting errors\n- Include all critical keywords 2-4x each\n- Read naturally (not keyword-stuffed)\n- Be ready to submit immediately\n",{"name":5,"description":7},"main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fcareer\u002Fresume-ats-optimizer",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":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add davila7\u002Fclaude-code-templates --skill resume-ats-optimizer",{"tool":65,"command":66},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill resume-ats-optimizer",{"tool":68,"command":69},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill resume-ats-optimizer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcareer\u002Fresume-ats-optimizer\u002FSKILL.md",true,[],[74,103,130,161,196,220],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":85,"publishedAt":44},"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",[80],{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[86,87,88,89,90,30,91,92,38,29,93,94,95,96,97,98,99,100,101,102],"scoring","pool","wealthville pool scoring","liquidity","which","exit","now","reduce","with","record","track","verdict","evm","solana","how","public","look",{"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":110,"publishedAt":44},"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",[109],{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},[111,112,113,114,115,116,117,118,119,120,121,29,122,123,124,125,126,127,128,129],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":143,"publishedAt":44},"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",[136,139,140],{"categoryNo":137,"categoryName":138,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},{"categoryNo":141,"categoryName":142,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000033","数据分析师",[144,145,146,147,148,149,150,30,151,152,153,154,155,156,157,38,158,159,29,160],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":165,"licenseFileUrl":166,"sourceHtmlUrl":167,"categories":168,"keywords":172,"publishedAt":44},"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",[169],{"categoryNo":170,"categoryName":171,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000009","前端开发",[173,174,175,176,177,178,179,180,181,182,183,184,185,186,187,188,189,190,191,192,193,194,30,195],"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":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":165,"licenseFileUrl":200,"sourceHtmlUrl":201,"categories":202,"keywords":207,"publishedAt":44},"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",[203,206],{"categoryNo":204,"categoryName":205,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":170,"categoryName":171,"taxonomyType":83,"taxonomyTypeDesc":84},[208,209,210,211,212,174,213,183,184,214,215,216,217,30,218,94,219],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":221,"name":222,"nameZh":6,"description":223,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":165,"licenseFileUrl":224,"sourceHtmlUrl":225,"categories":226,"keywords":234,"publishedAt":44},"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",[227,230,231],{"categoryNo":228,"categoryName":229,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},{"categoryNo":232,"categoryName":233,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000036","内容创作者",[235,236,237,238,239,240,241,242,176,243,186,122,244,245,246,247,248,156,249,29,250,251,252,253,254,100,255],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]