Cover Letter Writing SKILL.md

This is the exact file agents read, including the credit header and licence notice. Save it as cover-letter-writing/SKILL.md.

---
name: cover-letter-writing
description: "Write cover letters that earn their place: the employer's real need, an angle (problem, domain, transition, referral or product), two or three pieces of real evidence from the user's career profile, light verified company research, a 3 to 5-paragraph structure, short and email versions, variants for career changes, referrals and gaps, and regional norms. Use whenever someone needs a cover letter, motivation letter, 'why this role' answer, speculative application letter or application email, or wants a draft cover letter improved."
license: CC-BY-4.0
metadata:
  author: Afeez Adebayo
  author_url: https://afeezadebayo.com
  author_linkedin: https://www.linkedin.com/in/afeez-adebayo/
  author_x: https://x.com/za_icon
  source: https://afeezadebayo.com/skills-md/productivity/jobs-careers/cover-letter-writing/
  category: productivity
  subcategory: jobs-careers
  version: "1.0.0"
  created: "2026-10-12"
  updated: "2026-10-12"
---

# Cover Letter Writing

Most cover letters are skipped because they say nothing the CV does not. They open with "I am excited to apply", restate job titles, claim passion and close with "I believe I would be a great fit". AI has made this worse: recruiters now see the same polished, generic letter many times a day. Yet a short, specific letter still helps when a role is competitive, the fit is not obvious from the CV, the candidate is changing careers, or the employer asks for one.

This skill writes cover letters that earn their place. It reads the job and the company, picks two or three pieces of real evidence from the user's career profile, explains why this role and why this move makes sense, and delivers a full letter, a short version for form fields and an email version, all in the user's own voice.

## Operating principles
1. **Add what the CV cannot.** Motivation, context, the story behind a move and the link between the user's work and this employer's problem.
2. **Evidence beats adjectives.** Two or three specific results outperform any amount of enthusiasm.
3. **Specific to one employer.** If the letter could be sent to another company by changing the name, rewrite it.
4. **Truth first.** Every claim traces to the career profile or a fact the user confirms. Company facts come from the posting or verified research.
5. **Short wins.** 250 to 400 words by default; shorter when the evidence is clear.

## Inputs
- The job description (full posting, not a summary).
- The user's career profile (`career-profile.md`), or their CV if no profile exists yet.
- The tailored CV for this role, if one was written, so the letter complements rather than repeats it.
- Preferences: English variant, tone (formal, warm, direct), words or punctuation to avoid, sign-off details.
- Optional: a hiring manager's name, a referral, why the user wants this company, any constraint to address (relocation, notice period, career gap).

If a fact would strengthen the letter but is missing, ask one precise question or proceed without it.

## When to use, and when not to
Use it when an employer asks for a cover letter or motivation letter, when a form has a "why this role" field, for career changes, referrals, speculative applications and when the fit needs explaining.

Skip the letter when the employer says not to send one, or when a form gives no place for it and the CV already makes the fit obvious. Don't use it for the CV itself (`cv-writer`) or outreach messages to contacts (`networking-referral-outreach`).

## Workflow

### Step 1. Find the employer's real need
From the posting, identify the main problem the role exists to solve, the two or three requirements that matter most and any language the company uses repeatedly. Label inferences as inferences.

### Step 2. Choose the angle
Pick one of these, based on the evidence:

| Angle | Use when | Opening idea |
|---|---|---|
| Problem match | The user has solved the employer's core problem before | Name the problem and the result |
| Domain match | The user knows the industry or customer deeply | Show insight into the market |
| Transition | The user is changing field or level | Explain the logic of the move |
| Referral | Someone at the company recommended them | Name the person and the reason |
| Mission or product | The user has real, specific ties to the product | A concrete use or observation, never flattery |

### Step 3. Select evidence
Choose two or three achievements that map directly to the top requirements. Each needs a result, scale or concrete outcome. Do not reuse the CV's wording; add context the CV lacks, such as how the result was achieved.

### Step 4. Research the company lightly
If web access exists, check the company's site, product, recent news and the team behind the role. Use one specific, verified observation. Never invent company knowledge.

### Step 5. Draft with the structure below

### Step 6. Make the short and email versions
80 to 150 words for form fields with limits; an email body when the application goes by email.

### Step 7. Check and deliver
Run the checklist, match the user's language rules and deliver.

## Structure (3 to 5 short paragraphs)
1. **Opening (2 to 3 sentences).** Why this role, in specific terms: the problem, the product, the referral or the intersection with the user's work. No throat-clearing.
2. **Evidence (1 to 2 paragraphs).** Two or three results tied to the employer's needs, with brief context on how.
3. **Why this company and why now.** One verified observation and a reason the move makes sense.
4. **Practical points (optional).** Availability, location or time zone, relocation, notice period, gap explained in one line.
5. **Close (1 to 2 sentences).** A plain next step, such as being glad to talk through a specific area.

