resume-bullet-writer

paramchoudhary/resumeskills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/paramchoudhary/resumeskills --skill resume-bullet-writer
0 commentsdiscussion
summary

Use this skill when the user wants to:

skill.md

Resume Bullet Writer

When to Use This Skill

Use this skill when the user wants to:

  • Write or improve resume bullet points
  • Transform weak descriptions into strong achievements
  • Add metrics and quantifiable results
  • Make their experience more compelling
  • Mentions: "improve my bullets", "make my resume stronger", "quantify my achievements", "results-driven"

Also use when you see weak bullets that need improvement (passive language, no metrics, vague descriptions).

Core Capabilities

  • Transform weak bullet points into achievement-focused statements
  • Apply STAR method and X-Y-Z formula
  • Add quantifiable metrics and results
  • Use strong action verbs
  • Tailor bullets to specific roles/industries
  • Ensure every bullet shows impact, not just duties

The Bullet Point Problem

Most resumes have weak bullets that list job duties instead of achievements:

Weak Bullets (What NOT to do):

  • "Responsible for managing team"
  • "Helped with customer service"
  • "Worked on improving processes"
  • "Assisted with projects"

These are passive, vague, and don't show impact or results.

Strong Bullets (What TO do):

  • "Led cross-functional team of 12 to deliver $2M product, increasing revenue by 35%"
  • "Resolved 50+ customer issues daily, improving satisfaction scores from 3.2 to 4.8/5"
  • "Streamlined approval process, reducing cycle time by 40% (from 10 to 6 days)"
  • "Managed portfolio of 8 concurrent projects with 100% on-time delivery rate"

These are active, specific, and quantify the impact.

Core Frameworks

1. The X-Y-Z Formula (Google Method)

Structure: "Accomplished [X] as measured by [Y] by doing [Z]"

  • X = What you achieved
  • Y = How you measured it
  • Z = What actions you took

Examples:

❌ BEFORE: "Managed social media accounts"

✅ AFTER: "Grew Instagram following by 250% (5K to 17.5K) by implementing daily content calendar and influencer partnerships"

X = Grew Instagram following by 250%
Y = 5K to 17.5K followers
Z = Daily content calendar + influencer partnerships
❌ BEFORE: "Improved customer service"

✅ AFTER: "Increased customer satisfaction scores by 40% (3.2 to 4.5/5) by redesigning support ticketing system and training 15 agents"

X = Increased customer satisfaction by 40%
Y = 3.2 to 4.5 out of 5
Z = Redesigned ticketing system + trained agents

2. STAR Method

Structure:

  • Situation: What was the context?
  • Task: What needed to be done?
  • Action: What did YOU specifically do?
  • Result: What was the measurable outcome?

Example:

Full STAR story: "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)."

For resume bullet (condensed STAR): "Revitalized underperforming sales team through training program and commission restructure, improving quota attainment from 65% to 92% and generating $1.8M additional revenue"

3. CAR Method (Alternative to STAR)

Structure:

  • Challenge: What problem existed?
  • Action: What did you do about it?
  • Result: What happened?

Example:

"Reduced customer churn (C) by implementing proactive outreach program (A), retaining 85% of at-risk accounts worth $500K ARR (R)"

Power Verbs by Category

Leadership & Management

  • Led, Directed, Managed, Supervised, Coordinated
  • Spearheaded, Orchestrated, Oversaw, Championed, Mentored

Achievement & Success

  • Achieved, Delivered, Exceeded, Surpassed, Attained
  • Secured, Won, Earned, Captured, Clinched

Growth & Improvement

  • Grew, Increased, Boosted, Expanded, Scaled
  • Elevated, Amplified, Maximized, Accelerated, Doubled

Creation & Innovation

  • Created, Developed, Designed, Built, Launched
  • Pioneered, Established, Founded, Introduced, Originated

