cover-letter-genlisted

Generate ATS-optimized, company-specific cover letters for career-ops job applications. Paste a job description or provide a company name/URL → tailored cover letter in markdown, ready to attach or submit. Trigger when: the user asks to "generate cover letter", "write cover letter", "cover letter for this job", "/cover-letter", "tailor cover letter", or "company-specific cover letter"; the user pastes a job description; the user names a company and wants a targeted application letter; or the user wants to apply to a role with a customized, ATS-safe cover letter. Key capabilities: extracts company intel from JD (pain points, tech stack, culture signals, repeated keywords); scores achievements from cv.md against JD keywords (3pt direct match, 2pt relevant, 1pt loose, 0pt irrelevant); archetype-based narrative framing (LLMOps, Agentic, Technical AI PM, Solutions Architect, FDE, Transformation); 4-paragraph structure (hook with role+company, proof with top scored achievements, company-specific reasoning, close wi
Tekkiiiii/the-agency · ★ 0 · AI & Automation · score 68

Install: claude install-skill Tekkiiiii/the-agency

# Cover Letter Generator — career-ops Mode ## Core Mission Generate a compelling, ATS-optimized, company-specific cover letter that complements the career-ops PDF CV. One cover letter per application — never generic. Stops before submission. --- ## Input Resolution (in priority order) 1. **Pasted JD text** — if the user pasted raw JD text, use it directly 2. **URL** — if a job URL was provided, fetch via WebFetch or Playwright 3. **Company name** — if only a company name was given, search for the active JD in `data/pipeline.md` or `reports/` 4. **Context files to read always:** - `cv.md` — canonical CV - `config/profile.yml` — candidate narrative, archetype, target roles - `data/applications.md` — check if an evaluation report exists for this company --- ## Step 1 — Company Intel Extraction From the JD, extract: - Company name and industry - Role title and seniority level - Top 3 pain points / challenges the role solves - Must-have tech stack requirements - Culture signals (startup / enterprise / remote-first / etc.) - Tone of the JD writing (formal, direct, playful, technical) - 2-3 specific keywords or phrases used repeatedly --- ## Step 2 — Achievement Scoring From `cv.md`, extract all achievements / bullet points. **Score each achievement** against the JD keywords: - 3 pts: direct tech stack match + quantified result - 2 pts: relevant skill match (non-quantified) OR quantified result (no skill match) - 1 pt: loosely relevant - 0 pts: irrelevant Select