[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AE55JJ8JAD0P9RZDR4J4KR":3,"skill-same:01M6AE55JJ8JAD0P9RZDR4J4KR":62},{"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":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":38,"commitSha":39,"skillDirectory":40,"forksCount":41,"repositoryHtmlUrl":42,"repositoryHomepageUrl":43,"ownerHtmlUrl":44,"ownerBlogUrl":45,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M6AE55JJ8JAD0P9RZDR4J4KR","resume-tailor",null,"Customize resume for specific job postings while maintaining truthfulness. Use when the user wants to tailor, customize, or target their resume for a specific job, company, or role.","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-tailor\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32],"resume tailor","resume","customize","user","use","role","for","company","when","2026-11-10 10:12:30",false,"---\nname: resume-tailor\ndescription: Customize resume for specific job postings while maintaining truthfulness. Use when the user wants to tailor, customize, or target their resume for a specific job, company, or role.\n---\n\n# Resume Tailor\n\n## When to Use This Skill\n\nUse this skill when the user wants to:\n- Customize their resume for a specific job posting\n- Adjust their resume to match job requirements\n- Create a targeted version of their resume\n- Mentions: \"tailor resume\", \"customize resume\", \"target role\", \"specific job\", \"match job description\"\n\nUse AFTER job-description-analyzer to know what to emphasize.\n\n## Core Capabilities\n\n- Reorder experience sections by relevance to target role\n- Adjust professional summary for specific position\n- Add missing keywords from job description\n- Modify bullet points to match job requirements\n- Maintain authenticity while optimizing match\n- Create multiple targeted resume versions\n\n## The Tailoring Philosophy\n\n**Key Principle:** You're not lying or fabricating - you're HIGHLIGHTING the most relevant parts of your true experience.\n\nThink of your full experience as a library of achievements. Tailoring means selecting the books that best fit what each employer is looking for.\n\n## Tailoring Process\n\n### Step 1: Analyze the Job (Use Job Description Analyzer First)\n- Identify required skills and keywords\n- Note the company's priorities\n- Understand the role's primary responsibilities\n\n### Step 2: Audit Your Resume\nFor each section, ask:\n- Does this support my candidacy for THIS specific role?\n- Is there a better way to phrase this for THIS job?\n- Should this be higher or lower in priority?\n\n### Step 3: Make Strategic Adjustments\n\n**Professional Summary:** Rewrite to mirror the job's key requirements\n\n**Skills Section:** Reorder to put most relevant skills first, add missing keywords\n\n**Experience:** \n- Reorder jobs if a less recent role is more relevant\n- Swap bullet points to lead with most relevant achievements\n- Add keywords naturally into existing bullets\n\n**Education:** Highlight relevant coursework, certifications\n\n## Section-by-Section Tailoring Guide\n\n### Professional Summary\n\nThis is your \"elevator pitch\" - customize for each application.\n\n**Generic Summary (AVOID):**\n```\nResults-driven professional with 5 years of experience in business operations. Strong analytical and communication skills. Looking for a challenging opportunity to grow.\n```\n\n**Tailored for Operations Manager Role:**\n```\nOperations Manager with 5 years optimizing supply chain processes and reducing costs by 25%. Expertise in Lean Six Sigma, vendor management, and cross-functional team leadership. Track record of improving operational efficiency while maintaining quality standards.\n```\n\n**Tailored for Project Manager Role (Same Person):**\n```\nProject Manager with 5 years leading cross-functional initiatives from concept to delivery. PMP-certified with expertise in Agile methodology, stakeholder management, and budget oversight. Track record of on-time, under-budget project delivery across $10M+ portfolios.\n```\n\n### Skills Section Reordering\n\n**Job Description Emphasizes:** Data analysis, SQL, Python, stakeholder communication\n\n**Before (Generic Order):**\n```\nSkills: Microsoft Office, Communication, Project Management, Python, SQL, Data Visualization, Leadership\n```\n\n**After (Tailored Order):**\n```\nSkills: SQL, Python, Data Analysis, Data Visualization, Stakeholder Communication, Project Management, Microsoft Office\n```\n\n### Experience Section\n\n**Strategy 1: Reorder Jobs**\n\nIf your most recent job is less relevant than a previous role:\n\n**Before:**\n1. Marketing Coordinator (current, but applying for data role)\n2. Data Analyst (previous, highly relevant)\n\n**After:**\n1. Data Analyst (labeled with dates, moved up)\n2. Marketing Coordinator (still included, but secondary)\n\n**Strategy 2: Swap Bullet Order**\n\nLead with bullets most relevant to the target role.\n\n**Applying for Management Role - Lead with:**\n- \"Led team of 12...\"\n- \"Managed budget of $2M...\"\n\n**Applying for Technical Role - Lead with:**\n- \"Developed automated system...\"\n- \"Analyzed 500K+ data points...\"\n\n**Strategy 3: Adjust Bullet Language**\n\nIncorporate job description keywords while staying truthful.\n\n**Job Description Says:** \"stakeholder management\"\n**Your Bullet Says:** \"Worked with various teams\"\n**Tailored Version:** \"Managed stakeholder relationships across 5 departments, ensuring alignment on project priorities\"\n\n## Tailoring Templates\n\n### For Each Job Application, Create:\n\n```markdown\n## RESUME TAILORING PLAN\n\n**Target Position:** [Job Title]\n**Company:** [Company Name]\n**Match Score:** [From JD Analyzer]\n\n### Summary Customization\n**Current:** [Your current summary]\n**Tailored:** [Rewritten for this role]\n\n### Skills Reordering\n**Current Order:** [List]\n**New Order:** [Reordered list with added keywords]\n**Keywords Added:** [New skills from JD]\n\n### Experience Adjustments\n\n**Job 1: [Title]**\n- Bullet to emphasize: [Which bullet to lead with]\n- Keyword to add: [What phrase to incorporate]\n- Bullet to de-emphasize: [Move down or remove if space needed]\n\n**Job 2: [Title]**\n[Same structure]\n\n### Other Adjustments\n- Education: [Any relevant coursework to add]\n- Certifications: [Any to highlight]\n- Projects: [Relevant projects to include]\n```\n\n## Common Tailoring Scenarios\n\n### Scenario 1: Technical Role at Non-Tech Company\n\n**Challenge:** They want technical skills but also business acumen\n\n**Strategy:**\n- Lead with technical achievements\n- Include business impact in every technical bullet\n- Add \"translated technical concepts for business stakeholders\"\n\n### Scenario 2: Management Role (But You've Done Both IC and Management)\n\n**Challenge:** Show leadership without abandoning technical credibility\n\n**Strategy:**\n- Summary: Emphasize leadership\n- Experience: Lead with team management bullets\n- Keep some technical bullets to show you understand the work\n\n### Scenario 3: Startup (But You've Worked at Big Companies)\n\n**Challenge:** Show you can thrive in ambiguity and wear many hats\n\n**Strategy:**\n- Highlight cross-functional work\n- Emphasize initiative and self-starting\n- Show scrappy, creative problem-solving\n- De-emphasize rigid processes and large team structures\n\n### Scenario 4: Big Company (But You've Worked at Startups)\n\n**Challenge:** Show you can work within structure and at scale\n\n**Strategy:**\n- Emphasize process improvement\n- Highlight work that scaled\n- Show collaboration across teams\n- Add metrics that show impact at scale\n\n## Keyword Integration Rules\n\n### DO:\n- Add keywords that truthfully describe your work\n- Use exact phrasing from job description when accurate\n- Place keywords naturally in context\n- Include keywords in multiple locations (summary, skills, experience)\n\n### DON'T:\n- Add skills you don't actually have\n- Keyword stuff (repeating same term 10x)\n- Create a different meaning than your actual experience\n- Sacrifice readability for keyword density\n\n## Truth vs. Tailoring Line\n\n**Acceptable Tailoring:**\n- Reordering true information\n- Emphasizing relevant experience\n- Using industry-standard terminology\n- Adding context to vague statements\n- Matching language style to job description\n\n**Unacceptable (Lying):**\n- Adding skills you don't have\n- Changing numbers or metrics\n- Creating fake experiences\n- Claiming titles you didn't hold\n- Stating certifications you don't have\n\n## Version Management\n\n### Maintain a Master Resume\n- Keep ONE complete document with ALL experiences\n- Include every bullet you've ever written\n- This is your \"source of truth\"\n\n### Create Targeted Versions\n- Name files clearly: \"JohnSmith_Resume_ProductManager_TechCorp.pdf\"\n- Track which version went to which company\n- Save tailoring notes for interview prep\n\n### Version Naming Convention\n```\n[LastName]_Resume_[TargetRole]_[Company]_[Date].pdf\n\nExamples:\n- Smith_Resume_PM_Google_Jan2024.pdf\n- Smith_Resume_DataAnalyst_Meta_Jan2024.pdf\n- Smith_Resume_General_Master.docx (your master file)\n```\n\n## Quick Tailoring Checklist\n\nBefore submitting any resume:\n\n1. ✅ Summary mentions the exact job title\u002Ffunction\n2. ✅ Top 5 skills match job description's top 5 requirements\n3. ✅ Most relevant experience is positioned first\n4. ✅ Each job's top bullet addresses job's key requirement\n5. ✅ Keywords from JD appear naturally throughout\n6. ✅ Company\u002Findustry terminology is used correctly\n7. ✅ All claims are truthful\n8. ✅ File is named appropriately\n9. ✅ ATS formatting maintained\n10. ✅ Saved for interview prep reference\n\n## Output Format\n\nWhen tailoring a resume, provide:\n\n```markdown\n# TAILORED RESUME CHANGES\n\n## Target: [Job Title] at [Company]\n\n### Professional Summary\n**Before:** [Original]\n**After:** [Tailored version]\n**Keywords Added:** [List]\n\n### Skills Section\n**New Order:** [Reordered list]\n**Added:** [New keywords]\n**Removed:** [If any, for space]\n\n### Experience Changes\n\n**[Company Name] - [Title]**\n- Move bullet X to position 1\n- Modify bullet Y: [Before → After]\n- Add keyword \"[phrase]\" to bullet Z\n\n[Repeat for each relevant job]\n\n### Overall Changes Summary\n- Keywords added: X\n- Bullets modified: Y\n- Sections reordered: Yes\u002FNo\n- Estimated new match score: Z%\n```\n\n## Implementation Notes\n\n- Always start with the job description analyzer\n- Keep tailoring changes documented for interview prep\n- Maintain master resume as source of truth\n- Never sacrifice ATS compatibility for tailoring\n- Test keyword match after tailoring\n","# Resume Tailor\n\n## When to Use This Skill\n\nUse this skill when the user wants to:\n- Customize their resume for a specific job posting\n- Adjust their resume to match job requirements\n- Create a targeted version of their resume\n- Mentions: \"tailor resume\", \"customize resume\", \"target role\", \"specific job\", \"match job description\"\n\nUse AFTER job-description-analyzer to know what to emphasize.\n\n## Core Capabilities\n\n- Reorder experience sections by relevance to target role\n- Adjust professional summary for specific position\n- Add missing keywords from job description\n- Modify bullet points to match job requirements\n- Maintain authenticity while optimizing match\n- Create multiple targeted resume versions\n\n## The Tailoring Philosophy\n\n**Key Principle:** You're not lying or fabricating - you're HIGHLIGHTING the most relevant parts of your true experience.\n\nThink of your full experience as a library of achievements. Tailoring means selecting the books that best fit what each employer is looking for.\n\n## Tailoring Process\n\n### Step 1: Analyze the Job (Use Job Description Analyzer First)\n- Identify required skills and keywords\n- Note the company's priorities\n- Understand the role's primary responsibilities\n\n### Step 2: Audit Your Resume\nFor each section, ask:\n- Does this support my candidacy for THIS specific role?\n- Is there a better way to phrase this for THIS job?\n- Should this be higher or lower in priority?\n\n### Step 3: Make Strategic Adjustments\n\n**Professional Summary:** Rewrite to mirror the job's key requirements\n\n**Skills Section:** Reorder to put most relevant skills first, add missing keywords\n\n**Experience:** \n- Reorder jobs if a less recent role is more relevant\n- Swap bullet points to lead with most relevant achievements\n- Add keywords naturally into existing bullets\n\n**Education:** Highlight relevant coursework, certifications\n\n## Section-by-Section Tailoring Guide\n\n### Professional Summary\n\nThis is your \"elevator pitch\" - customize for each application.\n\n**Generic Summary (AVOID):**\n```\nResults-driven professional with 5 years of experience in business operations. Strong analytical and communication skills. Looking for a challenging opportunity to grow.\n```\n\n**Tailored for Operations Manager Role:**\n```\nOperations Manager with 5 years optimizing supply chain processes and reducing costs by 25%. Expertise in Lean Six Sigma, vendor management, and cross-functional team leadership. Track record of improving operational efficiency while maintaining quality standards.\n```\n\n**Tailored for Project Manager Role (Same Person):**\n```\nProject Manager with 5 years leading cross-functional initiatives from concept to delivery. PMP-certified with expertise in Agile methodology, stakeholder management, and budget oversight. Track record of on-time, under-budget project delivery across $10M+ portfolios.\n```\n\n### Skills Section Reordering\n\n**Job Description Emphasizes:** Data analysis, SQL, Python, stakeholder communication\n\n**Before (Generic Order):**\n```\nSkills: Microsoft Office, Communication, Project Management, Python, SQL, Data Visualization, Leadership\n```\n\n**After (Tailored Order):**\n```\nSkills: SQL, Python, Data Analysis, Data Visualization, Stakeholder Communication, Project Management, Microsoft Office\n```\n\n### Experience Section\n\n**Strategy 1: Reorder Jobs**\n\nIf your most recent job is less relevant than a previous role:\n\n**Before:**\n1. Marketing Coordinator (current, but applying for data role)\n2. Data Analyst (previous, highly relevant)\n\n**After:**\n1. Data Analyst (labeled with dates, moved up)\n2. Marketing Coordinator (still included, but secondary)\n\n**Strategy 2: Swap Bullet Order**\n\nLead with bullets most relevant to the target role.\n\n**Applying for Management Role - Lead with:**\n- \"Led team of 12...\"\n- \"Managed budget of $2M...\"\n\n**Applying for Technical Role - Lead with:**\n- \"Developed automated system...\"\n- \"Analyzed 500K+ data points...\"\n\n**Strategy 3: Adjust Bullet Language**\n\nIncorporate job description keywords while staying truthful.\n\n**Job Description Says:** \"stakeholder management\"\n**Your Bullet Says:** \"Worked with various teams\"\n**Tailored Version:** \"Managed stakeholder relationships across 5 departments, ensuring alignment on project priorities\"\n\n## Tailoring Templates\n\n### For Each Job Application, Create:\n\n```markdown\n## RESUME TAILORING PLAN\n\n**Target Position:** [Job Title]\n**Company:** [Company Name]\n**Match Score:** [From JD Analyzer]\n\n### Summary Customization\n**Current:** [Your current summary]\n**Tailored:** [Rewritten for this role]\n\n### Skills Reordering\n**Current Order:** [List]\n**New Order:** [Reordered list with added keywords]\n**Keywords Added:** [New skills from JD]\n\n### Experience Adjustments\n\n**Job 1: [Title]**\n- Bullet to emphasize: [Which bullet to lead with]\n- Keyword to add: [What phrase to incorporate]\n- Bullet to de-emphasize: [Move down or remove if space needed]\n\n**Job 2: [Title]**\n[Same structure]\n\n### Other Adjustments\n- Education: [Any relevant coursework to add]\n- Certifications: [Any to highlight]\n- Projects: [Relevant projects to include]\n```\n\n## Common Tailoring Scenarios\n\n### Scenario 1: Technical Role at Non-Tech Company\n\n**Challenge:** They want technical skills but also business acumen\n\n**Strategy:**\n- Lead with technical achievements\n- Include business impact in every technical bullet\n- Add \"translated technical concepts for business stakeholders\"\n\n### Scenario 2: Management Role (But You've Done Both IC and Management)\n\n**Challenge:** Show leadership without abandoning technical credibility\n\n**Strategy:**\n- Summary: Emphasize leadership\n- Experience: Lead with team management bullets\n- Keep some technical bullets to show you understand the work\n\n### Scenario 3: Startup (But You've Worked at Big Companies)\n\n**Challenge:** Show you can thrive in ambiguity and wear many hats\n\n**Strategy:**\n- Highlight cross-functional work\n- Emphasize initiative and self-starting\n- Show scrappy, creative problem-solving\n- De-emphasize rigid processes and large team structures\n\n### Scenario 4: Big Company (But You've Worked at Startups)\n\n**Challenge:** Show you can work within structure and at scale\n\n**Strategy:**\n- Emphasize process improvement\n- Highlight work that scaled\n- Show collaboration across teams\n- Add metrics that show impact at scale\n\n## Keyword Integration Rules\n\n### DO:\n- Add keywords that truthfully describe your work\n- Use exact phrasing from job description when accurate\n- Place keywords naturally in context\n- Include keywords in multiple locations (summary, skills, experience)\n\n### DON'T:\n- Add skills you don't actually have\n- Keyword stuff (repeating same term 10x)\n- Create a different meaning than your actual experience\n- Sacrifice readability for keyword density\n\n## Truth vs. Tailoring Line\n\n**Acceptable Tailoring:**\n- Reordering true information\n- Emphasizing relevant experience\n- Using industry-standard terminology\n- Adding context to vague statements\n- Matching language style to job description\n\n**Unacceptable (Lying):**\n- Adding skills you don't have\n- Changing numbers or metrics\n- Creating fake experiences\n- Claiming titles you didn't hold\n- Stating certifications you don't have\n\n## Version Management\n\n### Maintain a Master Resume\n- Keep ONE complete document with ALL experiences\n- Include every bullet you've ever written\n- This is your \"source of truth\"\n\n### Create Targeted Versions\n- Name files clearly: \"JohnSmith_Resume_ProductManager_TechCorp.pdf\"\n- Track which version went to which company\n- Save tailoring notes for interview prep\n\n### Version Naming Convention\n```\n[LastName]_Resume_[TargetRole]_[Company]_[Date].pdf\n\nExamples:\n- Smith_Resume_PM_Google_Jan2024.pdf\n- Smith_Resume_DataAnalyst_Meta_Jan2024.pdf\n- Smith_Resume_General_Master.docx (your master file)\n```\n\n## Quick Tailoring Checklist\n\nBefore submitting any resume:\n\n1. ✅ Summary mentions the exact job title\u002Ffunction\n2. ✅ Top 5 skills match job description's top 5 requirements\n3. ✅ Most relevant experience is positioned first\n4. ✅ Each job's top bullet addresses job's key requirement\n5. ✅ Keywords from JD appear naturally throughout\n6. ✅ Company\u002Findustry terminology is used correctly\n7. ✅ All claims are truthful\n8. ✅ File is named appropriately\n9. ✅ ATS formatting maintained\n10. ✅ Saved for interview prep reference\n\n## Output Format\n\nWhen tailoring a resume, provide:\n\n```markdown\n# TAILORED RESUME CHANGES\n\n## Target: [Job Title] at [Company]\n\n### Professional Summary\n**Before:** [Original]\n**After:** [Tailored version]\n**Keywords Added:** [List]\n\n### Skills Section\n**New Order:** [Reordered list]\n**Added:** [New keywords]\n**Removed:** [If any, for space]\n\n### Experience Changes\n\n**[Company Name] - [Title]**\n- Move bullet X to position 1\n- Modify bullet Y: [Before → After]\n- Add keyword \"[phrase]\" to bullet Z\n\n[Repeat for each relevant job]\n\n### Overall Changes Summary\n- Keywords added: X\n- Bullets modified: Y\n- Sections reordered: Yes\u002FNo\n- Estimated new match score: Z%\n```\n\n## Implementation Notes\n\n- Always start with the job description analyzer\n- Keep tailoring changes documented for interview prep\n- Maintain master resume as source of truth\n- Never sacrifice ATS compatibility for tailoring\n- Test keyword match after tailoring\n",{"name":5,"description":7},"main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fcareer\u002Fresume-tailor",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":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add davila7\u002Fclaude-code-templates --skill resume-tailor",{"tool":54,"command":55},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill resume-tailor",{"tool":57,"command":58},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill resume-tailor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcareer\u002Fresume-tailor\u002FSKILL.md",true,[],[63,92,119,150,185,209],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":74,"publishedAt":33},"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",[69],{"categoryNo":70,"categoryName":71,"taxonomyType":72,"taxonomyTypeDesc":73},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[75,76,77,78,79,30,80,81,28,32,82,83,84,85,86,87,88,89,90,91],"scoring","pool","wealthville pool scoring","liquidity","which","exit","now","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":99,"publishedAt":33},"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",[98],{"categoryNo":70,"categoryName":71,"taxonomyType":72,"taxonomyTypeDesc":73},[100,101,102,103,104,105,106,107,108,109,110,32,111,112,113,114,115,116,117,118],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":132,"publishedAt":33},"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",[125,128,129],{"categoryNo":126,"categoryName":127,"taxonomyType":72,"taxonomyTypeDesc":73},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":70,"categoryName":71,"taxonomyType":72,"taxonomyTypeDesc":73},{"categoryNo":130,"categoryName":131,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000033","数据分析师",[133,134,135,136,137,138,139,30,140,141,142,143,144,145,146,28,147,148,32,149],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":154,"licenseFileUrl":155,"sourceHtmlUrl":156,"categories":157,"keywords":161,"publishedAt":33},"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",[158],{"categoryNo":159,"categoryName":160,"taxonomyType":72,"taxonomyTypeDesc":73},"01JBSEEDCAT000000000000009","前端开发",[162,163,164,165,166,167,168,169,170,171,172,173,174,175,176,177,178,179,180,181,182,183,30,184],"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":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":154,"licenseFileUrl":189,"sourceHtmlUrl":190,"categories":191,"keywords":196,"publishedAt":33},"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",[192,195],{"categoryNo":193,"categoryName":194,"taxonomyType":72,"taxonomyTypeDesc":73},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":159,"categoryName":160,"taxonomyType":72,"taxonomyTypeDesc":73},[197,198,199,200,201,163,202,172,173,203,204,205,206,30,207,83,208],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":210,"name":211,"nameZh":6,"description":212,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":154,"licenseFileUrl":213,"sourceHtmlUrl":214,"categories":215,"keywords":223,"publishedAt":33},"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",[216,219,220],{"categoryNo":217,"categoryName":218,"taxonomyType":72,"taxonomyTypeDesc":73},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":70,"categoryName":71,"taxonomyType":72,"taxonomyTypeDesc":73},{"categoryNo":221,"categoryName":222,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000036","内容创作者",[224,225,226,227,228,229,230,231,165,232,175,111,233,234,235,236,237,145,238,32,239,240,241,242,243,89,244],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]