job-application

$npx mdskill add mohitagw15856/pm-claude-skills/job-application

This skill tailors a CV and cover letter to a specific job description — optimising for ATS keyword matching while keeping the writing human and compelling. It also flags gaps between the candidate's profile and the role requirements.

SKILL.md

.github/skills/job-applicationView on GitHub ↗
---
name: job-application
description: "Tailor a CV and cover letter to a specific job description. Use when asked to write a cover letter, tailor a CV or resume, optimise for ATS, match a job description, or prepare a job application. Produces an ATS-optimised tailored CV summary and a personalised cover letter."
---

# Job Application Skill

This skill tailors a CV and cover letter to a specific job description — optimising for ATS keyword matching while keeping the writing human and compelling. It also flags gaps between the candidate's profile and the role requirements.

## Required Inputs

Ask the user for these if not provided:
- **Job description** (paste in full)
- **Current CV / resume** (paste or describe key experience, roles, and skills)
- **The specific thing that excites them about this role** (used in the cover letter — must be genuine)
- **Any particular strengths to emphasise** (optional)
- **Any gaps they're worried about** (optional — helps address them proactively)

## Output Structure

---

## Part 1: JD Analysis

Before writing anything, analyse the job description and output:

### Must-Have Requirements
[List explicit requirements from the JD — qualifications, years of experience, specific skills]

### Key Themes in the JD
[3–5 themes that repeat or are emphasised — these are the keywords and priorities the hiring manager cares about most]

### ATS Keywords to Include
[List 10–15 specific keywords and phrases from the JD that should appear in the CV and cover letter. Include: tools, methodologies, job titles, skills]

### Gaps Assessment
[Honest comparison between the candidate's profile and the JD requirements. Flag: "Strong match" / "Partial match — can be positioned as X" / "Gap — address in cover letter or don't apply"]

---

## Part 2: Tailored CV Summary / Profile Section

Rewrite or create the candidate's CV summary/profile section (the 3–5 lines at the top of a CV) specifically for this role:

**Rules:**
- Open with the job title or a near-match (ATS reward)
- Include 2–3 keywords from the JD naturally
- Reference years of experience in the relevant area
- End with a forward-looking line connecting their background to what this role needs
- Keep to 60–80 words maximum

**Tailored CV Summary:**
[Write the summary]

---

## Part 3: Experience Bullet Point Rewrites

For the 2–3 most relevant roles on the CV, suggest how to reframe existing bullet points to better match this JD:

**[Role Title] at [Company]**

| Original Bullet | Tailored Version | Why |
|---|---|---|
| [Candidate's original text] | [Improved version with JD keywords and stronger impact framing] | [Brief note on what changed] |

**Rules for bullet point rewrites:**
- Lead with an action verb
- Include a quantified outcome where possible (%, £, time saved, users impacted)
- Weave in JD keywords naturally — not forced
- Keep to one line (2 max)

---

## Part 4: Cover Letter

**Format:** 3 paragraphs + closing. Target: 250–350 words. Anything longer won't be read.

---

[Hiring Manager's name if known, otherwise "Hiring Team"]

**Paragraph 1 — The Hook (Why this role, specifically)**
[2–4 sentences. Reference something specific about the company or role — not generic enthusiasm. The candidate's genuine reason for applying goes here. This is what makes it human. Generic openers like "I am writing to apply for..." are filtered out mentally within 3 seconds.]

**Paragraph 2 — The Evidence (Why them)**
[3–5 sentences. 2–3 specific examples from their background that directly address the JD's key themes. Use the language of the JD. Include at least one quantified achievement. Don't list everything — pick the 2–3 strongest matches and go deep, not broad.]

**Paragraph 3 — The Forward Bridge (Why now)**
[2–3 sentences. Connect their trajectory to this role. Why is this the logical next step? What do they want to learn or build that this role enables? This should feel like the natural continuation of their career, not just "I want a new challenge."]

---

I'd welcome the chance to discuss how my background could contribute to [Company/Team]. Thank you for your time.

[Name]
[Email] | [LinkedIn URL] | [Location if relevant]

---

## Part 5: Application Checklist

Before submitting:
- [ ] CV summary updated with tailored version above
- [ ] ATS keywords appear in CV body (not just summary)
- [ ] Cover letter is under 400 words
- [ ] Company name is spelled correctly throughout (sounds obvious — it happens)
- [ ] No generic phrases: "passionate about," "results-driven," "team player" without evidence
- [ ] LinkedIn profile updated to match CV (recruiters cross-check)
- [ ] Role title in subject line if emailing directly

---

## Quality Checks

- [ ] JD analysis completed before writing (not skipped)
- [ ] ATS keywords are integrated naturally (not stuffed)
- [ ] Cover letter opens with something specific (not a generic opener)
- [ ] Paragraph 2 includes at least one quantified achievement
- [ ] Cover letter is 250–350 words
- [ ] Gaps are either addressed or strategically omitted

## Example Trigger Phrases

- "Help me apply for this job: [paste JD]"
- "Tailor my CV for this role: [paste JD + CV]"
- "Write a cover letter for [role] at [company]"
- "Optimise my application for ATS for this job description"

More from mohitagw15856/pm-claude-skills

SkillDescription
360-feedback-templateDesign a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.
ab-test-plannerDesign statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.
accessibility-auditGenerate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.
account-planBuild a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.
aeo-optimizerOptimize an article for Answer Engine Optimization (AEO) — restructuring content so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Rewrites headings as questions, drops 50-80 word answer capsules, audits paragraph length, and flags trust signals. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines.
ai-ethics-reviewConduct an ethical review of an AI or ML feature, model, or product. Use when asked to run an AI ethics review, assess AI risks, audit a model for bias, or produce an AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with prioritised mitigations.
ai-product-canvasStructure AI and ML product decisions with the rigour of any product decision. Use when building AI-powered features, evaluating LLM integrations, designing AI products, or assessing AI readiness. Produces a complete AI product canvas covering problem definition, model approach, data requirements, evaluation framework, UX design, responsible AI checklist, and launch monitoring plan.
ambiguity-resolverStructure vague opportunities and unclear briefs into actionable one-page problem statements. Use when asked to clarify a vague brief, frame an undefined problem, make sense of an unclear opportunity, or when the user says 'we need to figure out what to do about X' or 'I've been asked to look into Y'. Produces a structured problem brief with reframed questions, scoped boundaries, and a minimum viable research plan.
api-docs-writerWrite clear, developer-facing API documentation. Use when asked to document an API endpoint, write API reference docs, create a developer guide, or turn a raw spec/Postman collection into documentation. Produces endpoint documentation with descriptions, parameters, request/response examples, and error codes.
api-versioning-strategyWrite an API versioning strategy document for a service or API platform. Use when asked to define versioning policy, plan API deprecation, classify breaking changes, or document version lifecycle. Produces a complete versioning strategy with breaking-change classification table, deprecation timeline, migration guide template, and client communication template.