cover-letter
Skill0 starsChanged 28 days agoMITView on GitHub
Generate a tailored, voice-matched cover letter for a product manager role from a resume and job description. Follows with a hiring lens check and offers targeted revisions. Use when the user asks to write, draft, or generate a cover letter — especially for PM roles. Also triggers for: "write me a cover letter", "help me apply to this job", "draft a letter for this role", "cover letter for [company]", or when the user pastes a JD and asks for application help. Invoke immediately — gather context as part of the skill flow.
34 other projects use a version of this.
Adopted by
Most recently taken up by
- Muvon/octomind-taptheir own version, first seen Nov 12, 2026
- thesun4sky/jobstacktheir own version, first seen Nov 10, 2026
- eggs-gd/career-spacetheir own version, first seen Nov 8, 2026
- pradyumnasagar/open-research-skillstheir own version, first seen Nov 8, 2026
- Mahashwetha/Job-search-email-system-claudetheir own version, first seen Nov 5, 2026
- mergisi/awesome-openclaw-agentstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use interview-prep, tailor-resume and 7 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AnthropicSkillinterview-prep
Create structured interview plans with competency-based questions and scorecards. Trigger with "interview plan for", "interview questions for", "how should we interview", "scorecard for", or when the user is preparing to interview candidates.
Also in 7 projects that use this
proficientlyjobsSkilltailor-resume
Tailor your resume for a specific job posting
Also in 4 projects that use this
proficientlyjobsSkilljob-search
Search for jobs matching my resume and preferences
Also in 4 projects that use this
aslavchevSkillmock-interview
Simulate a real job interview for any role. Use when user says "mock interview", "interview me", "interview prep", "practice interview", or wants to rehearse for a specific company or position. Adapts rounds and questions to the role — technical, managerial, creative, or any other.
Also in 3 projects that use this
JDerekLomasSkillliterature-review
Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.). This skill should be used when conducting systematic literature reviews, meta-analyses, research synthesis, or comprehensive literature searches across biomedical, scientific, and technical domains. Creates professionally formatted markdown documents and PDFs with verified citations in multiple citation styles (APA, Nature, Vancouver, etc.).
Also in 3 projects that use this
VercelSkillsetup
Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".
Also in 5 projects that use this
- +1 more from proficientlyjobs
Other versions34 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 34
- mergisi/awesome-openclaw-agents★ 4.1ksame name
- claude-office-skills/skills★ 433same name
- proficientlyjobs/proficiently-claude-skills★ 389same name
- thesun4sky/jobstack★ 216same name
- matthewdigiuseppe/MStack★ 17same name
- Mahashwetha/Job-search-email-system-claude★ 12same name
- pradyumnasagar/open-research-skills★ 8same name
- Muvon/octomind-tap★ 6same name
- xcrrr/claude-skills★ 6same name
- eggs-gd/career-space★ 4same name
24 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- ai-quality-scorecardSkill
- competitive-teardownSkill
- eval-framework-builderSkill
- linkedin-reviewerSkill
- okr-writerSkill
- pm-case-study-builderSkill
- pm-take-home-caseSkill
- prd-reviewerSkill
- prd-writerSkill
- resume-reviewSkill
- take-home-reviewerSkill
- user-interview-synthesisSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 30 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 45
Don't open with "I'm excited/thrilled/passionate to apply." Don't open with a biographical sentence.
- Distinctive: line 56
Don't say "please let me know if you have any questions." Don't say "I look forward to hearing from you." Close like someone who expects to …
- Distinctive: line 68
If a voice sample is provided, match it above all else.
- Distinctive: line 81
After drafting, run a fast three-question check.
- Distinctive: line 98
After the check, offer:
- Distinctive: line 102
If the user requests a revision, rewrite only the section that needs it — don't regenerate the whole letter unless asked.
- Distinctive: line 110
If the user's experience is a strong fit, the letter should show confidence
- Distinctive: line 111
If the fit is imperfect, don't paper over it — address the gap directly and make the case for why it doesn't matter
“Common” is measured: kept by at least 6 in 10 of the 30 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Cover Letter Generator
What this skill does
Drafts a tailored PM cover letter from a resume and job description — in the user's voice, not a template. Follows with a quick hiring lens check to pressure-test it, then offers targeted revisions.
The goal: a letter that earns a read, says something the resume doesn't, and ends with a clear ask. Not a summary of the resume. Not a declaration of passion.
Step 1: Gather context
Collect everything in one prompt. Skip anything already in context:
- Resume — paste the full resume or share a file path
- Job description — paste the full JD, or provide company name + role title if no JD is available
- What to lead with — 1–2 things they most want to highlight (optional; use judgment if not provided)
- What to avoid — anything they don't want in the letter (optional)
- Voice sample — paste a paragraph or two of their own writing so the letter can match their natural style (optional but strongly improves output)
Once you have what you need, draft immediately. Don't ask follow-up questions.
Step 2: Draft the cover letter
Structure
Opening paragraph — lead with the actual thing Don't open with "I'm excited/thrilled/passionate to apply." Don't open with a biographical sentence. Open with the specific insight, experience, or conviction that makes this application worth reading. One to two punchy sentences that pull the reader in.
Middle — 2 paragraphs, specific and connected Each paragraph does one job:
- Paragraph 2: Connect the most relevant experience to what this role actually needs. Use a specific example. Show impact, not just involvement. One concrete story beats three vague claims.
- Paragraph 3: Show you understand what this company is actually building or solving. Reference something specific — a product decision they've made, a problem in their space, a bet they're taking. Don't flatter. Demonstrate attention.
Close — specific ask, clean exit Name what you want (a conversation, a call, a chance to go deeper on a specific topic). Don't say "please let me know if you have any questions." Don't say "I look forward to hearing from you." Close like someone who expects to get the meeting.
Length
3–4 paragraphs. Under 400 words. Every sentence earns its place.
Voice defaults (apply when no voice sample is provided)
- Decisive, not tentative — "I built" not "I was involved in building"
- Specific, not vague — real metrics, real company names, real decisions made
- Active, not passive — "I shipped" not "work was completed"
- Lean, not padded — cut every word that doesn't do work
- Human, not stiff — this should sound like a person wrote it, not a template
If a voice sample is provided, match it above all else. Study the sentence length, word choice, formality level, and rhythm. The letter should be indistinguishable from something the user wrote themselves.
Never do this
- "I'm thrilled/excited/passionate to share..." → Lead with the actual thing
- "As a seasoned PM with X years..." → Show, don't label
- "I believe I would be a great fit..." → State it through specifics, not declaration
- "Please let me know if you have any questions" → Specific ask or clean close
- Summarizing the resume → Say something the resume doesn't
Step 3: Hiring lens check
After drafting, run a fast three-question check. Don't turn this into a full review — it's a pressure test.
1. Recruiter scan (6 seconds) Would a recruiter read past sentence 1? Does the opening signal a qualified, interesting candidate? Is there anything that would trigger a skip?
2. Hiring manager read Does this letter say something the resume doesn't? Is there a specific story or insight that makes the application feel real, not templated? Does it demonstrate genuine understanding of the role?
3. Clarity of ask Is the close specific? Does it feel like someone who expects the meeting, or someone who's hoping for a callback?
For each check: one sentence verdict and, if there's an issue, a specific fix.
Step 4: Offer revisions
After the check, offer:
"Want me to revise anything? I can rework the opening, strengthen the middle paragraphs, adjust the tone, or tailor it more specifically to the JD. Just say what needs work."
If the user requests a revision, rewrite only the section that needs it — don't regenerate the whole letter unless asked.
Tone guidance
This is a tool for getting a job. Write accordingly.
- If the user's experience is a strong fit, the letter should show confidence
- If the fit is imperfect, don't paper over it — address the gap directly and make the case for why it doesn't matter
- A letter that says one true, specific thing memorably is better than a letter that says five true things generically
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