Optimization & Efficiency

  • Streamlined, Optimized, Enhanced, Improved, Revitalized
  • Transformed, Restructured, Modernized, Automated, Simplified

Analysis & Strategy

  • Analyzed, Assessed, Evaluated, Identified, Diagnosed
  • Researched, Investigated, Examined, Audited, Forecasted

Collaboration & Communication

  • Collaborated, Partnered, Facilitated, Coordinated, United
  • Presented, Communicated, Negotiated, Influenced, Persuaded

Problem-Solving

  • Resolved, Solved, Troubleshot, Rectified, Debugged
  • Eliminated, Reduced, Mitigated, Prevented, Corrected

Quantification Strategies

Every bullet should have at least ONE number. Here's how to find metrics:

Types of Metrics to Include

1. Money

  • Revenue generated: "$2M in new revenue"
  • Money saved: "Reduced costs by $50K annually"
  • Budget managed: "Managed $5M project budget"
  • Deal size: "Closed 3 enterprise deals worth $500K"

2. Percentages

  • Growth: "Increased conversion rate by 45%"
  • Improvement: "Reduced error rate by 60%"
  • Efficiency: "Decreased processing time by 30%"
  • Quality: "Improved accuracy from 85% to 98%"

3. Time

  • Speed: "Reduced load time from 8s to 2s"
  • Frequency: "Delivered weekly reports to 50+ stakeholders"
  • Duration: "Completed 6-month project in 4 months"
  • Saved time: "Automated process, saving team 10 hours/week"

4. Scale/Volume

  • People: "Led team of 15", "Trained 50+ employees"
  • Projects: "Managed 8 concurrent initiatives"
  • Customers: "Served 500+ enterprise clients"
  • Users: "Built product used by 100K+ daily active users"

5. Comparison/Before-After

  • "Increased from X to Y"
  • "Reduced from X to Y"
  • "Grew from X to Y"

When You Don't Have Exact Numbers

Use estimation strategies:

Approximate with ~ "Improved performance by ~40%"

Use ranges "Managed team of 8-12 people" "Generated $50K-$75K in monthly revenue"

Use conservative estimates If you think it was 60%, say 50% If you saved 100 hours, say 75 hours

Quantify inputs if outputs unknown Can't measure revenue? Quantify activities:

  • "Conducted 30+ customer interviews"
  • "Analyzed 500+ data points"
  • "Created 20+ marketing campaigns"

Find related metrics Can't measure conversion? Measure traffic, engagement, or other funnel metrics

Industry-Specific Bullet Examples

Software Engineering

❌ WEAK:

  • Wrote code for new features
  • Fixed bugs in production
  • Worked with product team

✅ STRONG:

  • Architected authentication microservice serving 500K+ daily active users, reducing login latency by 60% (from 5s to 2s)
  • Resolved 50+ critical production bugs over 6 months, improving system uptime from 97.2% to 99.8%
  • Collaborated with product team to deliver 12 features ahead of schedule, resulting in 25% increase in user engagement

Product Management

❌ WEAK:

  • Managed product roadmap
  • Worked with stakeholders
  • Launched new features

✅ STRONG:

  • Defined and executed product roadmap for $10M ARR product, prioritizing 50+ feature requests from 200+ customers
  • Facilitated weekly stakeholder meetings with engineering, design, and executive teams to align on strategic priorities
  • Launched 8 major features in 12 months, driving 40% increase in customer retention and $2M additional revenue

Sales

❌ WEAK:

  • Met with clients
  • Closed deals
  • Exceeded quota

✅ STRONG:

  • Generated $3.2M in new business revenue by closing 15 enterprise deals, achieving 142% of annual quota
  • Managed sales cycle for 50+ prospects simultaneously, maintaining 35% close rate (company average: 22%)
  • Exceeded quarterly quota 8 consecutive quarters, ranking #2 out of 45 sales reps nationwide

Marketing

❌ WEAK:

  • Created marketing campaigns
  • Managed social media
  • Analyzed campaign performance

