job-application
# Job Application This skill tailors a CV and cover letter to a specific job description by analyzing role requirements, identifying ATS keywords, and flagging experience gaps. Use it when preparing to apply for a position to produce an optimized CV summary, reframed experience bullets, and a personalized cover letter that authentically connects the candidate's background to the role's priorities while maintaining readability beyond ATS systems.
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills /tmp/job-application && cp -r /tmp/job-application/plugins/pm-business/skills/job-application ~/.claude/skills/job-applicationSKILL.md
# 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 ## Anti-Patterns - [ ] Do not fabricate or embellish experience — only use real achievements from the provided CV - [ ] Do not use the same cover letter template for every role — every letter must reference specific details of the job description - [ ] Do not address selection criteria that aren't in the JD — match keywords the employer actually used - [ ] Do not omit ATS optimisation — ensure role-specific keywords from the JD appear naturally in the CV summary - [ ] Do not write a cover letter that re-summarises the CV — it must add context and motivation, not repeat bullet points ## 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"
Conduct a structured ethical review of an AI or ML feature, model, or product. Use when preparing to deploy an AI system, assessing algorithmic risk, auditing a model for bias, or producing a responsible AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with a risk tier score, pre-deployment checklist, and prioritised mitigations.
Structure 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.
Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context, success criteria, constraints, edge cases, and out-of-scope boundaries.
Design statistically rigorous A/B tests and interpret experiment results. Use when asked to design an experiment, run an A/B test, calculate sample size, interpret test results, or assess whether an experiment was successful. Produces a complete experiment design with hypothesis, sample size, run time, success criteria, and risk flags — or a results interpretation with ship/iterate/kill recommendation.
Synthesises user signals from multiple research sources into a unified, weighted insight brief. Use when you have data from interviews, support tickets, NPS verbatims, app reviews, or sales calls and need to reconcile contradictions, surface the underlying need behind requests, or answer 'what are users really telling us'. Produces ranked insights with confidence ratings, source weighting rationale, divergent signal analysis by user segment, and a research gap identification section.
Structure a product data analysis, metric deep-dive, funnel analysis, or cohort study. Use when asked to analyse product metrics, investigate a drop in conversion, explain a data change to stakeholders, or find the root cause of a metric movement. Produces a structured analysis with question, root cause, confidence level, and recommended action.
Interpret product metrics against goals and surface actionable signals. Use when asked to analyse product health, review key metrics, investigate a performance issue, produce a health report, or assess product-market fit signals. Produces a structured health report with RAG status, trend analysis, root cause hypotheses, and prioritised actions.
Structure a retention analysis, churn investigation, or engagement deep-dive for any product team. Use when asked to analyse user retention, investigate churn, measure DAU/MAU, or build a retention improvement plan. Produces a retention snapshot with root cause hypotheses, aha-moment correlation, and prioritised interventions.