skills/cover-letter/SKILL.md
Write a specific, non-generic cover letter that connects your evidence to the role. Use when asked to write a cover letter, an application letter, or a note to accompany a resume. Produces a tight 3–4 paragraph letter — a real hook, two evidence paragraphs mapping your proof to the job's needs, and a confident close — tailored to the company, ready to export as a designed PDF.
npx skillsauth add mohitagw15856/pm-claude-skills cover-letterInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Most cover letters are throat-clearing the reader skips. A good one does one job: connect your specific evidence to this company's specific need, in a voice that sounds like a person. This skill writes a tight, tailored letter — no "I am writing to apply for…", no restating the resume — that earns the read.
Ask for these only if they aren't already provided:
A 3–4 paragraph letter (≈250–350 words):
[Name] · [email] · [phone] · [date] Dear [hiring manager name, or "Hiring Team" if unknown],
Hook (1 short para) — open with a specific reason you're writing to them — a genuine connection to their product/mission/moment — and the role you want. No "I am writing to apply."
Evidence (1–2 paras) — the heart: take the role's top 2–3 needs and show, with a concrete result each, that you've done it. Map your proof to their problem; don't recap the resume — interpret it.
Close (1 short para) — what you'd bring, an honest note of enthusiasm, and a forward-looking line ("I'd love to talk about…"). Confident, not desperate.
Sincerely, [Name]
Voice note (for the user): keep it human — contractions, active voice, no thesaurus words. Read it aloud; if it sounds like a robot, cut.
Modern cover-letter practice — specific hook, evidence-to-need mapping, human voice.
business
Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.
development
Route a fuzzy request to the right skill in this library. Use when the user is unsure which skill fits, asks 'which skill should I use for X', describes a task without naming a skill, or when a request could plausibly match several skills. Produces a best-fit recommendation with the inputs to gather, a runner-up with the tie-breaker, and a workflow recipe when the job spans multiple skills.
testing
Triage a vulnerability or scanner finding — assess real severity, exploitability, and how urgently to fix. Use when asked to triage a CVE, prioritize scanner/pentest findings, assess a vuln's risk, or decide what to patch first. Produces a triage verdict: CVSS-informed severity adjusted for your context, exploitability, real risk, a fix/mitigation, and an SLA — so you fix what matters, not just what's red.
development
Stand up a Voice of Customer (VoC) program that turns feedback into action. Use when asked to build a VoC program, design a customer feedback loop, consolidate feedback sources, or set up a closed-loop feedback process. Produces a VoC program design — objectives, feedback sources and channels, a taxonomy, collection and analysis cadence, closed-loop routing, ownership, and success metrics.