✅ STRONG:

  • Launched 12 multi-channel campaigns generating $500K in attributed revenue and 2,500+ qualified leads
  • Grew LinkedIn audience by 400% (3K to 15K followers) through thought leadership content strategy, resulting in 200+ inbound demo requests
  • Analyzed campaign performance across 8 channels using Google Analytics, identifying 3 top-performing channels responsible for 75% of conversions

Customer Success

❌ WEAK:

  • Helped customers with problems
  • Managed customer accounts
  • Conducted onboarding sessions

✅ STRONG:

  • Maintained 95% customer retention rate across portfolio of 50 enterprise accounts representing $4M ARR
  • Resolved 40+ customer issues weekly with average response time of 2 hours, achieving 4.9/5 CSAT score
  • Delivered 25+ onboarding sessions for new customers, achieving 90% product adoption rate within first 30 days

Data Analysis

❌ WEAK:

  • Analyzed data
  • Created reports
  • Made recommendations

✅ STRONG:

  • Analyzed 500K+ transaction records to identify $2M revenue opportunity, presented findings to C-suite resulting in new product line
  • Built automated reporting dashboard in Tableau reducing manual reporting time by 15 hours/week for team of 8
  • Developed predictive model with 85% accuracy for customer churn, enabling proactive retention campaigns that saved $500K ARR

Operations/Project Management

❌ WEAK:

  • Managed projects
  • Coordinated with teams
  • Tracked progress

✅ STRONG:

  • Led 8 cross-functional projects simultaneously with 100% on-time delivery rate and zero budget overruns across $5M portfolio
  • Coordinated efforts across engineering, design, and marketing teams (30+ people) to launch product ahead of schedule
  • Implemented project tracking system reducing status meeting time by 50% and improving visibility for 15+ stakeholders

Common Bullet Writing Mistakes

Mistake 1: Passive Language

❌ "Was responsible for..." ❌ "Helped with..." ❌ "Assisted in..." ❌ "Participated in..."

✅ Use active verbs: Led, Created, Delivered, Achieved

Mistake 2: No Metrics

❌ "Improved website performance" ✅ "Improved website load time by 60% (8s to 3.2s)"

❌ "Managed large team" ✅ "Led cross-functional team of 25 across 4 departments"

Mistake 3: Job Duties Instead of Achievements

❌ "Responsible for customer support" ✅ "Resolved 50+ tickets daily with 98% customer satisfaction score"

❌ "Managed social media accounts" ✅ "Grew social media following by 300% (10K to 40K) in 8 months"

Mistake 4: Too Vague

❌ "Worked with stakeholders" ✅ "Facilitated weekly meetings with 15+ stakeholders across engineering, product, and executive teams"

❌ "Improved processes" ✅ "Streamlined approval workflow, reducing cycle time from 10 to 4 days (60% improvement)"

Mistake 5: Too Long

❌ "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..."

✅ "Led customer success for 50 enterprise clients ($3M ARR), achieving 95% retention rate"

Rule: Keep bullets to 1-2 lines maximum

Bullet Writing Process

Step 1: Start with the Weak Bullet

Original: "Managed social media"

Step 2: Ask Clarifying Questions

  • What platforms?
  • How many followers?
  • What growth did you achieve?
  • What specific actions did you take?
  • What business impact resulted?

Step 3: Gather Information

  • Platforms: Instagram, LinkedIn
  • Started: 5K followers
  • Ended: 18K followers
  • Actions: Daily content calendar, influencer partnerships
  • Impact: 200 leads generated

Step 4: Apply Formula

Using X-Y-Z: "Grew Instagram and LinkedIn following by 260% (5K to 18K) by implementing daily content calendar and 15 influencer partnerships, generating 200+ qualified leads"

Step 5: Optimize Length

If too long, prioritize most impressive metrics: "Grew social media audience by 260% (5K to 18K followers) through content strategy and influencer partnerships, generating 200+ leads"

