Cover letter

Skill ldenson1120/job-search-os/skills/cover-letter

A forkable job-search operating system for Claude — cover letters, interview prep, transcript Q&A, thank-you notes, and daily pipeline briefings, all in your own voice.

Install

npx -y skills add ldenson1120/job-search-os --skill cover-letter

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

This skill should be used when the user says "write a cover letter", "cover letter for [company or role]", "I'm applying to [company]", "help me apply to [role]", "draft a cover letter", or shares a job description and wants help writing application materials.

SKILL.md

2.8 KB, as published. Nobody here has run it

Cover Letter

Write a tailored cover letter that sounds like the person who actually did the work, not a document that sounds like a cover letter.

What to do

Get what you need. You need (a) the job description or enough detail about the role, and (b) the user's positioning and story bank. Load context/MY_POSITIONING.md, context/STORY_BANK.md, and — if it exists — context/MY_VOICE.md. The voice file is what keeps the letter from sounding AI-written; use it as the primary guide for how the letter should read. If any file is thin, work with what's there and flag the gap.
Identify the fit signal. Before writing, find the 2-3 points of genuine overlap between the user's background and what this role needs. These become the spine of the letter. Don't try to cover everything — cover what's most relevant and most differentiated.
Write a 3-paragraph letter. No more, no less, unless the user asks for something different.

Paragraph 1 — Hook + fit signal Start in the middle of something, not with "I'm excited to apply." Open with a specific observation about the company or role that shows you've actually thought about it, then connect it directly to your relevant experience. One sentence each is fine.

Paragraph 2 — Proof One or two proof points, not a resume summary. Choose the specific results that are most relevant to this role and company stage. Numbers when you have them. Write it the way you'd say it in a conversation, not the way it sounds in a press release.

Paragraph 3 — Close Short. Why now, why them. Invite a conversation without hard-selling. No "I look forward to hearing from you."
Calibrate the voice. Read the user's positioning doc for voice cues. The letter should sound like them — direct, grounded in specific work, no corporate gloss. If the job description has strong voice, match the register (scrappy startup tone vs. more formal enterprise tone).
Offer variants if needed. After the draft, offer to (a) write a shorter version, (b) shift the emphasis to a different proof point, or (c) adjust the opening if it doesn't land right.

Style rules