[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AE4VX6AVTZD8JBBT7E3EFZ":3,"skill-same:01M6AE4VX6AVTZD8JBBT7E3EFZ":74},{"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},"01M6AE4VX6AVTZD8JBBT7E3EFZ","resume-bullet-writer",null,"Transform weak resume bullets into achievement-focused statements with metrics and impact. Use when the user wants to rewrite bullets, strengthen accomplishments, or add action verbs and impact to their resume.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33602,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcareer\u002Fresume-bullet-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],"resume bullet writer","resume","writer","add action","metrics","user","use","rewrite","impact","add","transform","with","action","strengthen","when","2026-11-10 10:12:30",false,"---\nname: resume-bullet-writer\ndescription: Transform weak resume bullets into achievement-focused statements with metrics and impact. Use when the user wants to rewrite bullets, strengthen accomplishments, or add action verbs and impact to their resume.\n---\n\n# Resume Bullet Writer\n\n## When to Use This Skill\n\nUse this skill when the user wants to:\n- Write or improve resume bullet points\n- Transform weak descriptions into strong achievements\n- Add metrics and quantifiable results\n- Make their experience more compelling\n- Mentions: \"improve my bullets\", \"make my resume stronger\", \"quantify my achievements\", \"results-driven\"\n\nAlso use when you see weak bullets that need improvement (passive language, no metrics, vague descriptions).\n\n## Core Capabilities\n\n- Transform weak bullet points into achievement-focused statements\n- Apply STAR method and X-Y-Z formula\n- Add quantifiable metrics and results\n- Use strong action verbs\n- Tailor bullets to specific roles\u002Findustries\n- Ensure every bullet shows impact, not just duties\n\n## The Bullet Point Problem\n\nMost resumes have weak bullets that list job duties instead of achievements:\n\n❌ **Weak Bullets (What NOT to do):**\n- \"Responsible for managing team\"\n- \"Helped with customer service\"\n- \"Worked on improving processes\"\n- \"Assisted with projects\"\n\nThese are passive, vague, and don't show impact or results.\n\n✅ **Strong Bullets (What TO do):**\n- \"Led cross-functional team of 12 to deliver $2M product, increasing revenue by 35%\"\n- \"Resolved 50+ customer issues daily, improving satisfaction scores from 3.2 to 4.8\u002F5\"\n- \"Streamlined approval process, reducing cycle time by 40% (from 10 to 6 days)\"\n- \"Managed portfolio of 8 concurrent projects with 100% on-time delivery rate\"\n\nThese are active, specific, and quantify the impact.\n\n## Core Frameworks\n\n### 1. The X-Y-Z Formula (Google Method)\n\n**Structure:** \"Accomplished [X] as measured by [Y] by doing [Z]\"\n\n- X = What you achieved\n- Y = How you measured it\n- Z = What actions you took\n\n**Examples:**\n\n```\n❌ BEFORE: \"Managed social media accounts\"\n\n✅ AFTER: \"Grew Instagram following by 250% (5K to 17.5K) by implementing daily content calendar and influencer partnerships\"\n\nX = Grew Instagram following by 250%\nY = 5K to 17.5K followers\nZ = Daily content calendar + influencer partnerships\n```\n\n```\n❌ BEFORE: \"Improved customer service\"\n\n✅ AFTER: \"Increased customer satisfaction scores by 40% (3.2 to 4.5\u002F5) by redesigning support ticketing system and training 15 agents\"\n\nX = Increased customer satisfaction by 40%\nY = 3.2 to 4.5 out of 5\nZ = Redesigned ticketing system + trained agents\n```\n\n### 2. STAR Method\n\n**Structure:**\n- **S**ituation: What was the context?\n- **T**ask: What needed to be done?\n- **A**ction: What did YOU specifically do?\n- **R**esult: What was the measurable outcome?\n\n**Example:**\n\nFull STAR story:\n\"Inherited underperforming sales team (S) with 65% quota attainment. Tasked with improving performance within Q1 (T). Implemented new training program and revised commission structure (A). Achieved 92% quota attainment by Q2, generating $1.8M additional revenue (R).\"\n\nFor resume bullet (condensed STAR):\n\"Revitalized underperforming sales team through training program and commission restructure, improving quota attainment from 65% to 92% and generating $1.8M additional revenue\"\n\n### 3. CAR Method (Alternative to STAR)\n\n**Structure:**\n- **C**hallenge: What problem existed?\n- **A**ction: What did you do about it?\n- **R**esult: What happened?\n\n**Example:**\n\n\"Reduced customer churn (C) by implementing proactive outreach program (A), retaining 85% of at-risk accounts worth $500K ARR (R)\"\n\n## Power Verbs by Category\n\n### Leadership & Management\n- Led, Directed, Managed, Supervised, Coordinated\n- Spearheaded, Orchestrated, Oversaw, Championed, Mentored\n\n### Achievement & Success\n- Achieved, Delivered, Exceeded, Surpassed, Attained\n- Secured, Won, Earned, Captured, Clinched\n\n### Growth & Improvement\n- Grew, Increased, Boosted, Expanded, Scaled\n- Elevated, Amplified, Maximized, Accelerated, Doubled\n\n### Creation & Innovation\n- Created, Developed, Designed, Built, Launched\n- Pioneered, Established, Founded, Introduced, Originated\n\n### Optimization & Efficiency\n- Streamlined, Optimized, Enhanced, Improved, Revitalized\n- Transformed, Restructured, Modernized, Automated, Simplified\n\n### Analysis & Strategy\n- Analyzed, Assessed, Evaluated, Identified, Diagnosed\n- Researched, Investigated, Examined, Audited, Forecasted\n\n### Collaboration & Communication\n- Collaborated, Partnered, Facilitated, Coordinated, United\n- Presented, Communicated, Negotiated, Influenced, Persuaded\n\n### Problem-Solving\n- Resolved, Solved, Troubleshot, Rectified, Debugged\n- Eliminated, Reduced, Mitigated, Prevented, Corrected\n\n## Quantification Strategies\n\nEvery bullet should have at least ONE number. Here's how to find metrics:\n\n### Types of Metrics to Include\n\n**1. Money**\n- Revenue generated: \"$2M in new revenue\"\n- Money saved: \"Reduced costs by $50K annually\"\n- Budget managed: \"Managed $5M project budget\"\n- Deal size: \"Closed 3 enterprise deals worth $500K\"\n\n**2. Percentages**\n- Growth: \"Increased conversion rate by 45%\"\n- Improvement: \"Reduced error rate by 60%\"\n- Efficiency: \"Decreased processing time by 30%\"\n- Quality: \"Improved accuracy from 85% to 98%\"\n\n**3. Time**\n- Speed: \"Reduced load time from 8s to 2s\"\n- Frequency: \"Delivered weekly reports to 50+ stakeholders\"\n- Duration: \"Completed 6-month project in 4 months\"\n- Saved time: \"Automated process, saving team 10 hours\u002Fweek\"\n\n**4. Scale\u002FVolume**\n- People: \"Led team of 15\", \"Trained 50+ employees\"\n- Projects: \"Managed 8 concurrent initiatives\"\n- Customers: \"Served 500+ enterprise clients\"\n- Users: \"Built product used by 100K+ daily active users\"\n\n**5. Comparison\u002FBefore-After**\n- \"Increased from X to Y\"\n- \"Reduced from X to Y\"\n- \"Grew from X to Y\"\n\n### When You Don't Have Exact Numbers\n\nUse estimation strategies:\n\n**Approximate with ~**\n\"Improved performance by ~40%\"\n\n**Use ranges**\n\"Managed team of 8-12 people\"\n\"Generated $50K-$75K in monthly revenue\"\n\n**Use conservative estimates**\nIf you think it was 60%, say 50%\nIf you saved 100 hours, say 75 hours\n\n**Quantify inputs if outputs unknown**\nCan't measure revenue? Quantify activities:\n- \"Conducted 30+ customer interviews\"\n- \"Analyzed 500+ data points\"\n- \"Created 20+ marketing campaigns\"\n\n**Find related metrics**\nCan't measure conversion? Measure traffic, engagement, or other funnel metrics\n\n## Industry-Specific Bullet Examples\n\n### Software Engineering\n\n❌ WEAK:\n- Wrote code for new features\n- Fixed bugs in production\n- Worked with product team\n\n✅ STRONG:\n- Architected authentication microservice serving 500K+ daily active users, reducing login latency by 60% (from 5s to 2s)\n- Resolved 50+ critical production bugs over 6 months, improving system uptime from 97.2% to 99.8%\n- Collaborated with product team to deliver 12 features ahead of schedule, resulting in 25% increase in user engagement\n\n### Product Management\n\n❌ WEAK:\n- Managed product roadmap\n- Worked with stakeholders\n- Launched new features\n\n✅ STRONG:\n- Defined and executed product roadmap for $10M ARR product, prioritizing 50+ feature requests from 200+ customers\n- Facilitated weekly stakeholder meetings with engineering, design, and executive teams to align on strategic priorities\n- Launched 8 major features in 12 months, driving 40% increase in customer retention and $2M additional revenue\n\n### Sales\n\n❌ WEAK:\n- Met with clients\n- Closed deals\n- Exceeded quota\n\n✅ STRONG:\n- Generated $3.2M in new business revenue by closing 15 enterprise deals, achieving 142% of annual quota\n- Managed sales cycle for 50+ prospects simultaneously, maintaining 35% close rate (company average: 22%)\n- Exceeded quarterly quota 8 consecutive quarters, ranking #2 out of 45 sales reps nationwide\n\n### Marketing\n\n❌ WEAK:\n- Created marketing campaigns\n- Managed social media\n- Analyzed campaign performance\n\n✅ STRONG:\n- Launched 12 multi-channel campaigns generating $500K in attributed revenue and 2,500+ qualified leads\n- Grew LinkedIn audience by 400% (3K to 15K followers) through thought leadership content strategy, resulting in 200+ inbound demo requests\n- Analyzed campaign performance across 8 channels using Google Analytics, identifying 3 top-performing channels responsible for 75% of conversions\n\n### Customer Success\n\n❌ WEAK:\n- Helped customers with problems\n- Managed customer accounts\n- Conducted onboarding sessions\n\n✅ STRONG:\n- Maintained 95% customer retention rate across portfolio of 50 enterprise accounts representing $4M ARR\n- Resolved 40+ customer issues weekly with average response time of 2 hours, achieving 4.9\u002F5 CSAT score\n- Delivered 25+ onboarding sessions for new customers, achieving 90% product adoption rate within first 30 days\n\n### Data Analysis\n\n❌ WEAK:\n- Analyzed data\n- Created reports\n- Made recommendations\n\n✅ STRONG:\n- Analyzed 500K+ transaction records to identify $2M revenue opportunity, presented findings to C-suite resulting in new product line\n- Built automated reporting dashboard in Tableau reducing manual reporting time by 15 hours\u002Fweek for team of 8\n- Developed predictive model with 85% accuracy for customer churn, enabling proactive retention campaigns that saved $500K ARR\n\n### Operations\u002FProject Management\n\n❌ WEAK:\n- Managed projects\n- Coordinated with teams\n- Tracked progress\n\n✅ STRONG:\n- Led 8 cross-functional projects simultaneously with 100% on-time delivery rate and zero budget overruns across $5M portfolio\n- Coordinated efforts across engineering, design, and marketing teams (30+ people) to launch product ahead of schedule\n- Implemented project tracking system reducing status meeting time by 50% and improving visibility for 15+ stakeholders\n\n## Common Bullet Writing Mistakes\n\n### Mistake 1: Passive Language\n❌ \"Was responsible for...\"\n❌ \"Helped with...\"\n❌ \"Assisted in...\"\n❌ \"Participated in...\"\n\n✅ Use active verbs: Led, Created, Delivered, Achieved\n\n### Mistake 2: No Metrics\n❌ \"Improved website performance\"\n✅ \"Improved website load time by 60% (8s to 3.2s)\"\n\n❌ \"Managed large team\"\n✅ \"Led cross-functional team of 25 across 4 departments\"\n\n### Mistake 3: Job Duties Instead of Achievements\n❌ \"Responsible for customer support\"\n✅ \"Resolved 50+ tickets daily with 98% customer satisfaction score\"\n\n❌ \"Managed social media accounts\"\n✅ \"Grew social media following by 300% (10K to 40K) in 8 months\"\n\n### Mistake 4: Too Vague\n❌ \"Worked with stakeholders\"\n✅ \"Facilitated weekly meetings with 15+ stakeholders across engineering, product, and executive teams\"\n\n❌ \"Improved processes\"\n✅ \"Streamlined approval workflow, reducing cycle time from 10 to 4 days (60% improvement)\"\n\n### Mistake 5: Too Long\n❌ \"Was responsible for managing and overseeing all aspects of the customer success function including onboarding, training, support, and retention for a portfolio of enterprise clients...\"\n\n✅ \"Led customer success for 50 enterprise clients ($3M ARR), achieving 95% retention rate\"\n\n**Rule: Keep bullets to 1-2 lines maximum**\n\n## Bullet Writing Process\n\n### Step 1: Start with the Weak Bullet\n```\nOriginal: \"Managed social media\"\n```\n\n### Step 2: Ask Clarifying Questions\n- What platforms?\n- How many followers?\n- What growth did you achieve?\n- What specific actions did you take?\n- What business impact resulted?\n\n### Step 3: Gather Information\n- Platforms: Instagram, LinkedIn\n- Started: 5K followers\n- Ended: 18K followers  \n- Actions: Daily content calendar, influencer partnerships\n- Impact: 200 leads generated\n\n### Step 4: Apply Formula\nUsing X-Y-Z:\n\"Grew Instagram and LinkedIn following by 260% (5K to 18K) by implementing daily content calendar and 15 influencer partnerships, generating 200+ qualified leads\"\n\n### Step 5: Optimize Length\nIf too long, prioritize most impressive metrics:\n\"Grew social media audience by 260% (5K to 18K followers) through content strategy and influencer partnerships, generating 200+ leads\"\n\n## Bullet Strength Checklist\n\nEvery bullet should have:\n- ✅ Strong action verb (avoid \"responsible for\", \"helped\")\n- ✅ At least one number\u002Fmetric\n- ✅ Specific outcome or result\n- ✅ Context of scale (team size, budget, users, etc.)\n- ✅ 1-2 lines maximum\n- ✅ Reads as an achievement, not a duty\n- ✅ Relevant to target role\n\n## Output Format\n\nWhen rewriting bullets, provide:\n\n```markdown\n## BULLET IMPROVEMENTS\n\n### Original Bullet #1:\n\"Managed customer accounts\"\n\n### Issues:\n- Passive language (\"managed\")\n- No metrics\n- Vague (what does \"managed\" mean?)\n- No results shown\n\n### Improved Version:\n\"Grew portfolio of 40 enterprise accounts from $2M to $3.5M ARR (75% growth) through quarterly business reviews and proactive upselling strategy\"\n\n### What Changed:\n- Added scale (40 accounts)\n- Added growth metric (75%, $2M to $3.5M)\n- Specified actions (QBRs, upselling)\n- Shows business impact (revenue growth)\n\n---\n\n### Original Bullet #2:\n[Continue for each bullet...]\n```\n\n## Special Situations\n\n### For Entry-Level\u002FRecent Graduates\nFocus on:\n- Academic projects with real impact\n- Internship achievements\n- Relevant coursework projects\n- Volunteer work with quantifiable results\n- Club leadership with metrics\n\nExample:\n\"Led university marketing club of 50 members, organizing 8 events attended by 300+ students and securing $10K in corporate sponsorships\"\n\n### For Career Changers\nFocus on:\n- Transferable skills\n- Reframe old experience for new industry\n- Highlight relevant projects\u002Fside work\n- Emphasize learning and adaptation\n\nExample:\n\"Managed cross-functional teams of 15 (traditional retail) → can become:\n\"Led cross-functional teams of 15 across operations, merchandising, and customer experience, coordinating workflows and achieving 100% project completion rate\"\n\n### For Gaps in Employment\nFocus on:\n- Freelance\u002Fconsulting work\n- Volunteer achievements\n- Side projects\n- Professional development\n\nDon't draw attention to gaps, just fill space with relevant achievements.\n\n## Implementation Checklist\n\nFor each resume bullet:\n1. ✅ Identify weak verb → Replace with power verb\n2. ✅ Check for metrics → Add at least one number\n3. ✅ Verify it shows result → Add outcome\u002Fimpact\n4. ✅ Confirm specificity → Remove vague language\n5. ✅ Test length → Keep to 1-2 lines\n6. ✅ Read aloud → Ensure it sounds natural\n7. ✅ Verify relevance → Aligns with target role\n","# Resume Bullet Writer\n\n## When to Use This Skill\n\nUse this skill when the user wants to:\n- Write or improve resume bullet points\n- Transform weak descriptions into strong achievements\n- Add metrics and quantifiable results\n- Make their experience more compelling\n- Mentions: \"improve my bullets\", \"make my resume stronger\", \"quantify my achievements\", \"results-driven\"\n\nAlso use when you see weak bullets that need improvement (passive language, no metrics, vague descriptions).\n\n## Core Capabilities\n\n- Transform weak bullet points into achievement-focused statements\n- Apply STAR method and X-Y-Z formula\n- Add quantifiable metrics and results\n- Use strong action verbs\n- Tailor bullets to specific roles\u002Findustries\n- Ensure every bullet shows impact, not just duties\n\n## The Bullet Point Problem\n\nMost resumes have weak bullets that list job duties instead of achievements:\n\n❌ **Weak Bullets (What NOT to do):**\n- \"Responsible for managing team\"\n- \"Helped with customer service\"\n- \"Worked on improving processes\"\n- \"Assisted with projects\"\n\nThese are passive, vague, and don't show impact or results.\n\n✅ **Strong Bullets (What TO do):**\n- \"Led cross-functional team of 12 to deliver $2M product, increasing revenue by 35%\"\n- \"Resolved 50+ customer issues daily, improving satisfaction scores from 3.2 to 4.8\u002F5\"\n- \"Streamlined approval process, reducing cycle time by 40% (from 10 to 6 days)\"\n- \"Managed portfolio of 8 concurrent projects with 100% on-time delivery rate\"\n\nThese are active, specific, and quantify the impact.\n\n## Core Frameworks\n\n### 1. The X-Y-Z Formula (Google Method)\n\n**Structure:** \"Accomplished [X] as measured by [Y] by doing [Z]\"\n\n- X = What you achieved\n- Y = How you measured it\n- Z = What actions you took\n\n**Examples:**\n\n```\n❌ BEFORE: \"Managed social media accounts\"\n\n✅ AFTER: \"Grew Instagram following by 250% (5K to 17.5K) by implementing daily content calendar and influencer partnerships\"\n\nX = Grew Instagram following by 250%\nY = 5K to 17.5K followers\nZ = Daily content calendar + influencer partnerships\n```\n\n```\n❌ BEFORE: \"Improved customer service\"\n\n✅ AFTER: \"Increased customer satisfaction scores by 40% (3.2 to 4.5\u002F5) by redesigning support ticketing system and training 15 agents\"\n\nX = Increased customer satisfaction by 40%\nY = 3.2 to 4.5 out of 5\nZ = Redesigned ticketing system + trained agents\n```\n\n### 2. STAR Method\n\n**Structure:**\n- **S**ituation: What was the context?\n- **T**ask: What needed to be done?\n- **A**ction: What did YOU specifically do?\n- **R**esult: What was the measurable outcome?\n\n**Example:**\n\nFull STAR story:\n\"Inherited underperforming sales team (S) with 65% quota attainment. Tasked with improving performance within Q1 (T). Implemented new training program and revised commission structure (A). Achieved 92% quota attainment by Q2, generating $1.8M additional revenue (R).\"\n\nFor resume bullet (condensed STAR):\n\"Revitalized underperforming sales team through training program and commission restructure, improving quota attainment from 65% to 92% and generating $1.8M additional revenue\"\n\n### 3. CAR Method (Alternative to STAR)\n\n**Structure:**\n- **C**hallenge: What problem existed?\n- **A**ction: What did you do about it?\n- **R**esult: What happened?\n\n**Example:**\n\n\"Reduced customer churn (C) by implementing proactive outreach program (A), retaining 85% of at-risk accounts worth $500K ARR (R)\"\n\n## Power Verbs by Category\n\n### Leadership & Management\n- Led, Directed, Managed, Supervised, Coordinated\n- Spearheaded, Orchestrated, Oversaw, Championed, Mentored\n\n### Achievement & Success\n- Achieved, Delivered, Exceeded, Surpassed, Attained\n- Secured, Won, Earned, Captured, Clinched\n\n### Growth & Improvement\n- Grew, Increased, Boosted, Expanded, Scaled\n- Elevated, Amplified, Maximized, Accelerated, Doubled\n\n### Creation & Innovation\n- Created, Developed, Designed, Built, Launched\n- Pioneered, Established, Founded, Introduced, Originated\n\n### Optimization & Efficiency\n- Streamlined, Optimized, Enhanced, Improved, Revitalized\n- Transformed, Restructured, Modernized, Automated, Simplified\n\n### Analysis & Strategy\n- Analyzed, Assessed, Evaluated, Identified, Diagnosed\n- Researched, Investigated, Examined, Audited, Forecasted\n\n### Collaboration & Communication\n- Collaborated, Partnered, Facilitated, Coordinated, United\n- Presented, Communicated, Negotiated, Influenced, Persuaded\n\n### Problem-Solving\n- Resolved, Solved, Troubleshot, Rectified, Debugged\n- Eliminated, Reduced, Mitigated, Prevented, Corrected\n\n## Quantification Strategies\n\nEvery bullet should have at least ONE number. Here's how to find metrics:\n\n### Types of Metrics to Include\n\n**1. Money**\n- Revenue generated: \"$2M in new revenue\"\n- Money saved: \"Reduced costs by $50K annually\"\n- Budget managed: \"Managed $5M project budget\"\n- Deal size: \"Closed 3 enterprise deals worth $500K\"\n\n**2. Percentages**\n- Growth: \"Increased conversion rate by 45%\"\n- Improvement: \"Reduced error rate by 60%\"\n- Efficiency: \"Decreased processing time by 30%\"\n- Quality: \"Improved accuracy from 85% to 98%\"\n\n**3. Time**\n- Speed: \"Reduced load time from 8s to 2s\"\n- Frequency: \"Delivered weekly reports to 50+ stakeholders\"\n- Duration: \"Completed 6-month project in 4 months\"\n- Saved time: \"Automated process, saving team 10 hours\u002Fweek\"\n\n**4. Scale\u002FVolume**\n- People: \"Led team of 15\", \"Trained 50+ employees\"\n- Projects: \"Managed 8 concurrent initiatives\"\n- Customers: \"Served 500+ enterprise clients\"\n- Users: \"Built product used by 100K+ daily active users\"\n\n**5. Comparison\u002FBefore-After**\n- \"Increased from X to Y\"\n- \"Reduced from X to Y\"\n- \"Grew from X to Y\"\n\n### When You Don't Have Exact Numbers\n\nUse estimation strategies:\n\n**Approximate with ~**\n\"Improved performance by ~40%\"\n\n**Use ranges**\n\"Managed team of 8-12 people\"\n\"Generated $50K-$75K in monthly revenue\"\n\n**Use conservative estimates**\nIf you think it was 60%, say 50%\nIf you saved 100 hours, say 75 hours\n\n**Quantify inputs if outputs unknown**\nCan't measure revenue? Quantify activities:\n- \"Conducted 30+ customer interviews\"\n- \"Analyzed 500+ data points\"\n- \"Created 20+ marketing campaigns\"\n\n**Find related metrics**\nCan't measure conversion? Measure traffic, engagement, or other funnel metrics\n\n## Industry-Specific Bullet Examples\n\n### Software Engineering\n\n❌ WEAK:\n- Wrote code for new features\n- Fixed bugs in production\n- Worked with product team\n\n✅ STRONG:\n- Architected authentication microservice serving 500K+ daily active users, reducing login latency by 60% (from 5s to 2s)\n- Resolved 50+ critical production bugs over 6 months, improving system uptime from 97.2% to 99.8%\n- Collaborated with product team to deliver 12 features ahead of schedule, resulting in 25% increase in user engagement\n\n### Product Management\n\n❌ WEAK:\n- Managed product roadmap\n- Worked with stakeholders\n- Launched new features\n\n✅ STRONG:\n- Defined and executed product roadmap for $10M ARR product, prioritizing 50+ feature requests from 200+ customers\n- Facilitated weekly stakeholder meetings with engineering, design, and executive teams to align on strategic priorities\n- Launched 8 major features in 12 months, driving 40% increase in customer retention and $2M additional revenue\n\n### Sales\n\n❌ WEAK:\n- Met with clients\n- Closed deals\n- Exceeded quota\n\n✅ STRONG:\n- Generated $3.2M in new business revenue by closing 15 enterprise deals, achieving 142% of annual quota\n- Managed sales cycle for 50+ prospects simultaneously, maintaining 35% close rate (company average: 22%)\n- Exceeded quarterly quota 8 consecutive quarters, ranking #2 out of 45 sales reps nationwide\n\n### Marketing\n\n❌ WEAK:\n- Created marketing campaigns\n- Managed social media\n- Analyzed campaign performance\n\n✅ STRONG:\n- Launched 12 multi-channel campaigns generating $500K in attributed revenue and 2,500+ qualified leads\n- Grew LinkedIn audience by 400% (3K to 15K followers) through thought leadership content strategy, resulting in 200+ inbound demo requests\n- Analyzed campaign performance across 8 channels using Google Analytics, identifying 3 top-performing channels responsible for 75% of conversions\n\n### Customer Success\n\n❌ WEAK:\n- Helped customers with problems\n- Managed customer accounts\n- Conducted onboarding sessions\n\n✅ STRONG:\n- Maintained 95% customer retention rate across portfolio of 50 enterprise accounts representing $4M ARR\n- Resolved 40+ customer issues weekly with average response time of 2 hours, achieving 4.9\u002F5 CSAT score\n- Delivered 25+ onboarding sessions for new customers, achieving 90% product adoption rate within first 30 days\n\n### Data Analysis\n\n❌ WEAK:\n- Analyzed data\n- Created reports\n- Made recommendations\n\n✅ STRONG:\n- Analyzed 500K+ transaction records to identify $2M revenue opportunity, presented findings to C-suite resulting in new product line\n- Built automated reporting dashboard in Tableau reducing manual reporting time by 15 hours\u002Fweek for team of 8\n- Developed predictive model with 85% accuracy for customer churn, enabling proactive retention campaigns that saved $500K ARR\n\n### Operations\u002FProject Management\n\n❌ WEAK:\n- Managed projects\n- Coordinated with teams\n- Tracked progress\n\n✅ STRONG:\n- Led 8 cross-functional projects simultaneously with 100% on-time delivery rate and zero budget overruns across $5M portfolio\n- Coordinated efforts across engineering, design, and marketing teams (30+ people) to launch product ahead of schedule\n- Implemented project tracking system reducing status meeting time by 50% and improving visibility for 15+ stakeholders\n\n## Common Bullet Writing Mistakes\n\n### Mistake 1: Passive Language\n❌ \"Was responsible for...\"\n❌ \"Helped with...\"\n❌ \"Assisted in...\"\n❌ \"Participated in...\"\n\n✅ Use active verbs: Led, Created, Delivered, Achieved\n\n### Mistake 2: No Metrics\n❌ \"Improved website performance\"\n✅ \"Improved website load time by 60% (8s to 3.2s)\"\n\n❌ \"Managed large team\"\n✅ \"Led cross-functional team of 25 across 4 departments\"\n\n### Mistake 3: Job Duties Instead of Achievements\n❌ \"Responsible for customer support\"\n✅ \"Resolved 50+ tickets daily with 98% customer satisfaction score\"\n\n❌ \"Managed social media accounts\"\n✅ \"Grew social media following by 300% (10K to 40K) in 8 months\"\n\n### Mistake 4: Too Vague\n❌ \"Worked with stakeholders\"\n✅ \"Facilitated weekly meetings with 15+ stakeholders across engineering, product, and executive teams\"\n\n❌ \"Improved processes\"\n✅ \"Streamlined approval workflow, reducing cycle time from 10 to 4 days (60% improvement)\"\n\n### Mistake 5: Too Long\n❌ \"Was responsible for managing and overseeing all aspects of the customer success function including onboarding, training, support, and retention for a portfolio of enterprise clients...\"\n\n✅ \"Led customer success for 50 enterprise clients ($3M ARR), achieving 95% retention rate\"\n\n**Rule: Keep bullets to 1-2 lines maximum**\n\n## Bullet Writing Process\n\n### Step 1: Start with the Weak Bullet\n```\nOriginal: \"Managed social media\"\n```\n\n### Step 2: Ask Clarifying Questions\n- What platforms?\n- How many followers?\n- What growth did you achieve?\n- What specific actions did you take?\n- What business impact resulted?\n\n### Step 3: Gather Information\n- Platforms: Instagram, LinkedIn\n- Started: 5K followers\n- Ended: 18K followers  \n- Actions: Daily content calendar, influencer partnerships\n- Impact: 200 leads generated\n\n### Step 4: Apply Formula\nUsing X-Y-Z:\n\"Grew Instagram and LinkedIn following by 260% (5K to 18K) by implementing daily content calendar and 15 influencer partnerships, generating 200+ qualified leads\"\n\n### Step 5: Optimize Length\nIf too long, prioritize most impressive metrics:\n\"Grew social media audience by 260% (5K to 18K followers) through content strategy and influencer partnerships, generating 200+ leads\"\n\n## Bullet Strength Checklist\n\nEvery bullet should have:\n- ✅ Strong action verb (avoid \"responsible for\", \"helped\")\n- ✅ At least one number\u002Fmetric\n- ✅ Specific outcome or result\n- ✅ Context of scale (team size, budget, users, etc.)\n- ✅ 1-2 lines maximum\n- ✅ Reads as an achievement, not a duty\n- ✅ Relevant to target role\n\n## Output Format\n\nWhen rewriting bullets, provide:\n\n```markdown\n## BULLET IMPROVEMENTS\n\n### Original Bullet #1:\n\"Managed customer accounts\"\n\n### Issues:\n- Passive language (\"managed\")\n- No metrics\n- Vague (what does \"managed\" mean?)\n- No results shown\n\n### Improved Version:\n\"Grew portfolio of 40 enterprise accounts from $2M to $3.5M ARR (75% growth) through quarterly business reviews and proactive upselling strategy\"\n\n### What Changed:\n- Added scale (40 accounts)\n- Added growth metric (75%, $2M to $3.5M)\n- Specified actions (QBRs, upselling)\n- Shows business impact (revenue growth)\n\n---\n\n### Original Bullet #2:\n[Continue for each bullet...]\n```\n\n## Special Situations\n\n### For Entry-Level\u002FRecent Graduates\nFocus on:\n- Academic projects with real impact\n- Internship achievements\n- Relevant coursework projects\n- Volunteer work with quantifiable results\n- Club leadership with metrics\n\nExample:\n\"Led university marketing club of 50 members, organizing 8 events attended by 300+ students and securing $10K in corporate sponsorships\"\n\n### For Career Changers\nFocus on:\n- Transferable skills\n- Reframe old experience for new industry\n- Highlight relevant projects\u002Fside work\n- Emphasize learning and adaptation\n\nExample:\n\"Managed cross-functional teams of 15 (traditional retail) → can become:\n\"Led cross-functional teams of 15 across operations, merchandising, and customer experience, coordinating workflows and achieving 100% project completion rate\"\n\n### For Gaps in Employment\nFocus on:\n- Freelance\u002Fconsulting work\n- Volunteer achievements\n- Side projects\n- Professional development\n\nDon't draw attention to gaps, just fill space with relevant achievements.\n\n## Implementation Checklist\n\nFor each resume bullet:\n1. ✅ Identify weak verb → Replace with power verb\n2. ✅ Check for metrics → Add at least one number\n3. ✅ Verify it shows result → Add outcome\u002Fimpact\n4. ✅ Confirm specificity → Remove vague language\n5. ✅ Test length → Keep to 1-2 lines\n6. ✅ Read aloud → Ensure it sounds natural\n7. ✅ Verify relevance → Aligns with target role\n",{"name":5,"description":7},"main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fcareer\u002Fresume-bullet-writer",3963,"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-15 01:32:48",{"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-bullet-writer",{"tool":60,"command":61},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill resume-bullet-writer",{"tool":63,"command":64},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill resume-bullet-writer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcareer\u002Fresume-bullet-writer\u002FSKILL.md",true,[68],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"README.md","REFERENCE","参考文档",8102,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fgame-changing-features\u002FREADME.md",[75,104,131,162,197,221],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":86,"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",[81],{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[87,88,89,90,91,92,93,94,30,38,95,35,96,97,98,99,100,101,102,103],"scoring","pool","wealthville pool scoring","liquidity","which","for","exit","now","reduce","record","track","verdict","evm","solana","how","public","look",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":111,"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",[110],{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},[112,113,114,115,116,117,118,119,120,121,122,38,123,124,125,126,127,128,129,130],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":144,"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",[137,140,141],{"categoryNo":138,"categoryName":139,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},{"categoryNo":142,"categoryName":143,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000033","数据分析师",[145,146,147,148,149,150,151,92,152,153,154,155,156,157,158,30,159,160,38,161],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":166,"licenseFileUrl":167,"sourceHtmlUrl":168,"categories":169,"keywords":173,"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",[170],{"categoryNo":171,"categoryName":172,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000009","前端开发",[174,175,176,177,178,179,180,181,182,183,184,185,186,187,188,189,190,191,192,193,194,195,92,196],"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":198,"name":199,"nameZh":6,"description":200,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":166,"licenseFileUrl":201,"sourceHtmlUrl":202,"categories":203,"keywords":208,"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",[204,207],{"categoryNo":205,"categoryName":206,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":171,"categoryName":172,"taxonomyType":84,"taxonomyTypeDesc":85},[209,210,211,212,213,175,214,184,185,215,216,217,218,92,219,35,220],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":222,"name":223,"nameZh":6,"description":224,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":166,"licenseFileUrl":225,"sourceHtmlUrl":226,"categories":227,"keywords":235,"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",[228,231,232],{"categoryNo":229,"categoryName":230,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},{"categoryNo":233,"categoryName":234,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000036","内容创作者",[236,237,238,239,240,241,242,243,177,244,187,123,245,246,247,248,249,157,250,38,251,252,253,254,255,101,256],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]