agentleFS
nisarthnisarth/claude-skills-store/skills/writing/resume-cover-letter/SKILL.md

resume-cover-letter

Skill1 starsChanged 7 months agoMITView on GitHub

Write and optimize resumes and cover letters tailored to specific job descriptions. Trigger with "write a resume", "update my CV", "cover letter for", "tailor my resume to", "ATS optimize", "help me apply for", or when the user needs job application materials that highlight achievements and pass applicant tracking systems.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

16 rules. About 0 are common, 16 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈16

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write and optimize resumes and cover letters that are tailored to specific job descriptions, highlight quantified achievements, and pass …

    line 28
  2. Distinctive:

    Ask for the user's current resume or a summary of their experience.

    line 37
  3. Distinctive:

    Ask about specific achievements, metrics, or projects they want to highlight.

    line 40
  4. Distinctive:

    No photo, no age, no marital status.

    line 59
  5. Distinctive:

    Keep the cover letter under 400 words and one page.

    line 95
  6. Distinctive:

    Ensure the documents pass automated screening:

    line 99
  7. Distinctive:

    Use standard section headings (Experience, Education, Skills — not creative alternatives).

    line 101
  8. Distinctive:

    Avoid tables, columns, headers/footers, images, and text boxes.

    line 102
  9. Distinctive:

    Use standard fonts and formatting that parse cleanly.

    line 104
  10. Distinctive:

    Action: Use a functional or hybrid resume format, emphasize skills and projects over chronology, address the gap briefly and positively in …

    line 158
  11. Distinctive:

    Every bullet point should answer "So what?" — impact matters more than responsibilities.

    line 162
  12. Distinctive:

    Never fabricate experience or inflate metrics — integrity is non-negotiable.

    line 164
  13. Distinctive:

    Use present tense for current roles, past tense for previous roles.

    line 165
  14. Distinctive:

    Keep the resume to one page for under 10 years of experience, two pages for senior/executive.

    line 166
  15. Distinctive:

    If the user has no metrics, help them estimate reasonable ones ("managed a team of ~5" is better than "managed a team").

    line 168
  16. Distinctive:

    Test ATS compatibility by imagining the resume as plain text — if the structure breaks, fix it.

    line 169

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Resume and Cover Letter Writing

Write and optimize resumes and cover letters that are tailored to specific job descriptions, highlight quantified achievements, and pass applicant tracking systems (ATS).

Workflow

Step 1: Gather Inputs

Collect the information needed to build effective application materials:

  • Request the target job description (full text preferred over just the title).
  • Ask for the user's current resume or a summary of their experience.
  • Identify the user's career level: entry, mid, senior, or executive.
  • Note the industry and function (software engineering, marketing, finance, etc.).
  • Ask about specific achievements, metrics, or projects they want to highlight.
  • Determine if there are employment gaps or career changes that need framing.

Step 2: Analyze the Job Description

Extract requirements to guide tailoring:

  • Identify must-have qualifications vs. nice-to-haves.
  • Extract key skills, technologies, and competencies mentioned.
  • Note the company's values and culture signals from the language used.
  • List action verbs and terminology the employer uses (mirror these in the resume).
  • Identify the 3-5 most important requirements to emphasize in the application.

Step 3: Write the Resume

Build or rewrite the resume with ATS optimization:

Header

  • Full name, professional title, location (city/state only), phone, email, LinkedIn URL.
  • No photo, no age, no marital status.

Professional Summary (3-4 lines)

  • Years of experience + domain + key strength + signature achievement.
  • Incorporate the job title and 2-3 keywords from the description.

Experience (reverse chronological)

  • Company name, title, dates (month/year).
  • 3-5 bullet points per role, each following the formula: Action verb + task + result with metric.
  • Prioritize bullets that match the job description requirements.
  • Quantify wherever possible: revenue, percentages, team size, time saved, users served.

Skills Section

  • Match skill keywords exactly as they appear in the job description.
  • Group by category: languages, frameworks, tools, methodologies, certifications.
  • Include both spelled-out terms and acronyms (e.g., "Search Engine Optimization (SEO)").

Education

  • Degree, institution, graduation year. GPA only if above 3.5 and less than 5 years post-graduation.
  • Relevant coursework or honors only for entry-level candidates.

Optional Sections

  • Certifications, publications, speaking engagements, volunteer work — only if relevant to the role.

Step 4: Write the Cover Letter

Draft a compelling cover letter that complements (not repeats) the resume:

Opening paragraph: State the role, how you found it, and a one-sentence hook (a specific achievement or connection to the company's mission).

Body paragraph 1: Address the top requirement from the job description with a concrete example demonstrating that capability. Use the STAR format (Situation, Task, Action, Result).

Body paragraph 2: Address a second key requirement or demonstrate cultural fit. Connect your experience to the company's specific challenges or goals.

Closing paragraph: Reaffirm enthusiasm, state availability, and include a specific call to action (e.g., "I welcome the opportunity to discuss how [specific skill] can support [company goal]").

Keep the cover letter under 400 words and one page.

Step 5: ATS Optimization

Ensure the documents pass automated screening:

  • Use standard section headings (Experience, Education, Skills — not creative alternatives).
  • Avoid tables, columns, headers/footers, images, and text boxes.
  • Match keywords verbatim from the job description.
  • Use standard fonts and formatting that parse cleanly.
  • Save as .docx or plain text unless PDF is specifically requested.
  • Spell out acronyms at least once alongside the abbreviation.

Output Format

# [Full Name]
[Title] | [Location] | [Phone] | [Email] | [LinkedIn]

## Professional Summary
[3-4 line summary tailored to the target role]

## Experience

### [Job Title] — [Company Name]
*[Start Date] - [End Date]*
- [Achievement bullet with metric]
- [Achievement bullet with metric]
- [Achievement bullet with metric]

## Skills
**[Category]**: [Skill 1], [Skill 2], [Skill 3]

## Education
**[Degree]** — [University], [Year]

---

# Cover Letter

Dear [Hiring Manager / Hiring Team],

[Opening paragraph — hook + role + company connection]

[Body paragraph 1 — top qualification with STAR example]

[Body paragraph 2 — secondary qualification or cultural fit]

[Closing paragraph — enthusiasm + CTA]

Sincerely,
[Full Name]

Examples

User: "Tailor my resume to this senior frontend engineer role at Stripe" Action: Analyze the Stripe JD for key skills (React, TypeScript, performance, design systems), reorder and rewrite bullets to emphasize matching experience, add relevant keywords to the skills section.

User: "Write a cover letter for a product manager role — I'm transitioning from engineering" Action: Frame engineering experience as a strength (technical credibility, data-driven decisions), address the career change directly, highlight transferable skills with specific examples.

User: "I have a 2-year employment gap — help me address it" Action: Use a functional or hybrid resume format, emphasize skills and projects over chronology, address the gap briefly and positively in the cover letter (caregiving, education, personal project).

Best Practices

  • Every bullet point should answer "So what?" — impact matters more than responsibilities.
  • Tailor aggressively: a generic resume sent to 100 jobs loses to a tailored one sent to 10.
  • Never fabricate experience or inflate metrics — integrity is non-negotiable.
  • Use present tense for current roles, past tense for previous roles.
  • Keep the resume to one page for under 10 years of experience, two pages for senior/executive.
  • The cover letter should tell a story the resume cannot — motivation, context, and personality.
  • If the user has no metrics, help them estimate reasonable ones ("managed a team of ~5" is better than "managed a team").
  • Test ATS compatibility by imagining the resume as plain text — if the structure breaks, fix it.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.