Bullet Strength Checklist

Every bullet should have:

  • ✅ Strong action verb (avoid "responsible for", "helped")
  • ✅ At least one number/metric
  • ✅ Specific outcome or result
  • ✅ Context of scale (team size, budget, users, etc.)
  • ✅ 1-2 lines maximum
  • ✅ Reads as an achievement, not a duty
  • ✅ Relevant to target role

Output Format

When rewriting bullets, provide:

## BULLET IMPROVEMENTS

### Original Bullet #1:
"Managed customer accounts"

### Issues:
- Passive language ("managed")
- No metrics
- Vague (what does "managed" mean?)
- No results shown

### Improved Version:
"Grew portfolio of 40 enterprise accounts from $2M to $3.5M ARR (75% growth) through quarterly business reviews and proactive upselling strategy"

### What Changed:
- Added scale (40 accounts)
- Added growth metric (75%, $2M to $3.5M)
- Specified actions (QBRs, upselling)
- Shows business impact (revenue growth)

---

### Original Bullet #2:
[Continue for each bullet...]

Special Situations

For Entry-Level/Recent Graduates

Focus on:

  • Academic projects with real impact
  • Internship achievements
  • Relevant coursework projects
  • Volunteer work with quantifiable results
  • Club leadership with metrics

Example: "Led university marketing club of 50 members, organizing 8 events attended by 300+ students and securing $10K in corporate sponsorships"

For Career Changers

Focus on:

  • Transferable skills
  • Reframe old experience for new industry
  • Highlight relevant projects/side work
  • Emphasize learning and adaptation

Example: "Managed cross-functional teams of 15 (traditional retail) → can become: "Led cross-functional teams of 15 across operations, merchandising, and customer experience, coordinating workflows and achieving 100% project completion rate"

For Gaps in Employment

Focus on:

  • Freelance/consulting work
  • Volunteer achievements
  • Side projects
  • Professional development

Don't draw attention to gaps, just fill space with relevant achievements.

Implementation Checklist

For each resume bullet:

  1. ✅ Identify weak verb → Replace with power verb
  2. ✅ Check for metrics → Add at least one number
  3. ✅ Verify it shows result → Add outcome/impact
  4. ✅ Confirm specificity → Remove vague language
  5. ✅ Test length → Keep to 1-2 lines
  6. ✅ Read aloud → Ensure it sounds natural
  7. ✅ Verify relevance → Aligns with target role
how to use resume-bullet-writer

How to use resume-bullet-writer on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add resume-bullet-writer
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/paramchoudhary/resumeskills --skill resume-bullet-writer

The skills CLI fetches resume-bullet-writer from GitHub repository paramchoudhary/resumeskills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/resume-bullet-writer

Reload or restart Cursor to activate resume-bullet-writer. Access the skill through slash commands (e.g., /resume-bullet-writer) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.445 reviews
  • Ganesh Mohane· Dec 28, 2024

    Registry listing for resume-bullet-writer matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Mia Abebe· Dec 28, 2024

    resume-bullet-writer reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Lucas Verma· Dec 24, 2024

    Registry listing for resume-bullet-writer matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Xiao Nasser· Dec 16, 2024

    resume-bullet-writer has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Valentina Robinson· Dec 16, 2024

    Useful defaults in resume-bullet-writer — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Ama Bansal· Dec 12, 2024

    resume-bullet-writer is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Rahul Santra· Nov 19, 2024

    Solid pick for teams standardizing on skills: resume-bullet-writer is focused, and the summary matches what you get after install.

  • Soo Okafor· Nov 19, 2024

    We added resume-bullet-writer from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Soo Kim· Nov 15, 2024

    Solid pick for teams standardizing on skills: resume-bullet-writer is focused, and the summary matches what you get after install.

  • Mateo Mensah· Nov 7, 2024

    I recommend resume-bullet-writer for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

showing 1-10 of 45

1 / 5