resume-cover-letter

jezweb/claude-skills · 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/jezweb/claude-skills --skill resume-cover-letter
0 commentsdiscussion
summary

Produces job application documents: a resume/CV, a cover letter, or both. Every output is tailored to a specific role at a specific company — generic documents are not useful.

skill.md

Resume and Cover Letter Writer

Produces job application documents: a resume/CV, a cover letter, or both. Every output is tailored to a specific role at a specific company — generic documents are not useful.

Before You Start

Gather these inputs. Ask for anything missing:

  1. Target role — job title, company name, and the job listing or description (paste or URL)
  2. Mode — "resume", "cover-letter", or "both"
  3. Region — AU/NZ, US, or UK (affects format, terminology, length expectations)
  4. Candidate background — current role, years of experience, key skills, education, career highlights
  5. Special circumstances (if any) — career change, employment gap, overqualified, underqualified, visa/relocation

If the user provides a job listing, extract the key requirements and tailor everything to match them. Mirror the language the listing uses for skills and responsibilities.


Resume / CV

Regional Format Differences

Element AU/NZ US UK
Name CV or resume (both accepted) Resume CV
Length 2-3 pages standard 1 page (<10 years exp), 2 max 2 pages standard
Photo No No No
Date of birth / age No No No
Nationality / visa Include if relevant (common in AU/NZ) No (discrimination risk) Include visa status if applicable
Referees "Available on request" is outdated — omit entirely, or list 2 if specifically requested Omit Omit
Address City/state only (no street) City/state only City only

Section Order

Adjust based on seniority and what sells the candidate best:

Entry-level / graduate (0-3 years):

  1. Contact details
  2. Professional summary (3-4 lines)
  3. Education
  4. Experience (internships, part-time, volunteer)
  5. Skills
  6. Certifications / projects

Mid-career (3-10 years):

  1. Contact details
  2. Professional summary
  3. Experience
  4. Skills
  5. Education
  6. Certifications

Senior / executive (10+ years):

  1. Contact details
  2. Executive summary
  3. Key achievements (optional highlight section)
  4. Experience
  5. Board / advisory roles (if applicable)
  6. Education
  7. Professional memberships

Writing Achievement Bullets

Use CAR format: Challenge (context/problem), Action (what you did), Result (measurable outcome).

Every bullet should answer: "So what? What changed because of this?"

Too generic:

Managed social media accounts and created content for the company.

Right approach (CAR):

Rebuilt the social media strategy for a stagnant B2B account (Challenge), shifting from product-focused posts to customer case studies with a consistent weekly publishing schedule (Action), growing LinkedIn engagement 340% and generating 12 qualified leads in the first quarter (Result).

