Skip to content

ValentinNikolaev/agent-skills / agent-plugins/skills/write-cover-letter

write-cover-letter

Verified

Create, tailor, revise, or critique cover, motivation, and job-application letters from job requirements and verified candidate evidence; not CVs, LinkedIn profiles, recommendations, or generic correspondence.

FileKindSize
SKILL.mdskill md7.8 KB
agents/openai.yamlconfig245 B
references/cover-letter-workbench.mdmarkdown5.0 KB

references/cover-letter-workbench.md

View on GitHub
# Cover-letter workbench

Use this workbench to turn a job posting and verified candidate evidence into a focused letter. Keep it internal unless the user asks to see the analysis.

## Contents

- [Prioritize the posting](#prioritize-the-posting)
- [Build the evidence map](#build-the-evidence-map)
- [Select a story theme](#select-a-story-theme)
- [Shape each evidence paragraph](#shape-each-evidence-paragraph)
- [Research company motivation](#research-company-motivation)
- [Assemble the draft](#assemble-the-draft)
- [Final claim ledger](#final-claim-ledger)
- [Source](#source)

## Prioritize the posting

Split the posting into four groups:

| Group | Handle it this way |
|---|---|
| Core responsibilities | Prioritize explicit outcomes, repeated duties, and the earliest substantial bullets. |
| Required qualifications | Match directly or explain an honest transferable match. |
| Preferred or soft qualifications | Use them when supported; do not self-reject solely because one is missing. |
| Hard eligibility constraints | Surface licensure, clearance, authorization, location, or mandatory-language gaps. |

Treat ordering as a signal, not proof. A later requirement tied to a critical business outcome can outrank an earlier generic bullet.

## Build the evidence map

Use this schema:

| Priority requirement | Employer wording | Candidate evidence and source | Match | Verified metric | Story theme or gap |
|---|---|---|---|---|---|
| [Requirement] | [Exact key terms] | [Resume section or user statement] | Direct / transferable / gap | [Metric or none] | [Theme or gap] |

Apply these rules:

- Quote or closely preserve employer terminology in the analysis, then use it naturally in the letter.
- Keep the evidence source explicit so every drafted claim remains traceable.
- Prefer one strong example that proves several related requirements over several shallow examples.
- Choose two complementary stories rather than repeating the same achievement twice.
- Use `gap` when no evidence exists. Never convert a nearby skill into the requested named tool or credential.

## Select a story theme

Use a theme only to focus the story:

- leading people;
- taking initiative;
- affinity for challenging work;
- affinity for varied work;
- affinity for the specific work;
- dealing with failure;
- managing conflict;
- driven by curiosity.

Prefer a clearer evidence-led proposition when none of these themes fits. A theme is not permission to infer motives, emotions, or impact.

## Shape each evidence paragraph

Build each paragraph from five parts:

1. **Proposition or theme**: State the professional quality relevant to the role.
2. **Context**: Set the scene briefly.
3. **Action**: Describe the candidate's specific contribution.
4. **Outcome or learning**: Use a verified result; if none exists, state a supported lesson or capability.
5. **Role relevance**: Connect the evidence to a priority responsibility without claiming certainty about future performance.

Compress context before cutting action or outcome. Avoid claiming that a team result belongs solely to the candidate unless the evidence says so.

## Research company motivation

Capture company hooks separately from the candidate connection:

| Company fact | Primary source and access date | Candidate connection | Safe letter language |
|---|---|---|---|
| [Mission, value, product, or initiative] | [URL, date] | [Supplied goal or experience] | [Truthful connection] |

Prefer two hooks. Use product experience only when confirmed. Replace generic praise with a specific connection, but leave the section out rather than inventing one.

## Assemble the draft

Use this content skeleton, not as fixed wording:

- **Salutation**: verified person or Hiring Team.
- **Opening**: identity + target role + credible proposition + optional company detail.
- **Transition**: strongest relevant achievement + intended contribution.
- **Story one**: highest-priority responsibility and strongest evidence.
- **Story two**: complementary responsibility and evidence.
- **Company motivation**: two researched hooks tied to genuine candidate interests.
- **Closing**: concise fit, interest, and sign-off.

Keep only details that help the hiring reader answer three questions: Can this candidate do the important work? What evidence proves it? Why this company and role?

## Final claim ledger

Before delivery, check each risky statement:

| Claim type | Required support |
|---|---|
| Metric, tenure, title, credential, tool | Exact candidate evidence |
| Leadership or ownership | Evidence of the candidate's scope, not only the team's result |
| Company mission, product, value, initiative | Current source or supplied posting |
| Product use or personal enthusiasm | Explicit candidate confirmation |
| Eligibility | Exact candidate status and posting requirement |

Move unresolved items to `Confirm before sending`. Do not leave hidden assumptions inside the letter.

## Source

Method adapted and paraphrased from [My Guide To Writing A Killer Cover Letter](https://www.reddit.com/r/datascience/comments/tag8l5/my_guide_to_writing_a_killer_cover_letter/).
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 196kUpdated Claude CodeCodexVerifiedInstall