Writes a focused cover letter that links your real experience to the job, without padding or invented claims.
WHEN TO USE IT
When you are applying for a role and need a letter that fits the job advert.
Formats change. If a field stops working, check it against Anthropic's documentation.
One file. The description is what Claude matches against, so it says plainly when to use the skill.
---
name: cover-letter
description: Write a cover letter from the user's own experience and a job advert. Use when the user asks for a cover letter, application letter or motivation letter.
---
Write a cover letter for one specific job.
1. If the job advert, the company name or the user's relevant experience is missing, ask once, in one message, then continue.
2. Pick the three requirements in the advert that matter most.
3. For each, find a matching example in what the user has told you. If there is no match, say so instead of filling the gap.
4. Write the letter in four short parts:
- Opening: the role and one honest reason for applying.
- Middle: two or three examples, each tied to a requirement.
- Fit: why this company, using only what the advert or the user says.
- Close: a polite line about next steps.
5. Keep it under 350 words and in plain, confident language.
6. After the letter, list any requirement the user's experience did not cover.
Rules:
- Never invent experience, employers, job titles, dates, skills or achievements.
- Do not invent figures; write [check] where a number would help and the user has not given one.
- Avoid empty phrases such as "team player" unless an example backs them up.
Put the folder in your skills directory. Then ask in plain words, and Claude loads the skill when your request matches its description; or type the command yourself.
# for you, in every project
mkdir -p ~/.claude/skills/cover-letter
mv SKILL.md ~/.claude/skills/cover-letter/
# then, inside Claude Code, either ask naturally:
# help me write a cover letter for this job
# or run it by name:
# /cover-letter
MORE SKILLS
The authority
Anthropic's documentation for Skills
This template is a starting point. Field names and options are defined by Claude Code, and its documentation wins whenever the two disagree.
https://code.claude.com/docs/en/skills