cover-letter

Write a short, specific, human-sounding cover letter for a job from the user's real experience. Use when the user asks for a cover letter or an application requires one.

SKILL.md

GitHub

/cover-letter

Usage: /cover-letter <job folder or company + role> (or just ask in plain English).

Job: $ARGUMENTS.

Draft or coach? The letter has to end up the user's own: many employers and schools now expect application writing to be the candidate's, and a letter that sounds generated hurts more than it helps. The first time a user asks for a cover letter, offer the choice in one line: "I can draft it from your experience for you to edit, or coach you while you write it yourself. Which do you prefer?" Save their answer as a dated line under "Notes from conversations" in profile/preferences.md (show it; their OK) and don't ask again unless they bring it up. Coach means: ask for the hook and the story in their words, give an outline, then review their draft (truth-checker and voice-editor as below, specific suggestions, no wholesale rewrite), and build the PDF from their final text (steps 5-6). Draft is the steps below.

  1. Read the job's posting.md, fit.md, profile/master-resume.md, profile/story-bank.md, profile/voice.md. If optional: write one for priority A/B, or when it answers a question the resume raises (career change, relocation, gap, later start, referral); for priority C with no real hook, suggest skipping it. Evidence: references/cover-letter-evidence.md.
  2. Find one real, specific hook about the company: a product or service line, what the team or site focuses on, a recent announcement, why that location. Use the company-researcher agent if fit.md lacks it. No hook found → ask the user ("Anything you like about this company?"). Never fake enthusiasm.
    • Specific tailoring is what AI-written letters lose: once AI made tailored-looking text cheap, employers on a large freelance platform stopped paying more for applications closely tailored to the job post (Galdin & Silbert 2025). Echoing the posting's words isn't enough; every paragraph needs one detail only this user could write about this employer. Other kinds of job: hourly and shift jobs rarely need a letter (only when asked; then three or four sentences with availability). Academic jobs use a longer letter, commonly up to two pages, with short research and teaching paragraphs and the department's fit, plus separate statements when asked (knowledge/academic-jobs.md §2); the 300-word limit below doesn't apply. Freelance proposals follow knowledge/freelance-and-contract.md §3.
  3. Structure (≤ 300 words, 3–4 short paragraphs):
    • Open with the role and the hook in plain words, with no throat-clearing (a referral's name goes in the first sentence). A "pain letter" opening only around a need the posting states.
    • One paragraph: the single most relevant story with its number, from the master resume or story bank (e.g., "cut processing time 30%, saving $20K a year").
    • One paragraph: the second strength that matches a stated requirement in the posting.
    • Close: availability (only if timing matters, e.g. a future start date from preferences), one line of genuine interest, thanks. No "I believe I would be a great fit."
    • Country norms: follow the norms of the country the job is in (from the posting, else home_base): e.g. Letter paper in the US/Canada, A4 elsewhere; some countries expect a longer or more formal letter, a place-and-date line, or a fixed closing formula (references/languages-and-countries.md). Outside the US, ask the user once if unsure. Never add a photo, date of birth, marital status or similar personal details unless the user explicitly chooses to for this application.
    • Another language (any language other than the master resume's): write the letter in the posting's language only if it's in application_languages: in profile/preferences.md at about B2 or above (blank → ask once). Otherwise write it only if the user wants it, add a plain gloss in a language they read well (usually the master resume's), and mark it Needs a native-speaker check before sending. Write it directly in the target language from the master resume's facts, in that language's formal register, rather than translating an English draft line by line. Details: references/languages-and-countries.md.
    • Nothing hidden: never add white, tiny or invisible text, keyword stuffing, or prompts aimed at screening AI. Recruiters reject on sight.
  4. Save the text as jobs/<folder>/cover-letter.md. If the user can't start right away, state availability as a plain fact ("available full-time from <month year>"); never apologize for timing.
  5. Run truth-checker, then voice-editor, on cover-letter.md (for a letter in another language, tell both which language and country it's for; for an academic letter or any agreed length other than 300 words, tell voice-editor that length so it doesn't cut the letter). Fix what they flag; if anything changes after the truth-checker pass (including voice-editor's edits), re-check the changed sentences. (These checks are mandatory; for a priority C job, one combined truth-and-voice pass is fine.) Only then build cover-letter.html from the cover-letter template (profile/templates/cover-letter-template.html if it exists, the user's copy with their look; else templates/cover-letter-template.html, the app's copy, which you never edit) with the final text (fill the date, company, role and job ID, and the paragraphs). The template's date line, salutation ("Dear Hiring Team,") and closing ("Sincerely,") are US English examples: for another language or country, replace them with that country's forms (a place-and-date line such as "Berlin, 9. Oktober 2026", the formal salutation and closing in references/languages-and-countries.md). Fill its slots as the template's top comment lists them: the letterhead (header.masthead, the same name and contact line as the resume), p.date, p.recipient, p.subject (bold; "Re: ..." in English, "Bewerbung als ..." in German, "Objet : ..." in French), p.salutation, the paragraphs in div.letter-body, p.closing and p.signature. German and French letters put the place-and-date line after the recipient block (the template sets it right for lang="de" and lang="fr", and the French signature right). Its font, name accent, spacing, default paper and letterhead layout (layout_resume: classic, modern or compact, so the letterhead matches the resume) come from the documents block of profile/design.md; don't restyle it by hand or change data-layout (only @page size: may change for the job's country, and <html lang="..."> is set to the letter's language, e.g. de, so screen readers and hyphenation work). There is no designed cover letter. If the letter changes later, rebuild the HTML and the PDF so the PDF always matches the checked text.
  6. Make the PDF (only from the checked text): bash .claude/skills/tailor-resume/scripts/make-pdf.sh jobs/<folder>/cover-letter.html "<First Last>" "<Company>" (Windows without bash: powershell -NoProfile -ExecutionPolicy Bypass -File .claude\skills\tailor-resume\scripts\make-pdf.ps1 jobs\<folder>\cover-letter.html "<First Last>" "<Company>"). <First Last> is name: from profile/preferences.md (else the master resume's name) and <Company> is the job's company exactly as in jobs/tracker.csv, so the Apply Kit finds the file. It saves <First>-<Last>-Cover-Letter-<Company>.pdf in the job folder, no header or footer, on the template's paper size, and reports pages: and parse:. More pages than the target (1, unless the posting or the country or academic norm calls for a longer letter) → tighten the letter (re-check changed sentences), rebuild, run again. parse: check these: ... → fix the HTML and run again (a parse-note: line is not a problem; leave the layout alone). layout-warning: on an agreed longer letter (a last page with a few lines) → tighten it to end a page earlier, or leave it if it can't lose more without losing substance. print-failed with a check: line → the PDF came out blank or without the name, email and phone and was saved as ...-CHECK.pdf, which is never uploaded: fix cover-letter.html and run again (never rename the -CHECK file). no-browser, or print-failed without a check: line → the user opens cover-letter.html → Print → Save as PDF (Margins: Default, Headers and footers: off) under that name. Cover letters always use the HTML template, even when pdf_engine: rendercv. If the application has a text box instead of an upload, the user pastes the checked text without the letter header.
  7. Remind them, in one line, that it's a draft to make their own: read it aloud and change anything that doesn't sound like them (if they edit it, rebuild the PDF from their version after a quick truth-checker pass, and offer to note in profile/voice.md what they changed). Show the user the letter (plus the English gloss and the native-speaker-check line if it's in a language they can't review), tell them where the PDF is, and ask them to open the PDF and look it over before sending it, and whether anything sounds unlike them. If they change wording, re-check it and make the PDF again.