agentmods.dev

write-cover-letter

write-cover-letter is a skill for Claude Code from jain777/jobclaw-skills. It costs 74 tokens per session (1,277 once invoked), scanned A, original, MIT.

A job-specific cover-letter writer that creates a concise Markdown letter from the candidate’s profile and the role details.

In plain words
What is it for?
Use it to write a three-paragraph letter with an opening fit statement, two quantified examples, and a closing connection to the role.
Why use it?
It keeps the letter focused on the particular employer and role while reusing relevant evidence and keywords from resume tailoring.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the jobclaw-skills plugin — 20 skills shipped together

not rated 5repo 3mo ago A scan 74 tokens original MIT

Good fit Use it to write a three-paragraph letter with an opening fit statement, two quantified examples, and a closing connection to the role.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jain777/jobclaw-skills/write-cover-letter
View source ↗ jain777/jobclaw-skills
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add jain777/jobclaw-skills --skill write-cover-letter
Clone the repo
git clone --depth 1 https://github.com/jain777/jobclaw-skills

Made for: Claude Code.

Or install jobclaw-skills, the plugin that ships this one along with the rest of its 20 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for write-cover-letter

README.md
[![agentmods](https://agentmods.dev/badge/skills/jain777/jobclaw-skills/write-cover-letter/github.svg)](https://agentmods.dev/skills/jain777/jobclaw-skills/write-cover-letter)
Your own site
<a href="https://agentmods.dev/skills/jain777/jobclaw-skills/write-cover-letter"><img src="https://agentmods.dev/badge/skills/jain777/jobclaw-skills/write-cover-letter/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for write-cover-letter

Your own site · 80×15
<a href="https://agentmods.dev/skills/jain777/jobclaw-skills/write-cover-letter"><img src="https://agentmods.dev/badge/skills/jain777/jobclaw-skills/write-cover-letter.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 74 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,277 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00074 $0.01277
Opus 5 $0.00037 $0.00639
Sonnet 5 $0.00015 $0.00255
Haiku 4.5 $0.00007 $0.00128

Measured 12d ago against content hash 41cdc906a01e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

write-cover-letter scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/write-cover-letter/SKILL.md · 85 lines

How it starts

The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.

write-cover-letter

Earn the reader the next 30 seconds. Open with one concrete reason this candidate fits this role at this company. Hard rules: ../_shared/RULES.md. Use Communication / Management / Creative verbs from ../tailor-resume/reference/action-verbs.md.

Inputs

  1. Profile: profile/master-profile.md. Read context: for direction only — never quote.
  2. Job: pasted JD text, a URL (use WebFetch), or an entry from jobs/found-<date>.json. Known-info gate (RULES §6): if no job is given inline, read jobs/current.json and use its jd_text/company/role — do not re-ask for the JD when it's already captured upstream.
  3. Tone: enthusiastic | confident | concise | warm (default: confident).
  4. Optional sidecar: resumes/<slug>.tailor.json from a prior tailor-resume run — reuse its keyword list and basics_overrides.summary so the letter and the resume sing the same notes.
  5. Optional score-fit sidecar: scores/<job-id>.score.json — reuse missing_keywords to know what the resume already incorporated.

If no job is supplied and jobs/current.json is absent, ask for it; the tone has a safe default.

Method

  1. Region note. Read the target region pack:

    • US: cover letters role-dependent — stronger for senior, mission-driven, career-change roles. Surface this in the rationale so the user decides whether to send.
    • IN: cover letters less emphasized; usually a 2–3 sentence email body suffices. Offer a "short form" alternative if the user wants.

  2. Read the JD for 3–5 must-have themes, the JD's tone of voice (formal / casual / mission-led), and any explicit asks ("tell us why you want to work here").

  3. Pick two flagship achievements from the profile that map to those themes — each quantified. No invention; if the profile lacks a quantified match, pick the closest qualitative win and flag the gap rather than fabricating a number.

Read the full file on GitHub · 85 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 85 lines · 74 tokens per session scan A 41cdc906a01e

Subscribe to this mod's changes

write-cover-letter is a skill published in the GitHub repository jain777/jobclaw-skills (5 stars, last pushed 3mo ago), licensed MIT. It adds 74 tokens to every session and 1,277 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Writing and docs
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens