← ClaudeAtlas

jobhunt-resumelisted

Tailors the user's resume to one job posting using only the experience in jobhunt/profile.md: picks the most relevant roles and achievements, reorders and rewords them in the posting's language, and runs ats_match.py to report keyword coverage, missing terms and over-used words. Missing terms the user truly lacks are reported as gaps, never inserted. Ends with a truth check against the profile. Use when the user says "tailor my resume", "rewrite my CV for this job", "will my resume pass the ATS", "match my resume to this posting", "what keywords am I missing", or "make my resume stronger".
vivekbhange-hub/job-hunt-skill · ★ 0 · Data & Documents · score 75
Install: claude install-skill vivekbhange-hub/job-hunt-skill
# Tailor a resume Purpose: produce a resume for one posting that a recruiter can scan in ten seconds and an applicant tracking system can match, while every line stays true. Tailoring means choosing, ordering and rewording real experience. It never means adding experience the user does not have. ## Inputs - `jobhunt/profile.md` (required). If missing, stop and run `jobhunt-profile`. - The posting: `jobhunt/roles/<slug>/posting.md`, or a file/text the user gives (save it there first). If `decode.md` exists, use its must-haves. - Optional: the user's current resume, for layout and tone. ## Outputs - `jobhunt/roles/<slug>/resume.md`: the tailored resume in plain markdown (easy to paste into Word, Google Docs or an online form). - `jobhunt/roles/<slug>/ats-report.md`: keyword report before and after. - `jobhunt/roles/<slug>/gaps.md`: requirements the profile cannot support and how to close each one. ## Steps 1. Read the profile and the posting. List the must-haves (from `decode.md` if present, else pull them from the posting yourself). 2. Baseline: if the user has a current resume file, run `python3 "${CLAUDE_SKILL_DIR}/ats_match.py" --posting jobhunt/roles/<slug>/posting.md --resume <current resume> --json` and keep the coverage number for comparison. On Windows, `python` instead of `python3` is fine. 3. Map each must-have to profile evidence: role, achievement line, number and its tag (`[exact]`, `[estimate]`, `[range]`). Anything with no evidence go