[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AE4YVPCN9EDV9REMTG8AVK":3,"skill-same:01M6AE4YVPCN9EDV9REMTG8AVK":94},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":49,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M6AE4YVPCN9EDV9REMTG8AVK","resume-formatter",null,"Ensure ATS-friendly formatting and create clean, scannable layouts. Use when the user mentions resume format, layout, template, design, or fixing formatting issues.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33418,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcareer\u002Fresume-formatter\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],"resume formatter","resume","formatter","design","create","issues","format","template","user","use","clean","layout","formatting","ats","when","2026-11-10 10:12:30",false,"---\nname: resume-formatter\ndescription: Ensure ATS-friendly formatting and create clean, scannable layouts. Use when the user mentions resume format, layout, template, design, or fixing formatting issues.\n---\n\n# Resume Formatter\n\n## When to Use This Skill\n\nUse this skill when the user:\n- Needs help with resume layout and formatting\n- Has a messy or hard-to-read resume\n- Wants to ensure ATS compatibility through formatting\n- Needs a clean, professional design\n- Mentions: \"format resume\", \"resume layout\", \"resume design\", \"clean resume\", \"professional format\"\n\n## Core Capabilities\n\n- Structure resumes for optimal readability\n- Ensure ATS compatibility through formatting\n- Create visual hierarchy\n- Optimize white space and margins\n- Select appropriate fonts and sizes\n- Balance aesthetic appeal with functionality\n\n## Formatting Fundamentals\n\n### The Dual Audience Challenge\n\nYour resume must work for:\n1. **ATS (Applicant Tracking Systems)** - Robots that parse text\n2. **Human Readers** - Recruiters who scan quickly\n\n**The Solution:** Clean, simple formatting that satisfies both.\n\n## Document Setup\n\n### Page Length\n- **Entry Level (0-5 years):** 1 page\n- **Mid-Level (5-15 years):** 1-2 pages\n- **Senior\u002FExecutive (15+ years):** 2 pages (max 3 for executives)\n\n### Margins\n- **Recommended:** 0.5\" - 1\" all sides\n- **Minimum:** 0.5\" (don't go smaller)\n- **Maximum:** 1\" (don't waste space)\n\n### Font Selection\n\n**Safe, ATS-Friendly Fonts:**\n- **Sans-serif:** Arial, Calibri, Helvetica, Verdana\n- **Serif:** Times New Roman, Georgia, Garamond\n\n**Font Sizes:**\n- **Name:** 16-20pt\n- **Section Headers:** 12-14pt\n- **Body Text:** 10-12pt\n- **Minimum readable:** 10pt\n\n### Spacing\n- **Line spacing:** 1.0 to 1.15\n- **Space after paragraphs:** 6-12pt\n- **Section spacing:** 12-16pt between sections\n\n## ATS-Safe Formatting Rules\n\n### DO:\n- ✅ Use standard fonts\n- ✅ Use simple bullet points (•, -, *)\n- ✅ Use bold and italic sparingly\n- ✅ Use standard section headers\n- ✅ Save as .docx or text-based .pdf\n- ✅ Put contact info in body (not header)\n- ✅ Use single column layout\n- ✅ Use consistent formatting throughout\n\n### DON'T:\n- ❌ Use tables (except simple ones for contact info)\n- ❌ Use text boxes\n- ❌ Use columns (multi-column layouts)\n- ❌ Use headers\u002Ffooters for important info\n- ❌ Use images or graphics\n- ❌ Use unusual fonts\n- ❌ Use skill bars or progress indicators\n- ❌ Use special characters or emojis\n- ❌ Use color for essential information\n\n## Section Organization\n\n### Standard Section Order\n\n```\n1. Contact Information\n2. Professional Summary (optional)\n3. Skills\u002FTechnical Skills\n4. Professional Experience\n5. Education\n6. Certifications (if relevant)\n7. Additional (volunteer, languages, etc.)\n```\n\n### Section Header Formatting\n\n**ATS-Recognized Headers:**\n- PROFESSIONAL EXPERIENCE or WORK EXPERIENCE\n- EDUCATION\n- SKILLS or TECHNICAL SKILLS\n- PROFESSIONAL SUMMARY or SUMMARY\n- CERTIFICATIONS\n- PROJECTS\n\n**Format Options:**\n```\nPROFESSIONAL EXPERIENCE\n━━━━━━━━━━━━━━━━━━━━━━\n\nor\n\nProfessional Experience\n_______________________\n\nor\n\nPROFESSIONAL EXPERIENCE\n```\n\n## Contact Information Layout\n\n### Recommended Format\n```\nJOHN SMITH\njohn.smith@email.com | (555) 123-4567 | linkedin.com\u002Fin\u002Fjohnsmith\nSan Francisco, CA\n```\n\n### Alternative Format\n```\nJOHN SMITH\nSan Francisco, CA\njohn.smith@email.com | (555) 123-4567\nLinkedIn: linkedin.com\u002Fin\u002Fjohnsmith | GitHub: github.com\u002Fjohnsmith\n```\n\n### What to Include\n- ✅ Full name\n- ✅ Professional email\n- ✅ Phone number\n- ✅ City, State (no full address needed)\n- ✅ LinkedIn URL\n- ✅ Portfolio\u002FGitHub (if relevant)\n\n### What to Exclude\n- ❌ Full street address\n- ❌ Photo\n- ❌ Date of birth\n- ❌ Marital status\n- ❌ Multiple phone numbers\n- ❌ Personal social media\n\n## Experience Section Formatting\n\n### Standard Format\n```\nCOMPANY NAME | City, ST\nJob Title | Month Year - Month Year\n\n• Achievement bullet with metrics and results\n• Achievement bullet with metrics and results\n• Achievement bullet with metrics and results\n```\n\n### Alternative Format\n```\nJob Title\nCOMPANY NAME, City, ST                    Month Year - Month Year\n\n• Achievement bullet with metrics and results\n• Achievement bullet with metrics and results\n```\n\n### Date Formatting\n- **Consistent format:** Use same format throughout\n- **Recommended:** Month Year (Jan 2020 - Present)\n- **Also acceptable:** MM\u002FYYYY (01\u002F2020 - Present)\n- **Avoid:** Full dates (January 15, 2020)\n\n### Bullet Point Guidelines\n- **Length:** 1-2 lines each\n- **Format:** Start with action verb, end with result\n- **Quantity:** 3-6 bullets per role (more for recent, fewer for old)\n- **Symbol:** Use standard bullets (•, -, *)\n\n## Skills Section Formatting\n\n### Option 1: Simple List\n```\nSKILLS\nPython, JavaScript, SQL, React, Node.js, AWS, Docker, Git, Agile, JIRA\n```\n\n### Option 2: Categorized\n```\nTECHNICAL SKILLS\nLanguages: Python, JavaScript, TypeScript, SQL\nFrameworks: React, Node.js, Django, Flask\nTools: AWS, Docker, Kubernetes, Git, Jenkins\n```\n\n### Option 3: Columns (Careful with ATS)\n```\nSKILLS\nLanguages        Frameworks       Tools\nPython           React            AWS\nJavaScript       Node.js          Docker\nSQL              Django           Git\n```\n\n**Note:** Multi-column layouts may cause ATS issues. Test before using.\n\n## Education Section Formatting\n\n### Standard Format\n```\nEDUCATION\nBachelor of Science in Computer Science\nUniversity of California, Berkeley | 2018\nGPA: 3.8\u002F4.0 (include if 3.5+)\n```\n\n### With Honors\u002FDetails\n```\nEDUCATION\nMBA, Finance & Strategy | Stanford Graduate School of Business | 2020\n• Graduated with Distinction\n• Relevant Coursework: Corporate Finance, M&A Strategy\n```\n\n## Visual Hierarchy Principles\n\n### Hierarchy Order\n1. **Name** - Largest, most prominent\n2. **Section Headers** - Clear divisions\n3. **Job Titles\u002FCompany Names** - Easy to scan\n4. **Bullet Points** - The details\n\n### Creating Hierarchy\n- Use font SIZE to create levels\n- Use **BOLD** for emphasis (names, titles, headers)\n- Use CAPS for section headers\n- Use consistent spacing to separate sections\n\n## White Space Management\n\n### Good White Space:\n- Between sections (clear separation)\n- After headings (visual breathing room)\n- Between bullets (don't cram)\n- Around margins (frame the content)\n\n### Bad White Space:\n- Huge gaps between sections\n- Inconsistent spacing\n- Half-empty pages\n- Excessive margins eating space\n\n## Common Formatting Mistakes\n\n### Mistake 1: Wall of Text\n**Problem:** Dense paragraphs with no bullets\n**Solution:** Use bullet points, keep paragraphs short\n\n### Mistake 2: Inconsistent Formatting\n**Problem:** Different fonts, sizes, or styles throughout\n**Solution:** Pick one format and stick to it\n\n### Mistake 3: Trying to Be Creative\n**Problem:** Fancy designs that break ATS\n**Solution:** Save creativity for portfolio, not resume\n\n### Mistake 4: Too Much Information\n**Problem:** Cramming everything onto one page\n**Solution:** Edit ruthlessly, prioritize relevance\n\n### Mistake 5: Not Enough Information\n**Problem:** Half-page resume with massive margins\n**Solution:** Add detail, reduce margins (to 0.5\")\n\n## File Format Guidelines\n\n### For Online Applications\n- **.docx** - Best for ATS parsing\n- **.pdf** - Good if created from Word (not scanned)\n\n### For Email\u002FDirect Send\n- **.pdf** - Preserves formatting\n\n### File Naming\n```\nFirstName_LastName_Resume.pdf\nJohnSmith_Resume_ProductManager.pdf\n```\n\n**Avoid:**\n- resume_final_v2_updated_FINAL.docx\n- resume (1).pdf\n- Untitled document.docx\n\n## Output Format\n\nWhen formatting a resume:\n\n```markdown\n# RESUME FORMATTING REVIEW\n\n## Current Issues\n- [ ] [Issue 1]\n- [ ] [Issue 2]\n- [ ] [Issue 3]\n\n## Recommended Changes\n\n### Document Setup\n- Margins: [Current] → [Recommended]\n- Font: [Current] → [Recommended]\n- Font sizes: [Current] → [Recommended]\n\n### Section Order\n**Current:** [Current order]\n**Recommended:** [New order and why]\n\n### Visual Improvements\n- [Specific change 1]\n- [Specific change 2]\n\n### ATS Compatibility Fixes\n- [Fix 1]\n- [Fix 2]\n\n## Before\u002FAfter Preview\n\n### Before:\n[Description or example of current formatting]\n\n### After:\n[Description or example of improved formatting]\n```\n\n## Quick Formatting Checklist\n\nBefore submitting any resume:\n- ✅ One page (or two if warranted)\n- ✅ Standard font (10-12pt body)\n- ✅ Consistent formatting throughout\n- ✅ Clear section headers\n- ✅ Appropriate white space\n- ✅ No tables, text boxes, or columns\n- ✅ Contact info in body (not header)\n- ✅ Saved as .docx or .pdf\n- ✅ Proper file name\n- ✅ Proofread for consistency\n","# Resume Formatter\n\n## When to Use This Skill\n\nUse this skill when the user:\n- Needs help with resume layout and formatting\n- Has a messy or hard-to-read resume\n- Wants to ensure ATS compatibility through formatting\n- Needs a clean, professional design\n- Mentions: \"format resume\", \"resume layout\", \"resume design\", \"clean resume\", \"professional format\"\n\n## Core Capabilities\n\n- Structure resumes for optimal readability\n- Ensure ATS compatibility through formatting\n- Create visual hierarchy\n- Optimize white space and margins\n- Select appropriate fonts and sizes\n- Balance aesthetic appeal with functionality\n\n## Formatting Fundamentals\n\n### The Dual Audience Challenge\n\nYour resume must work for:\n1. **ATS (Applicant Tracking Systems)** - Robots that parse text\n2. **Human Readers** - Recruiters who scan quickly\n\n**The Solution:** Clean, simple formatting that satisfies both.\n\n## Document Setup\n\n### Page Length\n- **Entry Level (0-5 years):** 1 page\n- **Mid-Level (5-15 years):** 1-2 pages\n- **Senior\u002FExecutive (15+ years):** 2 pages (max 3 for executives)\n\n### Margins\n- **Recommended:** 0.5\" - 1\" all sides\n- **Minimum:** 0.5\" (don't go smaller)\n- **Maximum:** 1\" (don't waste space)\n\n### Font Selection\n\n**Safe, ATS-Friendly Fonts:**\n- **Sans-serif:** Arial, Calibri, Helvetica, Verdana\n- **Serif:** Times New Roman, Georgia, Garamond\n\n**Font Sizes:**\n- **Name:** 16-20pt\n- **Section Headers:** 12-14pt\n- **Body Text:** 10-12pt\n- **Minimum readable:** 10pt\n\n### Spacing\n- **Line spacing:** 1.0 to 1.15\n- **Space after paragraphs:** 6-12pt\n- **Section spacing:** 12-16pt between sections\n\n## ATS-Safe Formatting Rules\n\n### DO:\n- ✅ Use standard fonts\n- ✅ Use simple bullet points (•, -, *)\n- ✅ Use bold and italic sparingly\n- ✅ Use standard section headers\n- ✅ Save as .docx or text-based .pdf\n- ✅ Put contact info in body (not header)\n- ✅ Use single column layout\n- ✅ Use consistent formatting throughout\n\n### DON'T:\n- ❌ Use tables (except simple ones for contact info)\n- ❌ Use text boxes\n- ❌ Use columns (multi-column layouts)\n- ❌ Use headers\u002Ffooters for important info\n- ❌ Use images or graphics\n- ❌ Use unusual fonts\n- ❌ Use skill bars or progress indicators\n- ❌ Use special characters or emojis\n- ❌ Use color for essential information\n\n## Section Organization\n\n### Standard Section Order\n\n```\n1. Contact Information\n2. Professional Summary (optional)\n3. Skills\u002FTechnical Skills\n4. Professional Experience\n5. Education\n6. Certifications (if relevant)\n7. Additional (volunteer, languages, etc.)\n```\n\n### Section Header Formatting\n\n**ATS-Recognized Headers:**\n- PROFESSIONAL EXPERIENCE or WORK EXPERIENCE\n- EDUCATION\n- SKILLS or TECHNICAL SKILLS\n- PROFESSIONAL SUMMARY or SUMMARY\n- CERTIFICATIONS\n- PROJECTS\n\n**Format Options:**\n```\nPROFESSIONAL EXPERIENCE\n━━━━━━━━━━━━━━━━━━━━━━\n\nor\n\nProfessional Experience\n_______________________\n\nor\n\nPROFESSIONAL EXPERIENCE\n```\n\n## Contact Information Layout\n\n### Recommended Format\n```\nJOHN SMITH\njohn.smith@email.com | (555) 123-4567 | linkedin.com\u002Fin\u002Fjohnsmith\nSan Francisco, CA\n```\n\n### Alternative Format\n```\nJOHN SMITH\nSan Francisco, CA\njohn.smith@email.com | (555) 123-4567\nLinkedIn: linkedin.com\u002Fin\u002Fjohnsmith | GitHub: github.com\u002Fjohnsmith\n```\n\n### What to Include\n- ✅ Full name\n- ✅ Professional email\n- ✅ Phone number\n- ✅ City, State (no full address needed)\n- ✅ LinkedIn URL\n- ✅ Portfolio\u002FGitHub (if relevant)\n\n### What to Exclude\n- ❌ Full street address\n- ❌ Photo\n- ❌ Date of birth\n- ❌ Marital status\n- ❌ Multiple phone numbers\n- ❌ Personal social media\n\n## Experience Section Formatting\n\n### Standard Format\n```\nCOMPANY NAME | City, ST\nJob Title | Month Year - Month Year\n\n• Achievement bullet with metrics and results\n• Achievement bullet with metrics and results\n• Achievement bullet with metrics and results\n```\n\n### Alternative Format\n```\nJob Title\nCOMPANY NAME, City, ST                    Month Year - Month Year\n\n• Achievement bullet with metrics and results\n• Achievement bullet with metrics and results\n```\n\n### Date Formatting\n- **Consistent format:** Use same format throughout\n- **Recommended:** Month Year (Jan 2020 - Present)\n- **Also acceptable:** MM\u002FYYYY (01\u002F2020 - Present)\n- **Avoid:** Full dates (January 15, 2020)\n\n### Bullet Point Guidelines\n- **Length:** 1-2 lines each\n- **Format:** Start with action verb, end with result\n- **Quantity:** 3-6 bullets per role (more for recent, fewer for old)\n- **Symbol:** Use standard bullets (•, -, *)\n\n## Skills Section Formatting\n\n### Option 1: Simple List\n```\nSKILLS\nPython, JavaScript, SQL, React, Node.js, AWS, Docker, Git, Agile, JIRA\n```\n\n### Option 2: Categorized\n```\nTECHNICAL SKILLS\nLanguages: Python, JavaScript, TypeScript, SQL\nFrameworks: React, Node.js, Django, Flask\nTools: AWS, Docker, Kubernetes, Git, Jenkins\n```\n\n### Option 3: Columns (Careful with ATS)\n```\nSKILLS\nLanguages        Frameworks       Tools\nPython           React            AWS\nJavaScript       Node.js          Docker\nSQL              Django           Git\n```\n\n**Note:** Multi-column layouts may cause ATS issues. Test before using.\n\n## Education Section Formatting\n\n### Standard Format\n```\nEDUCATION\nBachelor of Science in Computer Science\nUniversity of California, Berkeley | 2018\nGPA: 3.8\u002F4.0 (include if 3.5+)\n```\n\n### With Honors\u002FDetails\n```\nEDUCATION\nMBA, Finance & Strategy | Stanford Graduate School of Business | 2020\n• Graduated with Distinction\n• Relevant Coursework: Corporate Finance, M&A Strategy\n```\n\n## Visual Hierarchy Principles\n\n### Hierarchy Order\n1. **Name** - Largest, most prominent\n2. **Section Headers** - Clear divisions\n3. **Job Titles\u002FCompany Names** - Easy to scan\n4. **Bullet Points** - The details\n\n### Creating Hierarchy\n- Use font SIZE to create levels\n- Use **BOLD** for emphasis (names, titles, headers)\n- Use CAPS for section headers\n- Use consistent spacing to separate sections\n\n## White Space Management\n\n### Good White Space:\n- Between sections (clear separation)\n- After headings (visual breathing room)\n- Between bullets (don't cram)\n- Around margins (frame the content)\n\n### Bad White Space:\n- Huge gaps between sections\n- Inconsistent spacing\n- Half-empty pages\n- Excessive margins eating space\n\n## Common Formatting Mistakes\n\n### Mistake 1: Wall of Text\n**Problem:** Dense paragraphs with no bullets\n**Solution:** Use bullet points, keep paragraphs short\n\n### Mistake 2: Inconsistent Formatting\n**Problem:** Different fonts, sizes, or styles throughout\n**Solution:** Pick one format and stick to it\n\n### Mistake 3: Trying to Be Creative\n**Problem:** Fancy designs that break ATS\n**Solution:** Save creativity for portfolio, not resume\n\n### Mistake 4: Too Much Information\n**Problem:** Cramming everything onto one page\n**Solution:** Edit ruthlessly, prioritize relevance\n\n### Mistake 5: Not Enough Information\n**Problem:** Half-page resume with massive margins\n**Solution:** Add detail, reduce margins (to 0.5\")\n\n## File Format Guidelines\n\n### For Online Applications\n- **.docx** - Best for ATS parsing\n- **.pdf** - Good if created from Word (not scanned)\n\n### For Email\u002FDirect Send\n- **.pdf** - Preserves formatting\n\n### File Naming\n```\nFirstName_LastName_Resume.pdf\nJohnSmith_Resume_ProductManager.pdf\n```\n\n**Avoid:**\n- resume_final_v2_updated_FINAL.docx\n- resume (1).pdf\n- Untitled document.docx\n\n## Output Format\n\nWhen formatting a resume:\n\n```markdown\n# RESUME FORMATTING REVIEW\n\n## Current Issues\n- [ ] [Issue 1]\n- [ ] [Issue 2]\n- [ ] [Issue 3]\n\n## Recommended Changes\n\n### Document Setup\n- Margins: [Current] → [Recommended]\n- Font: [Current] → [Recommended]\n- Font sizes: [Current] → [Recommended]\n\n### Section Order\n**Current:** [Current order]\n**Recommended:** [New order and why]\n\n### Visual Improvements\n- [Specific change 1]\n- [Specific change 2]\n\n### ATS Compatibility Fixes\n- [Fix 1]\n- [Fix 2]\n\n## Before\u002FAfter Preview\n\n### Before:\n[Description or example of current formatting]\n\n### After:\n[Description or example of improved formatting]\n```\n\n## Quick Formatting Checklist\n\nBefore submitting any resume:\n- ✅ One page (or two if warranted)\n- ✅ Standard font (10-12pt body)\n- ✅ Consistent formatting throughout\n- ✅ Clear section headers\n- ✅ Appropriate white space\n- ✅ No tables, text boxes, or columns\n- ✅ Contact info in body (not header)\n- ✅ Saved as .docx or .pdf\n- ✅ Proper file name\n- ✅ Proofread for consistency\n",{"name":5,"description":7},"main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fcareer\u002Fresume-formatter",3926,"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-12 14:45:56",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add davila7\u002Fclaude-code-templates --skill resume-formatter",{"tool":60,"command":61},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill resume-formatter",{"tool":63,"command":64},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill resume-formatter","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcareer\u002Fresume-formatter\u002FSKILL.md",true,[68,74,78,82,86,90],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"agents\u002Fopenai.yaml","REFERENCE","参考文档",152,"https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fagents\u002Fopenai.yaml",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"domain.md",2033,"https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fdomain.md",{"path":79,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":80,"sourceHtmlUrl":81},"issue-tracker-github.md",3731,"https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fissue-tracker-github.md",{"path":83,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":84,"sourceHtmlUrl":85},"issue-tracker-gitlab.md",3809,"https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fissue-tracker-gitlab.md",{"path":87,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":88,"sourceHtmlUrl":89},"issue-tracker-local.md",1810,"https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fissue-tracker-local.md",{"path":91,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":92,"sourceHtmlUrl":93},"triage-labels.md",1045,"https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Fsetup-matt-pocock-skills\u002Ftriage-labels.md",[95,125,152,183,218,242],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":106,"publishedAt":39},"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",[101],{"categoryNo":102,"categoryName":103,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[107,108,109,110,111,112,113,114,33,38,115,116,117,118,119,120,121,122,123,124],"scoring","pool","wealthville pool scoring","liquidity","which","for","exit","now","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":132,"publishedAt":39},"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",[131],{"categoryNo":102,"categoryName":103,"taxonomyType":104,"taxonomyTypeDesc":105},[133,134,135,136,137,138,139,140,141,142,143,38,144,145,146,147,148,149,150,151],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":165,"publishedAt":39},"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",[158,161,162],{"categoryNo":159,"categoryName":160,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":102,"categoryName":103,"taxonomyType":104,"taxonomyTypeDesc":105},{"categoryNo":163,"categoryName":164,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000033","数据分析师",[166,167,168,169,170,171,172,112,173,174,175,176,177,178,179,33,180,181,38,182],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":187,"licenseFileUrl":188,"sourceHtmlUrl":189,"categories":190,"keywords":194,"publishedAt":39},"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",[191],{"categoryNo":192,"categoryName":193,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000009","前端开发",[195,196,197,198,199,200,201,202,203,204,205,206,207,208,209,210,211,212,213,214,215,216,112,217],"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":219,"name":220,"nameZh":6,"description":221,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":187,"licenseFileUrl":222,"sourceHtmlUrl":223,"categories":224,"keywords":229,"publishedAt":39},"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",[225,228],{"categoryNo":226,"categoryName":227,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":192,"categoryName":193,"taxonomyType":104,"taxonomyTypeDesc":105},[230,231,232,233,234,196,235,205,206,236,237,238,239,112,240,116,241],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":243,"name":244,"nameZh":6,"description":245,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":187,"licenseFileUrl":246,"sourceHtmlUrl":247,"categories":248,"keywords":256,"publishedAt":39},"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",[249,252,253],{"categoryNo":250,"categoryName":251,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":102,"categoryName":103,"taxonomyType":104,"taxonomyTypeDesc":105},{"categoryNo":254,"categoryName":255,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000036","内容创作者",[257,258,259,260,261,262,263,264,198,265,208,144,266,267,268,269,270,178,271,38,272,273,274,275,276,122,277],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]