agentleFS
JayRHaJayRHa/agent-skills/cover-letter-writer/SKILL.md

cover-letter-writer

Skill12 starsChanged 5 months agoMITView on GitHub

Writes tailored, persuasive cover letters that connect a candidate's concrete achievements to a specific role and company — with a strong hook, evidence-backed body, and clear close. Use this skill when a user asks to "write a cover letter", "write a motivation letter", "cover letter for this job", "letter of interest", or wants help explaining a career change, employment gap, or why they want a particular role.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 4

    Distinctive

    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:

    Map proof to needs: Read the JD's top 3 requirements.

    line 26
  2. Distinctive:

    Complement the resume, don't recite it: Add narrative and the *why*.

    line 49
  3. Distinctive:

    Confident, warm, concise: No begging, no arrogance.

    line 50
  4. Distinctive:

    Address it to a person: when you can find the name.

    line 51

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “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

Cover Letter Writer

Overview

This skill writes a short, specific, genuinely persuasive cover letter that complements (never repeats) the resume. A good cover letter answers three questions fast: Why this company? Why this role? Why you? — backed by one or two concrete proof points.

Keywords: cover letter, motivation letter, letter of interest, application letter, Anschreiben, job application, career change, why this company.

When to use vs. not

Use this whenever a role asks for (or allows) a cover letter, or when the candidate needs to explain something a resume can't (a pivot, a gap, an unusual fit). Don't pad — if there's nothing role-specific to say, a tight 3-paragraph letter beats a generic page. Never fabricate enthusiasm with invented facts about the company; use real, verifiable specifics.

Inputs to gather first

  1. The job description and company name.
  2. The candidate's 2–3 strongest relevant achievements (ideally quantified).
  3. One genuine reason they want this company/role (product, mission, team, problem).
  4. Anything to address head-on: career change, gap, relocation, over/under-qualification.
  5. Tone target: formal (finance/law/gov) vs. warm-professional (startup/creative).

Workflow

  1. Research the hook. Find one specific, true thing about the company (a product, value, recent launch, problem they solve) the candidate authentically connects to. This becomes the opener. Generic "I am writing to apply for…" openers are dead on arrival.
  2. Map proof to needs. Read the JD's top 3 requirements. Pick the candidate's achievements that directly answer them.
  3. Write the opening (2–3 sentences). Name the role, lead with the hook or a punchy proof point. Make the reader want the next paragraph.
  4. Write the body (1–2 short paragraphs). Each makes one claim about fit and backs it with a concrete, quantified example. Show impact, not a duty list. This is "the resume's greatest hits, with narrative."
  5. Address the elephant (if any). One confident sentence on the gap/pivot/relocation — framed forward, never apologetic.
  6. Close (2 sentences). Restate enthusiasm, state availability, and a light call to action ("I'd welcome the chance to discuss…"). Thank them.
  7. Trim to ~250–350 words / under one page. Cut every sentence that could appear in any other letter.
  8. Match format. Email body vs. attached letter; for DACH, follow the formal Anschreiben layout (sender/recipient blocks, date, subject line).

Decision framework

SituationEmphasis
Strong direct fitLead with the single most relevant quantified win
Career changeLead with transferable skills + why the pivot is deliberate, not random
Employment gapOne forward-framed sentence; spend the rest on value
Dream company, stretch roleLead with genuine mission alignment + fastest-ramp evidence
Referral existsName the referrer in the first line

Worked example

See examples/career-change.md for a full letter from a teacher moving into UX research.

Best Practices

  • One specific company detail proves you didn't mass-mail it.
  • Show, don't claim. "Increased newsletter open rates 40%" beats "I am passionate about marketing."
  • Complement the resume, don't recite it. Add narrative and the why.
  • Confident, warm, concise. No begging, no arrogance.
  • Address it to a person when you can find the name.

Common Pitfalls

  • Generic opener that could be sent to any company.
  • Summarizing the whole resume in prose.
  • Making it about what the candidate wants, not what they offer.
  • Apologizing for gaps or missing requirements.
  • Too long. Recruiters skim; one page max, ideally less.
  • Typos / wrong company name from a recycled letter — fatal.

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.