Not every bullet needs hard numbers, but aim for at least 60% of bullets to include a measurable result. Acceptable result types:

  • Percentages (increased, reduced, improved by X%)
  • Dollar amounts (managed $X budget, saved $X, generated $X revenue)
  • Volume/scale (team of X, X users, X transactions per day)
  • Time (reduced from X weeks to Y days, delivered 2 weeks ahead of schedule)
  • Rankings/ratings (achieved #1, rated 4.8/5, top 10%)

When the user does not have specific numbers, ask if they can estimate. If not, use qualitative results: "significantly reduced", "consistently exceeded targets", "recognised by leadership for".

Action Verbs

Choose verbs that match the type of contribution:

Category Verbs
Leadership Led, directed, managed, oversaw, mentored, championed, established
Creation Developed, designed, built, launched, created, implemented, introduced
Improvement Increased, improved, streamlined, optimised, reduced, enhanced, modernised
Analysis Analysed, evaluated, assessed, identified, researched, investigated
Communication Presented, negotiated, facilitated, coordinated, advised, authored
Technical Engineered, automated, configured, deployed, integrated, migrated, architected

Avoid weak openers: "Responsible for", "Helped with", "Assisted in", "Involved in", "Participated in". These describe proximity, not contribution.

ATS-Friendly Formatting

Applicant Tracking Systems parse resumes before humans see them. Follow these rules:

  • Use standard section headings: "Experience", "Education", "Skills" — not creative alternatives like "Where I've Made an Impact"
  • No tables, columns, or text boxes — ATS reads left-to-right, top-to-bottom
  • No headers or footers — ATS often ignores these entirely
  • No images, icons, or graphics
  • Use standard fonts (Calibri, Arial, Garamond, Georgia)
  • File format: PDF unless the listing specifically requests .docx
  • Include keywords from the job listing naturally in context — not keyword-stuffed in a hidden block
  • Spell out acronyms on first use, then abbreviate: "Search Engine Optimisation (SEO)"

What to Omit

  • "References available upon request" — assumed and wastes space
  • Objective statements — replaced by professional summaries years ago
  • Every job since high school — include only relevant roles (last 10-15 years)
  • High school education (if you have a degree)
  • Hobbies/interests — unless directly relevant to the role or culture
  • Salary expectations — never on the resume itself
  • Reasons for leaving previous roles

Professional Summary

3-4 lines at the top. Not a personality description — a positioning statement.

Too vague:

Motivated professional with strong communication skills and a passion for technology seeking a challenging role.

Right approach:

Operations manager with 8 years in logistics and supply chain for mid-market retailers. Track record of reducing fulfilment costs (cut 22% at current role) while maintaining 99.4% on-time delivery. Looking to bring that operational discipline to a high-growth e-commerce environment.

Formula: [Role identity] + [years/domain] + [signature achievement or strength] + [what you're looking for].


Cover Letter

Structure

Three to four paragraphs, under one page. Every paragraph earns its place.

Paragraph 1 — Opening hook: Why this role, why now, why you noticed. Reference something specific about the company or role. No "I am writing to express my interest in the position of..." — that is the most wasted sentence in job applications.

Paragraph 2 — Why you (the match): Two to three specific examples of how your experience maps to their requirements. This is not a resume summary — pick the two strongest matches and give brief context. Use language from the job listing.

Paragraph 3 — Why this company (the fit): Show you have done your homework. Reference their product, mission, recent news, company culture, or a specific project. Explain why this matters to you personally. Generic flattery ("I admire your innovative approach") does not count.

Paragraph 4 — Close: Clear call to action. "I'd welcome the chance to discuss how my experience in X could support your team's work on Y. I'm available for a conversation at your convenience." Confident, not desperate.

Length and Format

  • Under one page, always
  • Same header/font as the resume for visual consistency
  • Address to a named person where possible (check LinkedIn, company website). "Dear Hiring Manager" as a last resort
  • AU/NZ: sign off with "Kind regards" (proposals/applications) or "Cheers" (if tone is casual)
  • US/UK: "Sincerely" or "Kind regards"

Tone Matching

Read the job listing and company website to calibrate tone:

Company type Tone Example phrasing
Startup / tech Conversational, direct "I've spent the last 3 years building exactly this kind of thing"
Corporate / enterprise Professional, measured "My experience in enterprise integration aligns closely with your stated objectives"
Government / public sector Formal, criteria-driven "I address each of the key selection criteria below"
Creative agency Personality forward "Your work on the X campaign is what made me pay attention"
Non-profit Mission-aligned "I've followed your work in X for several years and share your commitment to Y"

Common Mistakes

  • Rehashing the resume. The cover letter adds context and personality — it does not repeat bullet points.
  • Generic openings. "I am excited to apply for..." tells the reader nothing. Open with something specific.
  • No company reference. If you could send the same letter to 50 companies, it is too generic.
  • Underselling or overselling. State what you have done, factually. No "I'm the perfect candidate" and no "I know I don't have much experience but..."
  • Burying the lead. If you have a direct connection to the role (you use their product, you know someone there, you have deep domain expertise), say it in the first line.

Cover Letter Example

Too generic:

Dear Hiring Manager,

I am writing to express my interest in the Marketing Manager position. I have 5 years of marketing experience and am a strong communicator with excellent organisational skills. I believe I would be a great addition to your team.

Right approach:

Hi Sarah,

Your job listing mentioned you are looking for someone to rebuild the content strategy from the ground up — that is exactly what I did at Redgum Digital over the past two years, taking their blog from 400 monthly visitors to 12,000 and making it their primary lead channel.

The two things that stood out in the listing were the focus on SEO-driven content and the need to work closely with the sales team on case studies. At Redgum, I built both of those functions: a keyword-driven editorial calendar that targeted commercial intent terms, and a case study pipeline where I partnered with account managers to document client wins monthly. Five of those case studies became our top-converting landing pages.

I have been following [Company]'s expansion into the SME market since the product launch in October. The positioning challenge — making enterprise-grade software feel approachable for smaller teams — is something I find genuinely interesting, and it is the kind of messaging work I do best.

I would welcome the chance to talk through how I could help build out your content operation. Happy to chat whenever suits.


Special Circumstances

Career changers

Lead with transferable skills, not job titles. The professional summary should bridge the gap: "Project manager transitioning from construction to software delivery — 6 years of managing cross-functional teams, budgets, and tight deadlines." Emphasise skills that translate directly.

Employment gaps

Do not hide them or get creative with dates. If there is a gap, briefly explain it in the cover letter (caring responsibilities, study, travel, health — one sentence is enough). On the resume, list any relevant activity during the gap: freelance work, volunteering, courses, personal projects.

Overqualified

The cover letter must address the obvious question: "Why do you want this role?" Be direct about your motivation. Scaling back for work-life balance, pivoting into a new area, genuinely interested in the company — whatever the reason, name it.

Underqualified

Focus on adjacent experience and learning velocity. Show you have done something similar at a smaller scale or in a different context. The cover letter should acknowledge the stretch honestly while demonstrating you have closed similar gaps before.

Multiple roles at the same company

List the company once with each role as a sub-entry showing clear progression. This signals growth and loyalty.


Output Format

Deliver the document as clean markdown. If the user needs a formatted file, offer to create it as a .md or .txt that they can paste into their preferred tool (Google Docs, Word, Canva). Do not attempt to generate .docx or .pdf files directly.

For "both" mode, deliver the resume first, then the cover letter, in the same response.

how to use resume-cover-letter

How to use resume-cover-letter 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-cover-letter
2

Execute installation command

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

$npx skills add https://github.com/jezweb/claude-skills --skill resume-cover-letter

The skills CLI fetches resume-cover-letter from GitHub repository jezweb/claude-skills 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-cover-letter

Reload or restart Cursor to activate resume-cover-letter. Access the skill through slash commands (e.g., /resume-cover-letter) 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.557 reviews
  • Layla Garcia· Dec 24, 2024

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

  • Anika Brown· Dec 24, 2024

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

  • Anaya Torres· Dec 20, 2024

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

  • Yuki Perez· Dec 16, 2024

    resume-cover-letter fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Yuki Taylor· Dec 12, 2024

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

  • Anika Perez· Dec 4, 2024

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

  • Isabella Robinson· Nov 23, 2024

    Keeps context tight: resume-cover-letter is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Yusuf Rao· Nov 15, 2024

    resume-cover-letter fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Henry Patel· Nov 15, 2024

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

  • Anika Abebe· Nov 11, 2024

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

showing 1-10 of 57

1 / 6