[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AE57QBTR9W5ACTKGGMVH6Z":3,"skill-same:01M6AE57QBTR9W5ACTKGGMVH6Z":110},{"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":28,"publishedAt":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":51,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M6AE57QBTR9W5ACTKGGMVH6Z","resume-version-manager",null,"Track different resume versions, maintain a master resume, and manage tailored variants. Use when the user mentions managing multiple resume versions, master resume, or organizing tailored copies.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33332,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcareer\u002Fresume-version-manager\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40],"resume version manager","version","resume","manager","user","use","master","manage","maintain","track","variants","when","2026-11-10 10:12:30",false,"---\nname: resume-version-manager\ndescription: Track different resume versions, maintain a master resume, and manage tailored variants. Use when the user mentions managing multiple resume versions, master resume, or organizing tailored copies.\n---\n\n# Resume Version Manager\n\n## When to Use This Skill\n\nUse this skill when the user:\n- Has multiple resume versions to manage\n- Needs to track tailored resumes\n- Wants to maintain a master resume\n- Is applying to many different roles\n- Mentions: \"resume versions\", \"master resume\", \"different versions\", \"track resumes\", \"which resume\"\n\n## Core Capabilities\n\n- Create and maintain master resume document\n- Track tailored resume versions\n- Organize resume versions by role\u002Findustry\n- Maintain consistent source of truth\n- Streamline resume updates\n- Prevent version confusion\n\n## The Version Management Problem\n\n**Common Pain Points:**\n- \"Which version did I send to Company X?\"\n- \"Where's my most recent resume?\"\n- \"I have 15 resume files and don't know which is best\"\n- \"I forgot to update my resume after that project\"\n- \"I keep tailoring from different base versions\"\n\n**The Solution:**\nA systematic approach with:\n1. One master resume (source of truth)\n2. Organized tailored versions\n3. Clear naming conventions\n4. Update workflow\n\n## Master Resume Concept\n\n### What is a Master Resume?\n\nA comprehensive document containing:\n- ALL your experiences (not just recent)\n- ALL bullet points you've ever written\n- Every achievement, project, skill\n- Full details (even if they won't fit on one page)\n\n**Purpose:** Source of truth to pull from when tailoring\n\n### Master Resume Structure\n\n```markdown\n# MASTER RESUME - [YOUR NAME]\nLast Updated: [Date]\n\n## CONTACT INFORMATION\n[Full contact details]\n\n## PROFESSIONAL SUMMARY VERSIONS\n[Summary for Role Type A]\n[Summary for Role Type B]\n[Summary for Role Type C]\n\n## ALL SKILLS\n### Technical Skills\n[Complete list by category]\n\n### Soft Skills\n[Complete list]\n\n### Industry Knowledge\n[All domains]\n\n## PROFESSIONAL EXPERIENCE\n\n### Company Name | Title | Dates\n\n**All Bullets (choose best for each application):**\n• Bullet 1 (leadership focused)\n• Bullet 2 (technical focused)\n• Bullet 3 (results focused)\n• Bullet 4 (collaboration focused)\n• Bullet 5 (additional achievement)\n• Bullet 6 (additional achievement)\n\n**Keywords this experience covers:**\n[List of keywords this job demonstrates]\n\n### Previous Company | Title | Dates\n[Same format...]\n\n## EDUCATION\n[Complete education history]\n\n## CERTIFICATIONS\n[All certifications ever earned]\n\n## PROJECTS\n[All notable projects]\n\n## VOLUNTEER \u002F ADDITIONAL\n[All other relevant experience]\n```\n\n## File Organization System\n\n### Folder Structure\n\n```\nResume\u002F\n├── Master\u002F\n│   └── LastName_Master_Resume.docx\n├── Tailored\u002F\n│   ├── ProductManagement\u002F\n│   │   ├── LastName_PM_Google_Jan2024.pdf\n│   │   └── LastName_PM_Meta_Jan2024.pdf\n│   ├── Engineering\u002F\n│   │   ├── LastName_SWE_Startup_Feb2024.pdf\n│   │   └── LastName_SWE_Enterprise_Feb2024.pdf\n│   └── General\u002F\n│       └── LastName_General_Resume.pdf\n├── CoverLetters\u002F\n│   ├── Google_PM_CoverLetter.docx\n│   └── Meta_PM_CoverLetter.docx\n└── Applications\u002F\n    └── ApplicationTracker.xlsx\n```\n\n### File Naming Convention\n\n**Pattern:**\n`[LastName]_[Role\u002FType]_[Company]_[Date].pdf`\n\n**Examples:**\n- `Smith_ProductManager_Google_Jan2024.pdf`\n- `Smith_SWE_Stripe_Feb2024.pdf`\n- `Smith_DataScience_General_2024.pdf`\n- `Smith_Master_Resume_v3.docx`\n\n## Version Categories\n\n### By Target Role\n\n**Product Management:**\n- Emphasizes: Strategy, roadmap, metrics, stakeholders\n- Skills highlight: Product tools, analytics, user research\n\n**Software Engineering:**\n- Emphasizes: Technical projects, systems, code\n- Skills highlight: Languages, frameworks, tools\n\n**Data Science:**\n- Emphasizes: Analysis, ML, statistical methods\n- Skills highlight: Python, SQL, ML libraries\n\n### By Industry\n\n**Tech\u002FStartup:**\n- Emphasizes: Innovation, growth, scrappiness\n- Tone: Modern, direct, achievement-focused\n\n**Enterprise\u002FCorporate:**\n- Emphasizes: Scale, process, collaboration\n- Tone: Professional, structured, comprehensive\n\n**Finance:**\n- Emphasizes: Analysis, compliance, accuracy\n- Tone: Conservative, precise, credentialed\n\n### By Seniority Level\n\n**Individual Contributor:**\n- Focus on execution and technical skills\n- Detailed project descriptions\n- Technical accomplishments\n\n**Manager:**\n- Team leadership and development\n- Cross-functional collaboration\n- Business impact metrics\n\n**Executive:**\n- Strategic leadership\n- P&L responsibility\n- Organizational transformation\n\n## Application Tracking\n\n### Simple Tracker Spreadsheet\n\n```\n| Company | Role | Version Used | Date Applied | Status | Notes |\n|---------|------|--------------|--------------|--------|-------|\n| Google | PM | PM_Google_Jan | 1\u002F15\u002F24 | Interview | 2nd round 2\u002F1 |\n| Meta | PM | PM_Meta_Jan | 1\u002F18\u002F24 | Applied | Referral from John |\n| Startup | PM | PM_General | 1\u002F20\u002F24 | Rejected | Too senior |\n```\n\n### Information to Track\n\n- Company name\n- Job title\n- Resume version used\n- Cover letter version used\n- Application date\n- Application method (portal, referral, direct)\n- Current status\n- Follow-up dates\n- Notes and contacts\n\n## Update Workflow\n\n### When to Update Master Resume\n\n**Immediately Update For:**\n- New job or promotion\n- Completed major project\n- New skills or certifications\n- Significant achievements\n- Awards or recognition\n\n**Quarterly Review:**\n- Add recent accomplishments\n- Update metrics with new data\n- Refresh skills section\n- Remove outdated information\n\n### Master to Tailored Workflow\n\n```\n1. Start with Master Resume\n   ↓\n2. Copy to new file (don't edit master)\n   ↓\n3. Analyze job description\n   ↓\n4. Select relevant bullets from master\n   ↓\n5. Choose appropriate summary version\n   ↓\n6. Reorder skills for relevance\n   ↓\n7. Add job-specific keywords\n   ↓\n8. Trim to appropriate length\n   ↓\n9. Save with proper naming convention\n   ↓\n10. Update application tracker\n```\n\n## Common Scenarios\n\n### Scenario 1: Applying to Similar Roles\n\n**Strategy:**\n- Create one well-tailored version for the role type\n- Make minor adjustments for each company\n- Track which slight variation went where\n\n### Scenario 2: Applying to Different Role Types\n\n**Strategy:**\n- Create separate base versions for each role type\n- Maintain clear folder organization\n- Each version pulls from same master\n\n### Scenario 3: Rapid Application Volume\n\n**Strategy:**\n- Create 2-3 strong category versions\n- Use \"general\" versions for quick applications\n- Reserve deep tailoring for top choices\n\n### Scenario 4: Career Transition\n\n**Strategy:**\n- Create transition-focused version\n- Emphasize transferable skills\n- Maintain original industry version as backup\n\n## Version Control Best Practices\n\n### DO:\n- ✅ Always work from master as source\n- ✅ Use consistent naming conventions\n- ✅ Track which version went where\n- ✅ Keep master updated\n- ✅ Date your files\n- ✅ Backup to cloud storage\n\n### DON'T:\n- ❌ Edit master directly for applications\n- ❌ Use vague names like \"resume_final_v2\"\n- ❌ Forget which version you sent\n- ❌ Let master get out of date\n- ❌ Have multiple \"master\" files\n- ❌ Delete old versions (archive instead)\n\n## Output Format\n\nWhen managing resume versions:\n\n```markdown\n# RESUME VERSION MANAGEMENT\n\n## Master Resume Status\n**Last Updated:** [Date]\n**Location:** [File path]\n**Total Experience Entries:** [X]\n**Total Bullet Points Available:** [X]\n\n## Active Versions\n\n### Role Type: Product Management\n**Base Version:** PM_General_2024.docx\n**Tailored Versions:**\n| Company | File Name | Date Created | Status |\n|---------|-----------|--------------|--------|\n| Google | PM_Google_Jan24 | 1\u002F15\u002F24 | Submitted |\n| Meta | PM_Meta_Jan24 | 1\u002F18\u002F24 | Submitted |\n\n### Role Type: Engineering\n[Same structure]\n\n## Update Queue\n- [ ] Add Q4 project results to master\n- [ ] Update skills with new certification\n- [ ] Archive versions older than 6 months\n\n## Recommended Actions\n1. [Action 1]\n2. [Action 2]\n```\n\n## Version Management Checklist\n\n- ✅ Master resume exists and is current\n- ✅ Folder structure is organized\n- ✅ Naming convention is consistent\n- ✅ Application tracker is maintained\n- ✅ Know which version sent to each company\n- ✅ All versions pull from same master\n- ✅ Backup system in place\n- ✅ Old versions archived (not deleted)\n- ✅ Update workflow is established\n- ✅ Regular master resume reviews scheduled\n","# Resume Version Manager\n\n## When to Use This Skill\n\nUse this skill when the user:\n- Has multiple resume versions to manage\n- Needs to track tailored resumes\n- Wants to maintain a master resume\n- Is applying to many different roles\n- Mentions: \"resume versions\", \"master resume\", \"different versions\", \"track resumes\", \"which resume\"\n\n## Core Capabilities\n\n- Create and maintain master resume document\n- Track tailored resume versions\n- Organize resume versions by role\u002Findustry\n- Maintain consistent source of truth\n- Streamline resume updates\n- Prevent version confusion\n\n## The Version Management Problem\n\n**Common Pain Points:**\n- \"Which version did I send to Company X?\"\n- \"Where's my most recent resume?\"\n- \"I have 15 resume files and don't know which is best\"\n- \"I forgot to update my resume after that project\"\n- \"I keep tailoring from different base versions\"\n\n**The Solution:**\nA systematic approach with:\n1. One master resume (source of truth)\n2. Organized tailored versions\n3. Clear naming conventions\n4. Update workflow\n\n## Master Resume Concept\n\n### What is a Master Resume?\n\nA comprehensive document containing:\n- ALL your experiences (not just recent)\n- ALL bullet points you've ever written\n- Every achievement, project, skill\n- Full details (even if they won't fit on one page)\n\n**Purpose:** Source of truth to pull from when tailoring\n\n### Master Resume Structure\n\n```markdown\n# MASTER RESUME - [YOUR NAME]\nLast Updated: [Date]\n\n## CONTACT INFORMATION\n[Full contact details]\n\n## PROFESSIONAL SUMMARY VERSIONS\n[Summary for Role Type A]\n[Summary for Role Type B]\n[Summary for Role Type C]\n\n## ALL SKILLS\n### Technical Skills\n[Complete list by category]\n\n### Soft Skills\n[Complete list]\n\n### Industry Knowledge\n[All domains]\n\n## PROFESSIONAL EXPERIENCE\n\n### Company Name | Title | Dates\n\n**All Bullets (choose best for each application):**\n• Bullet 1 (leadership focused)\n• Bullet 2 (technical focused)\n• Bullet 3 (results focused)\n• Bullet 4 (collaboration focused)\n• Bullet 5 (additional achievement)\n• Bullet 6 (additional achievement)\n\n**Keywords this experience covers:**\n[List of keywords this job demonstrates]\n\n### Previous Company | Title | Dates\n[Same format...]\n\n## EDUCATION\n[Complete education history]\n\n## CERTIFICATIONS\n[All certifications ever earned]\n\n## PROJECTS\n[All notable projects]\n\n## VOLUNTEER \u002F ADDITIONAL\n[All other relevant experience]\n```\n\n## File Organization System\n\n### Folder Structure\n\n```\nResume\u002F\n├── Master\u002F\n│   └── LastName_Master_Resume.docx\n├── Tailored\u002F\n│   ├── ProductManagement\u002F\n│   │   ├── LastName_PM_Google_Jan2024.pdf\n│   │   └── LastName_PM_Meta_Jan2024.pdf\n│   ├── Engineering\u002F\n│   │   ├── LastName_SWE_Startup_Feb2024.pdf\n│   │   └── LastName_SWE_Enterprise_Feb2024.pdf\n│   └── General\u002F\n│       └── LastName_General_Resume.pdf\n├── CoverLetters\u002F\n│   ├── Google_PM_CoverLetter.docx\n│   └── Meta_PM_CoverLetter.docx\n└── Applications\u002F\n    └── ApplicationTracker.xlsx\n```\n\n### File Naming Convention\n\n**Pattern:**\n`[LastName]_[Role\u002FType]_[Company]_[Date].pdf`\n\n**Examples:**\n- `Smith_ProductManager_Google_Jan2024.pdf`\n- `Smith_SWE_Stripe_Feb2024.pdf`\n- `Smith_DataScience_General_2024.pdf`\n- `Smith_Master_Resume_v3.docx`\n\n## Version Categories\n\n### By Target Role\n\n**Product Management:**\n- Emphasizes: Strategy, roadmap, metrics, stakeholders\n- Skills highlight: Product tools, analytics, user research\n\n**Software Engineering:**\n- Emphasizes: Technical projects, systems, code\n- Skills highlight: Languages, frameworks, tools\n\n**Data Science:**\n- Emphasizes: Analysis, ML, statistical methods\n- Skills highlight: Python, SQL, ML libraries\n\n### By Industry\n\n**Tech\u002FStartup:**\n- Emphasizes: Innovation, growth, scrappiness\n- Tone: Modern, direct, achievement-focused\n\n**Enterprise\u002FCorporate:**\n- Emphasizes: Scale, process, collaboration\n- Tone: Professional, structured, comprehensive\n\n**Finance:**\n- Emphasizes: Analysis, compliance, accuracy\n- Tone: Conservative, precise, credentialed\n\n### By Seniority Level\n\n**Individual Contributor:**\n- Focus on execution and technical skills\n- Detailed project descriptions\n- Technical accomplishments\n\n**Manager:**\n- Team leadership and development\n- Cross-functional collaboration\n- Business impact metrics\n\n**Executive:**\n- Strategic leadership\n- P&L responsibility\n- Organizational transformation\n\n## Application Tracking\n\n### Simple Tracker Spreadsheet\n\n```\n| Company | Role | Version Used | Date Applied | Status | Notes |\n|---------|------|--------------|--------------|--------|-------|\n| Google | PM | PM_Google_Jan | 1\u002F15\u002F24 | Interview | 2nd round 2\u002F1 |\n| Meta | PM | PM_Meta_Jan | 1\u002F18\u002F24 | Applied | Referral from John |\n| Startup | PM | PM_General | 1\u002F20\u002F24 | Rejected | Too senior |\n```\n\n### Information to Track\n\n- Company name\n- Job title\n- Resume version used\n- Cover letter version used\n- Application date\n- Application method (portal, referral, direct)\n- Current status\n- Follow-up dates\n- Notes and contacts\n\n## Update Workflow\n\n### When to Update Master Resume\n\n**Immediately Update For:**\n- New job or promotion\n- Completed major project\n- New skills or certifications\n- Significant achievements\n- Awards or recognition\n\n**Quarterly Review:**\n- Add recent accomplishments\n- Update metrics with new data\n- Refresh skills section\n- Remove outdated information\n\n### Master to Tailored Workflow\n\n```\n1. Start with Master Resume\n   ↓\n2. Copy to new file (don't edit master)\n   ↓\n3. Analyze job description\n   ↓\n4. Select relevant bullets from master\n   ↓\n5. Choose appropriate summary version\n   ↓\n6. Reorder skills for relevance\n   ↓\n7. Add job-specific keywords\n   ↓\n8. Trim to appropriate length\n   ↓\n9. Save with proper naming convention\n   ↓\n10. Update application tracker\n```\n\n## Common Scenarios\n\n### Scenario 1: Applying to Similar Roles\n\n**Strategy:**\n- Create one well-tailored version for the role type\n- Make minor adjustments for each company\n- Track which slight variation went where\n\n### Scenario 2: Applying to Different Role Types\n\n**Strategy:**\n- Create separate base versions for each role type\n- Maintain clear folder organization\n- Each version pulls from same master\n\n### Scenario 3: Rapid Application Volume\n\n**Strategy:**\n- Create 2-3 strong category versions\n- Use \"general\" versions for quick applications\n- Reserve deep tailoring for top choices\n\n### Scenario 4: Career Transition\n\n**Strategy:**\n- Create transition-focused version\n- Emphasize transferable skills\n- Maintain original industry version as backup\n\n## Version Control Best Practices\n\n### DO:\n- ✅ Always work from master as source\n- ✅ Use consistent naming conventions\n- ✅ Track which version went where\n- ✅ Keep master updated\n- ✅ Date your files\n- ✅ Backup to cloud storage\n\n### DON'T:\n- ❌ Edit master directly for applications\n- ❌ Use vague names like \"resume_final_v2\"\n- ❌ Forget which version you sent\n- ❌ Let master get out of date\n- ❌ Have multiple \"master\" files\n- ❌ Delete old versions (archive instead)\n\n## Output Format\n\nWhen managing resume versions:\n\n```markdown\n# RESUME VERSION MANAGEMENT\n\n## Master Resume Status\n**Last Updated:** [Date]\n**Location:** [File path]\n**Total Experience Entries:** [X]\n**Total Bullet Points Available:** [X]\n\n## Active Versions\n\n### Role Type: Product Management\n**Base Version:** PM_General_2024.docx\n**Tailored Versions:**\n| Company | File Name | Date Created | Status |\n|---------|-----------|--------------|--------|\n| Google | PM_Google_Jan24 | 1\u002F15\u002F24 | Submitted |\n| Meta | PM_Meta_Jan24 | 1\u002F18\u002F24 | Submitted |\n\n### Role Type: Engineering\n[Same structure]\n\n## Update Queue\n- [ ] Add Q4 project results to master\n- [ ] Update skills with new certification\n- [ ] Archive versions older than 6 months\n\n## Recommended Actions\n1. [Action 1]\n2. [Action 2]\n```\n\n## Version Management Checklist\n\n- ✅ Master resume exists and is current\n- ✅ Folder structure is organized\n- ✅ Naming convention is consistent\n- ✅ Application tracker is maintained\n- ✅ Know which version sent to each company\n- ✅ All versions pull from same master\n- ✅ Backup system in place\n- ✅ Old versions archived (not deleted)\n- ✅ Update workflow is established\n- ✅ Regular master resume reviews scheduled\n",{"name":5,"description":7},"main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fcareer\u002Fresume-version-manager",3911,"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-11 21:38:31",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add davila7\u002Fclaude-code-templates --skill resume-version-manager",{"tool":62,"command":63},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill resume-version-manager",{"tool":65,"command":66},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill resume-version-manager","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcareer\u002Fresume-version-manager\u002FSKILL.md",true,[70,76,80,84,90,94,100,103,106],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"append-handoff.sh","SCRIPT","脚本",56,"https:\u002F\u002Fgithub.com\u002Fpydantic\u002Fpydantic-ai\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbranch-context\u002Fappend-handoff.sh",{"path":77,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":78,"sourceHtmlUrl":79},"append-pr-decision.sh",60,"https:\u002F\u002Fgithub.com\u002Fpydantic\u002Fpydantic-ai\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbranch-context\u002Fappend-pr-decision.sh",{"path":81,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":82,"sourceHtmlUrl":83},"check-autoload-safety.sh",63,"https:\u002F\u002Fgithub.com\u002Fpydantic\u002Fpydantic-ai\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbranch-context\u002Fcheck-autoload-safety.sh",{"path":85,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"handoffs-index.template.md","REFERENCE","参考文档",65,"https:\u002F\u002Fgithub.com\u002Fpydantic\u002Fpydantic-ai\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbranch-context\u002Fhandoffs-index.template.md",{"path":91,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":92,"sourceHtmlUrl":93},"issue-brief.template.md",62,"https:\u002F\u002Fgithub.com\u002Fpydantic\u002Fpydantic-ai\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbranch-context\u002Fissue-brief.template.md",{"path":95,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":98,"sourceHtmlUrl":99},"issue-comment-fingerprint","OTHER","其他",64,"https:\u002F\u002Fgithub.com\u002Fpydantic\u002Fpydantic-ai\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbranch-context\u002Fissue-comment-fingerprint",{"path":101,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":102},"latest-handoff.sh","https:\u002F\u002Fgithub.com\u002Fpydantic\u002Fpydantic-ai\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbranch-context\u002Flatest-handoff.sh",{"path":104,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":82,"sourceHtmlUrl":105},"pr-decisions.template.md","https:\u002F\u002Fgithub.com\u002Fpydantic\u002Fpydantic-ai\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbranch-context\u002Fpr-decisions.template.md",{"path":107,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":108,"sourceHtmlUrl":109},"status.sh",48,"https:\u002F\u002Fgithub.com\u002Fpydantic\u002Fpydantic-ai\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbranch-context\u002Fstatus.sh",[111,136,163,194,229,253],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":118,"publishedAt":41},"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",[117],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[119,120,121,122,123,124,125,126,34,40,127,128,129,38,130,131,132,133,134,135],"scoring","pool","wealthville pool scoring","liquidity","which","for","exit","now","reduce","with","record","verdict","evm","solana","how","public","look",{"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":143,"publishedAt":41},"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",[142],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[144,145,146,147,148,149,150,151,152,153,154,40,155,156,157,158,159,160,161,162],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":176,"publishedAt":41},"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",[169,172,173],{"categoryNo":170,"categoryName":171,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":174,"categoryName":175,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000033","数据分析师",[177,178,179,180,181,182,183,124,184,185,186,187,188,189,190,34,191,192,40,193],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":195,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":198,"licenseFileUrl":199,"sourceHtmlUrl":200,"categories":201,"keywords":205,"publishedAt":41},"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",[202],{"categoryNo":203,"categoryName":204,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[206,207,208,209,210,211,212,213,214,215,216,217,218,219,220,221,222,223,224,225,226,227,124,228],"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":230,"name":231,"nameZh":6,"description":232,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":198,"licenseFileUrl":233,"sourceHtmlUrl":234,"categories":235,"keywords":240,"publishedAt":41},"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",[236,239],{"categoryNo":237,"categoryName":238,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":203,"categoryName":204,"taxonomyType":21,"taxonomyTypeDesc":22},[241,242,243,244,245,207,246,216,217,247,248,249,250,124,251,128,252],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":254,"name":255,"nameZh":6,"description":256,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":198,"licenseFileUrl":257,"sourceHtmlUrl":258,"categories":259,"keywords":267,"publishedAt":41},"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",[260,263,264],{"categoryNo":261,"categoryName":262,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":265,"categoryName":266,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",[268,269,270,271,272,273,274,275,209,276,219,155,277,278,279,280,281,189,282,40,283,284,285,286,287,133,288],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]