/cover

Run the cover-letter step for: $ARGUMENTS

1. Read jobs/$ARGUMENTS/job.md, jobs/$ARGUMENTS/score.md, and the profile/ files (positioning, proof points, master record).

2. Draft a cover letter (max one page) in a warm, human, first-person voice - never template tone (no "I am writing to apply for", no "I would welcome the chance to discuss"). Mirror the JD's language, open with the user's strongest matching proof point, and address the top must-have skills. Use only facts from profile/. Never cite employer programmes or sector terms the user has not personally worked on as their own motivation.

   Pass the humanity check. Recruiters now bin AI-slop on sight - surveys put "generic and unpersonalised" as the top stated rejection reason, and 80% of hiring managers believe they can spot AI writing. So:

   • The letter must contain at least one thing that is NOT on the CV: why this company, why this role, why now. A letter that restates the CV is a wasted page.
   • At least two specifics only someone who actually read about THIS company could write (a product, a project, a market move) - and only ones the user genuinely cares about; ask them if unsure.
   • Banned: "delve", "realm", "intricate", "showcasing", "pivotal", "leverage" (as a verb), "I am excited to", praise any company could receive ("your prestigious organisation"), keyword-stuffed sentences, and em-dash-heavy prose.
   • Read it aloud test: if a sentence doesn't sound like the user talking, rewrite it.

3. If a warm-intro contact maps to this company (profile.yml contacts), note it at the top so the user leads with the intro rather than a cold application.

4. Write jobs/$ARGUMENTS/cover.md (plain text - easy to paste into web forms). If a PDF toolchain is available and the user wants PDFs, also build cover.pdf matching their CV's typography. Draft only - the user reviews and sends.