[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AE4B11Y7RNSVCBE52NMHGW":3,"skill-same:01M6AE4B11Y7RNSVCBE52NMHGW":78},{"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":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":53,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M6AE4B11Y7RNSVCBE52NMHGW","executive-resume-writer",null,"Create C-suite and VP-level resumes emphasizing strategic leadership, P&L ownership, and board-level impact. Use when the user mentions executive, C-suite, CEO, CFO, CTO, VP, director, or senior leadership resume.","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\u002Fexecutive-resume-writer\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],"executive resume writer","resume","writer","resume writer","senior","create","when","cfo","suite","cto","strategic","ownership","impact","director","leadership","use","user","board","ceo","2026-11-10 10:12:30",false,"---\nname: executive-resume-writer\ndescription: Create C-suite and VP-level resumes emphasizing strategic leadership, P&L ownership, and board-level impact. Use when the user mentions executive, C-suite, CEO, CFO, CTO, VP, director, or senior leadership resume.\n---\n\n# Executive Resume Writer\n\n## When to Use This Skill\n\nUse this skill when the user:\n- Is applying for C-suite, VP, or Director roles\n- Has 15+ years of experience in senior leadership\n- Needs to emphasize strategic leadership over tactical skills\n- Mentions: \"executive resume\", \"C-suite\", \"VP resume\", \"senior leadership\", \"board\", \"executive search\"\n\n## Core Capabilities\n\n- Write resumes for C-suite and VP-level positions\n- Emphasize strategic leadership and business transformation\n- Showcase P&L responsibility and organizational impact\n- Balance achievements with leadership philosophy\n- Format for executive recruiters and board presentations\n- Include board experience and industry recognition\n\n## Executive Resume Philosophy\n\n**Key Differences from Standard Resumes:**\n\n| Standard Resume | Executive Resume |\n|-----------------|------------------|\n| Lists skills | Demonstrates leadership brand |\n| Shows tasks | Shows strategic impact |\n| Focuses on \"what\" | Focuses on \"so what\" |\n| 1-2 pages | 2-3 pages acceptable |\n| Keywords for ATS | Story for decision-makers |\n| Individual contributions | Organizational transformation |\n\n## Executive Resume Structure\n\n### Recommended Sections\n\n```\n1. Executive Profile\u002FSummary\n2. Core Competencies (Leadership Themes)\n3. Career Highlights \u002F Key Achievements\n4. Professional Experience\n5. Board & Advisory Roles\n6. Education & Executive Development\n7. Industry Recognition (optional)\n```\n\n### Length Guidelines\n- VP\u002FSVP: 2 pages\n- C-Suite: 2-3 pages\n- Board CV: Can be longer\n\n## Executive Profile Section\n\nThis replaces the standard professional summary. Should communicate your **leadership brand**.\n\n### Format\n```\n[TITLE\u002FFUNCTION] EXECUTIVE\n\n[Leadership brand statement - who you are as a leader]\n\n[2-3 sentences on your track record with scope\u002Fscale]\n\n[What you're known for \u002F unique value proposition]\n```\n\n### Example\n\n```\nCHIEF OPERATING OFFICER | P&L LEADERSHIP | OPERATIONAL TRANSFORMATION\n\nGrowth-focused operations executive with 20+ years scaling B2B technology companies from $50M to $500M+ in revenue. Known for building high-performance teams, operational excellence, and creating scalable infrastructure that enables rapid growth.\n\nTrack record includes 3 successful exits, 2 IPO preparations, and leading organizations of 500+ employees across 6 countries. Expertise in operational strategy, M&A integration, and digital transformation in SaaS and enterprise software environments.\n\nCore philosophy: Build repeatable processes that scale while maintaining the agility that drives innovation.\n```\n\n## Core Competencies Section\n\nFrame as leadership themes rather than skills lists.\n\n### Example\n```\nLEADERSHIP COMPETENCIES\n\nStrategic Growth        | M&A Integration          | Digital Transformation\nP&L Management ($500M+) | Global Team Leadership   | Board Relations\nOperational Excellence  | Change Management        | Investor Relations\n```\n\n## Career Highlights Section\n\nPlace your biggest achievements upfront before chronological experience.\n\n### Format\n```\nCAREER HIGHLIGHTS\n\n• [Achievement 1 with metrics]\n• [Achievement 2 with metrics]\n• [Achievement 3 with metrics]\n• [Achievement 4 with metrics]\n```\n\n### Example\n```\nCAREER HIGHLIGHTS\n\n• Led operational transformation at TechCorp, improving EBITDA margins from 12% to 28% while growing revenue from $150M to $400M\n• Executed 5 acquisitions totaling $200M+ and successfully integrated 3 companies with 95% employee retention\n• Built global operations team from 50 to 500+ employees across US, EMEA, and APAC regions\n• Prepared company for successful IPO, implementing SOX compliance and investor-ready reporting\n```\n\n## Experience Section for Executives\n\n### The Executive Bullet Formula\n\n**[Leadership Action] + [Strategic Initiative] + [Business Outcome at Scale]**\n\n### Example Role\n\n```\nCHIEF OPERATING OFFICER\nTechCorp Inc. | San Francisco, CA | 2019 - Present\n$400M B2B SaaS company | 1,200 employees | Series D - IPO track\n\nRecruited by CEO to transform operations and prepare company for IPO. Direct reports include VP Engineering, VP Customer Success, VP Operations, and CIO. Full P&L ownership for services business ($150M).\n\nStrategic Initiatives & Results:\n\n• Operational Transformation: Redesigned end-to-end operations, improving gross margins from 62% to 78% and reducing customer onboarding time from 90 to 30 days\n\n• Scale & Growth: Built infrastructure to support growth from $150M to $400M revenue, including implementation of ERP, expansion to 3 new geographies, and establishment of 24\u002F7 global support\n\n• M&A Leadership: Served as operational lead for 3 acquisitions totaling $75M, achieving full integration within 6 months and 95% talent retention\n\n• Team Development: Expanded operations organization from 200 to 600 employees, established leadership development program that promoted 15 internal candidates to VP\u002FDirector roles\n\n• IPO Preparation: Led SOX compliance implementation, established audit committee reporting, and built investor-ready operational metrics and forecasting capabilities\n```\n\n### Key Elements for Executive Experience\n\n**Always Include:**\n- Company context (revenue, employees, stage)\n- Reporting structure \u002F span of control\n- P&L or budget responsibility\n- Strategic scope\n\n**Metrics to Emphasize:**\n- Revenue growth ($ and %)\n- Profitability improvement (margins, EBITDA)\n- Cost reduction\n- Team size and development\n- Geographic expansion\n- M&A activity\n- Exit outcomes\n\n## Board & Advisory Section\n\n```\nBOARD & ADVISORY POSITIONS\n\nBoard of Directors | TechStartup Inc. | 2022 - Present\n$50M ARR B2B SaaS company. Chair of Compensation Committee.\n\nAdvisory Board | VentureStudio | 2020 - Present\nSupporting portfolio companies with operational strategy and GTM execution.\n\nBoard Observer | AcquiredCo (acquired by BigTech, 2023) | 2021 - 2023\nProvided operational guidance through $200M acquisition process.\n```\n\n## Executive-Specific Considerations\n\n### Emphasize Transformation\n\nExecutives are hired to **transform**, not maintain. Show:\n- What changed because of you\n- Before\u002Fafter states\n- Scale of impact\n\n**Transformation Story Formula:**\n\"Inherited [situation]. Implemented [strategic change]. Achieved [outcome].\"\n\n### Show Leadership Philosophy\n\nUnlike individual contributor resumes, executive resumes should hint at **how** you lead.\n\n**Examples:**\n- \"Known for building consensus across diverse stakeholder groups\"\n- \"Leads with data-driven decision making while maintaining strategic flexibility\"\n- \"Champions innovation while maintaining operational discipline\"\n\n### Handle Tenure Carefully\n\n**Short Tenures:** Frame around specific missions\n- \"Brought in to lead post-merger integration\"\n- \"Recruited for turnaround; completed in 18 months\"\n- \"Joined to prepare company for acquisition\"\n\n**Long Tenures:** Show progression and reinvention\n- \"Promoted through 4 roles over 12 years\"\n- \"Led multiple transformations as company grew from $50M to $500M\"\n\n### Confidential Information\n\n**Do:**\n- Use percentage improvements when absolutes are confidential\n- Use ranges for revenue\u002Fheadcount\n- Speak to relative impact\n\n**Don't:**\n- Share proprietary strategies\n- Name confidential acquisition targets\n- Reveal undisclosed financial information\n\n## Executive Resume Tone\n\n### Power Language for Executives\n\n**Strategic Action Verbs:**\n- Spearheaded, Orchestrated, Championed, Steered\n- Transformed, Revolutionized, Pioneered\n- Architected, Engineered (strategically)\n- Drove, Accelerated, Catalyzed\n\n**Leadership Language:**\n- \"Led organization through...\"\n- \"Built and scaled...\"\n- \"Established vision for...\"\n- \"Negotiated and secured...\"\n- \"Championed transformation...\"\n\n### What to Avoid\n\n- ❌ Tactical\u002Foperational language (managed, handled, assisted)\n- ❌ First person pronouns (I, my, me)\n- ❌ Jargon without context\n- ❌ Generic statements without proof\n- ❌ Too much humility (take credit appropriately)\n\n## Output Format\n\nWhen writing an executive resume:\n\n```markdown\n# EXECUTIVE RESUME\n\n## Executive Profile\n[Full executive profile section]\n\n## Core Competencies\n[Formatted competency grid]\n\n## Career Highlights\n[4-6 top achievements with metrics]\n\n## Professional Experience\n\n### [Most Recent Role]\n[Full executive role writeup]\n\n### [Previous Role]\n[Full executive role writeup]\n\n## Board & Advisory\n[Board positions]\n\n## Education & Development\n[Degrees and executive education]\n\n---\n\n## Positioning Notes\n- Key narrative theme: [The story your resume tells]\n- Leadership brand: [What you're known for]\n- Differentiator: [What sets you apart]\n```\n\n## Executive Search Considerations\n\n**Your resume may be seen by:**\n- Executive recruiters\n- Board members\n- PE\u002FVC partners\n- CEOs and CHROs\n\n**Optimize for:**\n- Quick scanning by busy executives\n- Clear narrative of career progression\n- Obvious leadership brand\n- Credible, verifiable achievements\n\n**Remember:**\n- Executive searches often involve references before interviews\n- Your resume will be fact-checked\n- Relationships and reputation matter\n- The resume opens doors; relationships close deals\n","# Executive Resume Writer\n\n## When to Use This Skill\n\nUse this skill when the user:\n- Is applying for C-suite, VP, or Director roles\n- Has 15+ years of experience in senior leadership\n- Needs to emphasize strategic leadership over tactical skills\n- Mentions: \"executive resume\", \"C-suite\", \"VP resume\", \"senior leadership\", \"board\", \"executive search\"\n\n## Core Capabilities\n\n- Write resumes for C-suite and VP-level positions\n- Emphasize strategic leadership and business transformation\n- Showcase P&L responsibility and organizational impact\n- Balance achievements with leadership philosophy\n- Format for executive recruiters and board presentations\n- Include board experience and industry recognition\n\n## Executive Resume Philosophy\n\n**Key Differences from Standard Resumes:**\n\n| Standard Resume | Executive Resume |\n|-----------------|------------------|\n| Lists skills | Demonstrates leadership brand |\n| Shows tasks | Shows strategic impact |\n| Focuses on \"what\" | Focuses on \"so what\" |\n| 1-2 pages | 2-3 pages acceptable |\n| Keywords for ATS | Story for decision-makers |\n| Individual contributions | Organizational transformation |\n\n## Executive Resume Structure\n\n### Recommended Sections\n\n```\n1. Executive Profile\u002FSummary\n2. Core Competencies (Leadership Themes)\n3. Career Highlights \u002F Key Achievements\n4. Professional Experience\n5. Board & Advisory Roles\n6. Education & Executive Development\n7. Industry Recognition (optional)\n```\n\n### Length Guidelines\n- VP\u002FSVP: 2 pages\n- C-Suite: 2-3 pages\n- Board CV: Can be longer\n\n## Executive Profile Section\n\nThis replaces the standard professional summary. Should communicate your **leadership brand**.\n\n### Format\n```\n[TITLE\u002FFUNCTION] EXECUTIVE\n\n[Leadership brand statement - who you are as a leader]\n\n[2-3 sentences on your track record with scope\u002Fscale]\n\n[What you're known for \u002F unique value proposition]\n```\n\n### Example\n\n```\nCHIEF OPERATING OFFICER | P&L LEADERSHIP | OPERATIONAL TRANSFORMATION\n\nGrowth-focused operations executive with 20+ years scaling B2B technology companies from $50M to $500M+ in revenue. Known for building high-performance teams, operational excellence, and creating scalable infrastructure that enables rapid growth.\n\nTrack record includes 3 successful exits, 2 IPO preparations, and leading organizations of 500+ employees across 6 countries. Expertise in operational strategy, M&A integration, and digital transformation in SaaS and enterprise software environments.\n\nCore philosophy: Build repeatable processes that scale while maintaining the agility that drives innovation.\n```\n\n## Core Competencies Section\n\nFrame as leadership themes rather than skills lists.\n\n### Example\n```\nLEADERSHIP COMPETENCIES\n\nStrategic Growth        | M&A Integration          | Digital Transformation\nP&L Management ($500M+) | Global Team Leadership   | Board Relations\nOperational Excellence  | Change Management        | Investor Relations\n```\n\n## Career Highlights Section\n\nPlace your biggest achievements upfront before chronological experience.\n\n### Format\n```\nCAREER HIGHLIGHTS\n\n• [Achievement 1 with metrics]\n• [Achievement 2 with metrics]\n• [Achievement 3 with metrics]\n• [Achievement 4 with metrics]\n```\n\n### Example\n```\nCAREER HIGHLIGHTS\n\n• Led operational transformation at TechCorp, improving EBITDA margins from 12% to 28% while growing revenue from $150M to $400M\n• Executed 5 acquisitions totaling $200M+ and successfully integrated 3 companies with 95% employee retention\n• Built global operations team from 50 to 500+ employees across US, EMEA, and APAC regions\n• Prepared company for successful IPO, implementing SOX compliance and investor-ready reporting\n```\n\n## Experience Section for Executives\n\n### The Executive Bullet Formula\n\n**[Leadership Action] + [Strategic Initiative] + [Business Outcome at Scale]**\n\n### Example Role\n\n```\nCHIEF OPERATING OFFICER\nTechCorp Inc. | San Francisco, CA | 2019 - Present\n$400M B2B SaaS company | 1,200 employees | Series D - IPO track\n\nRecruited by CEO to transform operations and prepare company for IPO. Direct reports include VP Engineering, VP Customer Success, VP Operations, and CIO. Full P&L ownership for services business ($150M).\n\nStrategic Initiatives & Results:\n\n• Operational Transformation: Redesigned end-to-end operations, improving gross margins from 62% to 78% and reducing customer onboarding time from 90 to 30 days\n\n• Scale & Growth: Built infrastructure to support growth from $150M to $400M revenue, including implementation of ERP, expansion to 3 new geographies, and establishment of 24\u002F7 global support\n\n• M&A Leadership: Served as operational lead for 3 acquisitions totaling $75M, achieving full integration within 6 months and 95% talent retention\n\n• Team Development: Expanded operations organization from 200 to 600 employees, established leadership development program that promoted 15 internal candidates to VP\u002FDirector roles\n\n• IPO Preparation: Led SOX compliance implementation, established audit committee reporting, and built investor-ready operational metrics and forecasting capabilities\n```\n\n### Key Elements for Executive Experience\n\n**Always Include:**\n- Company context (revenue, employees, stage)\n- Reporting structure \u002F span of control\n- P&L or budget responsibility\n- Strategic scope\n\n**Metrics to Emphasize:**\n- Revenue growth ($ and %)\n- Profitability improvement (margins, EBITDA)\n- Cost reduction\n- Team size and development\n- Geographic expansion\n- M&A activity\n- Exit outcomes\n\n## Board & Advisory Section\n\n```\nBOARD & ADVISORY POSITIONS\n\nBoard of Directors | TechStartup Inc. | 2022 - Present\n$50M ARR B2B SaaS company. Chair of Compensation Committee.\n\nAdvisory Board | VentureStudio | 2020 - Present\nSupporting portfolio companies with operational strategy and GTM execution.\n\nBoard Observer | AcquiredCo (acquired by BigTech, 2023) | 2021 - 2023\nProvided operational guidance through $200M acquisition process.\n```\n\n## Executive-Specific Considerations\n\n### Emphasize Transformation\n\nExecutives are hired to **transform**, not maintain. Show:\n- What changed because of you\n- Before\u002Fafter states\n- Scale of impact\n\n**Transformation Story Formula:**\n\"Inherited [situation]. Implemented [strategic change]. Achieved [outcome].\"\n\n### Show Leadership Philosophy\n\nUnlike individual contributor resumes, executive resumes should hint at **how** you lead.\n\n**Examples:**\n- \"Known for building consensus across diverse stakeholder groups\"\n- \"Leads with data-driven decision making while maintaining strategic flexibility\"\n- \"Champions innovation while maintaining operational discipline\"\n\n### Handle Tenure Carefully\n\n**Short Tenures:** Frame around specific missions\n- \"Brought in to lead post-merger integration\"\n- \"Recruited for turnaround; completed in 18 months\"\n- \"Joined to prepare company for acquisition\"\n\n**Long Tenures:** Show progression and reinvention\n- \"Promoted through 4 roles over 12 years\"\n- \"Led multiple transformations as company grew from $50M to $500M\"\n\n### Confidential Information\n\n**Do:**\n- Use percentage improvements when absolutes are confidential\n- Use ranges for revenue\u002Fheadcount\n- Speak to relative impact\n\n**Don't:**\n- Share proprietary strategies\n- Name confidential acquisition targets\n- Reveal undisclosed financial information\n\n## Executive Resume Tone\n\n### Power Language for Executives\n\n**Strategic Action Verbs:**\n- Spearheaded, Orchestrated, Championed, Steered\n- Transformed, Revolutionized, Pioneered\n- Architected, Engineered (strategically)\n- Drove, Accelerated, Catalyzed\n\n**Leadership Language:**\n- \"Led organization through...\"\n- \"Built and scaled...\"\n- \"Established vision for...\"\n- \"Negotiated and secured...\"\n- \"Championed transformation...\"\n\n### What to Avoid\n\n- ❌ Tactical\u002Foperational language (managed, handled, assisted)\n- ❌ First person pronouns (I, my, me)\n- ❌ Jargon without context\n- ❌ Generic statements without proof\n- ❌ Too much humility (take credit appropriately)\n\n## Output Format\n\nWhen writing an executive resume:\n\n```markdown\n# EXECUTIVE RESUME\n\n## Executive Profile\n[Full executive profile section]\n\n## Core Competencies\n[Formatted competency grid]\n\n## Career Highlights\n[4-6 top achievements with metrics]\n\n## Professional Experience\n\n### [Most Recent Role]\n[Full executive role writeup]\n\n### [Previous Role]\n[Full executive role writeup]\n\n## Board & Advisory\n[Board positions]\n\n## Education & Development\n[Degrees and executive education]\n\n---\n\n## Positioning Notes\n- Key narrative theme: [The story your resume tells]\n- Leadership brand: [What you're known for]\n- Differentiator: [What sets you apart]\n```\n\n## Executive Search Considerations\n\n**Your resume may be seen by:**\n- Executive recruiters\n- Board members\n- PE\u002FVC partners\n- CEOs and CHROs\n\n**Optimize for:**\n- Quick scanning by busy executives\n- Clear narrative of career progression\n- Obvious leadership brand\n- Credible, verifiable achievements\n\n**Remember:**\n- Executive searches often involve references before interviews\n- Your resume will be fact-checked\n- Relationships and reputation matter\n- The resume opens doors; relationships close deals\n",{"name":5,"description":7},"main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fcareer\u002Fexecutive-resume-writer",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":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add davila7\u002Fclaude-code-templates --skill executive-resume-writer",{"tool":64,"command":65},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill executive-resume-writer",{"tool":67,"command":68},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill executive-resume-writer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcareer\u002Fexecutive-resume-writer\u002FSKILL.md",true,[72],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"agents\u002Fopenai.yaml","REFERENCE","参考文档",145,"https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Fgrill-with-docs\u002Fagents\u002Fopenai.yaml",[79,109,136,167,201,225],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":90,"publishedAt":43},"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",[85],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[91,92,93,94,95,96,97,98,39,30,99,100,101,102,103,104,105,106,107,108],"scoring","pool","wealthville pool scoring","liquidity","which","for","exit","now","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":116,"publishedAt":43},"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",[115],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},[117,118,119,120,121,122,123,124,125,126,127,30,128,129,130,131,132,133,134,135],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":149,"publishedAt":43},"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",[142,145,146],{"categoryNo":143,"categoryName":144,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},{"categoryNo":147,"categoryName":148,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000033","数据分析师",[150,151,152,153,154,155,156,96,157,158,159,160,161,162,163,39,164,165,30,166],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":171,"licenseFileUrl":172,"sourceHtmlUrl":173,"categories":174,"keywords":178,"publishedAt":43},"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",[175],{"categoryNo":176,"categoryName":177,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000009","前端开发",[179,180,181,182,183,184,185,186,187,188,189,190,191,192,193,194,195,196,32,197,198,199,96,200],"artifacts builder","web","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","file","components","shadcn","react","Tailwind","jsx","html","single-file","ui components",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":171,"licenseFileUrl":205,"sourceHtmlUrl":206,"categories":207,"keywords":212,"publishedAt":43},"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",[208,211],{"categoryNo":209,"categoryName":210,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":176,"categoryName":177,"taxonomyType":88,"taxonomyTypeDesc":89},[213,214,215,216,217,180,218,189,190,219,220,221,222,96,223,100,224],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":226,"name":227,"nameZh":6,"description":228,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":171,"licenseFileUrl":229,"sourceHtmlUrl":230,"categories":231,"keywords":239,"publishedAt":43},"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",[232,235,236],{"categoryNo":233,"categoryName":234,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},{"categoryNo":237,"categoryName":238,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000036","内容创作者",[240,241,242,243,244,245,246,247,182,248,192,128,249,250,251,252,253,162,254,30,255,256,257,258,259,106,260],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]