tailor-resume

Installation
SKILL.md

tailor-resume

Inputs

  • Target JD (and score-fit output if available).
  • profile/cv.md and profile/facts.json (source of truth).

Steps

  1. Extract the JD's top 6–8 keywords (languages, frameworks, ML/data tools, responsibilities).
  2. Select content: education first for students; then the 2–3 most relevant experiences/projects by keyword overlap. Drop weak items to stay on one page.
  3. Rewrite bullets: action verb + what + tool + result. Reuse metrics only if present in facts.json. Mirror JD wording only where the fact supports it (e.g. "REST API" if FastAPI service exists).
  4. Reorder the skills line to put JD-matching, evidenced skills first. Never add a skill not in facts.json.skills or a project stack.
  5. Verify: produce a mapping table — each bullet → source fact id (exp1, proj1…). Any bullet without a source is removed or flagged as [NEEDS FACT] and you ask the user.
  6. Output to output/resume-<company>-<role>.md (default) or .tex (simple one-column LaTeX, no exotic packages). Keep to one page: ≤ ~550 words, ≤ 4 bullets per entry.
  7. Show a short diff summary: what moved up, what was cut, keywords covered / still missing (missing ones go back to score-fit gaps, not into the resume).

Rules

  • No invented experience, employers, dates, metrics, or skills. Rephrasing is fine; fabrication is not.
  • Keep contact info and education dates exactly as in facts.json.
  • ATS-friendly: no tables/columns/images in the resume itself; standard headings.
Installs
1
First Seen
Nov 7, 2026