resume-jd-tune

Original：🇺🇸 English
Translated

Tailor an existing resume to a specific job description. Extracts hard-skill keywords from the JD, ensures they appear in the Skills section and most-recent-role bullets, adds a bridging title line if the user's title differs materially from the target. Reports projected Jobscan match score before and after. Triggers on: tailor my resume, tune for JD, match this job description, /resume tune, optimize for this role.

4installs
Sourcekunalrawat425/claude-resume
Added on

NPX Install

npx skill4agent add kunalrawat425/claude-resume resume-jd-tune

Tags

Translated version includes tags in frontmatter
resume-optimizationjob-description-tuningATS-compliancejobscan-matchresume-tailoring

SKILL.md Content

View Translation Comparison →

Resume JD Tune: Job-Description Keyword Tuner

Invocation: 
/resume tune <resume-file> <jd-file-or-url>
Scripts: Inline (no script needed; runs in the orchestrator).
Tailors an existing ATS-safe resume to a specific job description by mirroring the JD's hard-skill keywords and bridging title vocabulary. Targets Jobscan's 75–80% match benchmark.

Behavior

Always interview the user briefly before tuning. Use 
mcp__conductor__AskUserQuestion
(one question per call) to ask:
  1. Confirm target role title from JD vs. user's actual seniority claim
  2. For each JD hard-skill the resume doesn't already mention — does the user actually have this skill? (Yes / No / Limited exposure)
  3. Tone preference for any rewritten bullets (Conservative / Modern / Balanced)
  4. Whether to add a bridging title line if titles differ materially
Never claim a skill the user marks "No". Flag the gap in the report instead.

Quick Reference

StepWhat it does
1Brief interview (skill confirmation, tone, bridging-title preference) via AskUserQuestion.
2Parse the JD — extract hard skills, required tools, exact title, key phrases.
3Diff against the resume's Skills section + most-recent-role bullets.
4Insert missing JD keywords into Skills (only if user confirmed they have the skill).
5Rewrite 1–2 bullets in the most-recent role to use JD's exact phrasing.
6Add bridging title line under the name if the user's title differs from the JD title.
7Report projected match score before/after, plus skill gaps.

Rules

  • Never claim a skill the user doesn't have. If the JD lists "Kafka" and the user has never touched it, do NOT add it. Flag the gap to the user.
  • Mirror exact phrasing where possible. If the JD says "Kubernetes," include both "Kubernetes" and "K8s" in Skills (one parses each variant).
  • Acronym + expansion once. "SEO (Search Engine Optimization)" the first time only.
  • Bridging title is optional. Only add if the user's title is materially different from the JD's. "Senior Software Engineer" → "Senior Software Engineer | Backend Platform Engineer" is fine.
  • Don't keyword-stuff. AI-layered ATS in 2026 (Jobscan AI, Eightfold) cross-check claims against bullet evidence and penalize unsupported skills.

Output

A modified DOCX named 
<original-name>_tuned_for_<jd-slug>.docx
, plus a side-by-side report:
JD: Senior Backend Engineer @ AcmeCo

Match score:    72%  →  87%
Hard skills:    14/19 → 19/19  (added: gRPC, Postgres, Kubernetes)
Title bridge:   added "| Backend Platform Engineer"
Bullets edited: 2 (Aerem, Sky2c)
Skill gaps:     [none — user had all JD skills]
If there are skill gaps, the report calls them out so the user can decide whether to add evidence in a different format (project, certification, side work).

Sources

Match-score benchmarks from Jobscan, Resume Worded, and Enhancv (2026). Methodology: keyword overlap weighted by section (Skills 1.0x, recent-role bullets 0.6x, summary 0.4x, older bullets 0.2x).