## Example of the difference
**Generic:**
"I am excited to apply for the Lifecycle Marketing Manager role. With many years in marketing, I am confident I would be a great fit for your dynamic team."

**Specific:**
"Your posting talks about lifting activation in the first 30 days. That is the problem I worked on for the past two years: an onboarding journey I rebuilt raised first-month deposits by 24%, mostly by fixing the step where new customers stalled."

The second version names the problem, gives a result and explains how, in fewer words.

## Phrases to avoid
`I am excited to apply`, `I am writing to express my interest`, `Throughout my career`, `I believe I would be a great fit`, `I am confident that`, `passionate about`, `proven track record`, `results-driven`, `dynamic team`, `leverage my skills`, `hit the ground running`, `I have always admired your innovative company`. Also avoid any punctuation the user bans, such as em dashes.

## Variants
| Situation | Adjustments |
|---|---|
| Career change | Lead with the transferable result; one sentence on why the move is deliberate; never claim the target title |
| Referral | Name the referrer in the first line, with permission |
| Speculative letter | Name the problem you can help with and a specific team; keep under 250 words |
| Internal move | Reference work the reader knows; focus on what changes in the new role |
| Career gap | One factual line, then move on; no over-explaining |
| Senior roles | Strategy, commercial outcomes and leadership evidence; avoid task lists |
| Graduate or early career | Projects, internships, coursework results and evidence of learning fast |
| Motivation letter (Europe) | Slightly more on motivation and fit with the organisation; follow the posting's language |

## Regional notes
| Market | Practice |
|---|---|
| UK and Ireland | Often requested; one page; "Dear Hiring Manager" if no name |
| US and Canada | Often optional but read for competitive roles; one page |
| Germany, France, Netherlands | Motivation letters common; formal tone; local language if the posting uses it |
| Nigeria and West Africa | Common for formal roles; clear, formal and concise; address to the named recruiter where possible |

## Formats
- **Full letter:** 250 to 400 words, PDF unless the employer asks for Word, file name `<Name>_Cover_Letter_-_<Company>`.
- **Short version:** 80 to 150 words for form fields.
- **Email version:** short version as plain text, a clear subject following any employer format, CV attached.
- **Greeting:** the named hiring manager if known and verified; otherwise "Dear Hiring Team" or "Dear Hiring Manager".

## Checklist
- Specific to this company and role; would fail if sent elsewhere.
- Opens with something concrete, not enthusiasm.
- Two or three pieces of evidence, each with a result or scale.
- Adds context the CV lacks; does not repeat it.
- No invented facts about the user or the company.
- No banned phrases or punctuation; matches the English variant.
- Within the word count; short and email versions provided when useful.
- Reads like a person: would the user say these sentences aloud?

## Edge cases and judgement calls
| Situation | What to do |
|---|---|
| No hiring manager name | Use "Dear Hiring Team"; do not guess a name |
| The posting asks specific questions | Answer them directly, in order, instead of a standard letter |
| Weak fit | Address the biggest gap openly with adjacent evidence, or advise not applying |
| Salary asked in the letter | Give a researched range only if the user approves it |
| User supplies a draft | Edit for specificity and evidence; keep their voice |
| Very short form limit (e.g. 300 characters) | One sentence of fit plus one result |

## Handoffs to related skills
- Tailored CV: `cv-writer`
- Finding roles: `daily-job-opportunities`
- Career profile and evidence: `career-profile`
- Referral messages: `networking-referral-outreach`
- Remote and international applications: `remote-international-jobs`

## Worked example
A product analyst moving into product management applies to a logistics startup. The letter opens with the company's stated problem of late deliveries, then gives two results: a dashboard that cut failed deliveries by 12% at the analyst's current employer and an experiment programme they ran with the product team. One paragraph explains why the move to product management is deliberate, citing the experiments they already lead. It closes by offering to walk through the experiment results. The full letter is 310 words, with a 120-word version for the application form.

## Output format
```
1. Angle chosen and why (one line)
2. Full cover letter
3. Short version (80 to 150 words)
4. Email version (subject line and body), if applying by email
5. Notes: facts to confirm, company claims to verify
```

## Self-check before you answer
- Could this letter be sent to another company unchanged? If yes, rewrite.
- Does every claim trace to the profile or a confirmed fact?
- Does it add something the CV does not say?
- Is it within length and free of banned phrases?

---
Created by Afeez Adebayo, Marketing, SEO & Growth Expert
Website: https://afeezadebayo.com
LinkedIn: https://www.linkedin.com/in/afeez-adebayo/
X: https://x.com/za_icon
Source: https://afeezadebayo.com/skills-md/productivity/jobs-careers/cover-letter-writing/

Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). You may copy, share and adapt this skill, including for commercial use, as long as you credit Afeez Adebayo and link to the source URL above. Keep this notice in any copy or adapted version.