Resume Builder — resume-deck.mdx into the user's own .docx
The user's template is the toolchain; the build copies its look, never a re-styled copy. Not for what
the resume says (manage step 9 designs resume-skeleton.md) or a pptx (deck-builder).
Engine, run from the workspace root: python3 ${CLAUDE_PLUGIN_ROOT}/skills/resume-builder/scripts/resume.py <cmd>
(catalog, build, render; one JSON object each). Detail: references/resume.md.
Process
- Catalog.
catalog --template template/<file>.docx: paragraph styles (id, name, count, sample,
suggested role) and looks (each distinct size, weight, colour, list once, with its text).
- Front matter. In
resume-deck.mdx: template:, pages: (the user's budget), and one mapping.
styles: role → paragraph style when the template has real styles; samples: role → the opening
text of the template paragraph whose look it takes when every line is Normal.
Roles: # name, ## section, ### entry, - bullet, plain body; any other {role} text.
- Build.
build copies the template, drops its sample body, writes each line in its role's look
(numbering included), keeps the photo on the first paragraph. A role mapped nowhere, a style the
template lacks, or a sample text no paragraph starts with is refused before anything is written.
- Final checks. The build output carries
warnings (an unconfirmed [확인 필요: …] line is kept
and named) and ai_traces: {removed, reported}: an AI disclaimer left in alt text ("AI-generated
content may be incorrect") is removed; an AI tool named in the document properties or an AI phrase
in the visible text is reported and never deleted. Say each reported item to the user.
Nothing is called submittable before python3 ${CLAUDE_PLUGIN_ROOT}/scripts/office_render.py final-check [--dir build] [--allow "Claude Code,Codex"] [--author NAME] has run over resume.docx and resume.pdf:
one verdict per file (깨끗함 or the list), exit non-zero on any finding. It checks alt-text
disclaimers (removed), document properties naming an AI tool or a library (--author rewrites
creator and last editor in the docx), and text, notes and PDF metadata for AI phrases and work
annotations ([확인 필요, TODO, FIXME, (본인 확인, Generated with, Co-Authored-By, a model as
writer). Findings are reported, never deleted. --allow lists the tools the person really lists as
their own skills. Say every finding; the person decides.
- Render. Only when the user says:
render writes build/resume.pdf, counts pages against pages:,
rewrites the page previews build/pages/resume-p-N.png (stale ones deleted) and prints the
final_check verdicts.
- Review. After every render, not only when over budget, run
render-review on the PDF and its fresh previews.
- Fit. Over budget:
over_lines is the number of text lines past the last allowed page. Propose
cuts with their line counts (a section, a block to one bullet) and wait. Cut text, never type size,
line spacing or margins. Then render and review again.
The user's material never goes to git: the engine refuses a template, source or output a git repository
would carry (.gitignore it or work outside it).
Output Template
이력서 <빌드함 | 안 함> — <paragraphs>줄, 템플릿 <file>
매핑: <styles | samples>로 <roles>
최종 검사: final-check <파일별 깨끗함 | n건 (<항목>)> · AI 흔적 <removed>건 제거 · [확인 필요] <n>건
렌더: <pages>쪽 / 예산 <pages>쪽 · 넘친 줄 <over_lines | 없음 | 렌더 안 함>
정하실 것: <잘라낼 후보와 줄 수 | 없음>
What Claude Does / What You Do
| Claude |
You |
| Lists the template's styles and looks, proposes the role mapping |
Confirm the mapping; say which lines are which when the template does not |
| Builds into your template, keeps the photo, runs the final AI-trace check |
Provide the template and resume-deck.mdx; keep both out of git |
| Reports every unconfirmed line and every reported AI trace |
Answer [확인 필요] lines; decide what to do with a reported phrase |
Renders when told, sizes the cut by over_lines, waits |
Say when to render; choose what to cut |
Related Skills
manage — step 9 designs the resume (resume-skeleton.md) and calls this skill to build it
render-review — page-by-page review of the rendered PDF
deck-builder — the pptx counterpart; same renderer and the same final AI-trace check
write:like-me — the voice of every sentence written into the source
1---2name: resume-builder3effort: medium4description: >-5 Use when a resume must be written into the user's own Word template: "이력서 만들어줘", "이력서 docx",6 "Word 템플릿에 이력서", "resume docx", "build my resume from this template". Catalog, build, check, PDF, fit.7scenarios:8 - "Build my resume into this Word template from resume-deck.mdx, then render the PDF."9 - "The resume is two lines over one page — tell me what to cut."10 - "Map this template's lines to roles: it is all Normal, only the run format differs."11 - "이력서 만들어줘. 내 템플릿 docx 그대로 쓰고 사진도 유지해줘"12 - "이력서 docx 뽑고 PDF로 페이지 수 확인해줘"13 - "Word 템플릿에 이력서 채워줘, 한 장에 맞게"14compatibility:15 required:16 - python 3.9+ (stdlib only)17 recommended:18 - LibreOffice (soffice on PATH) or DECK_RENDER_DOCKER=<image> — `render` needs it; catalog and build do not19 - pdftotext (poppler) — `over_lines` needs it20 remote_mcp_note: >-21 LibreOffice가 없으면 `build`까지는 동작하고 `render`만 멈춥니다. 페이지 수와 넘친 줄 수는 렌더한22 PDF에서만 알 수 있으니 가능하면 설치하세요.23metadata:24 source: https://skillmd.com/skills/newkayak12/resume-builder25---2627# Resume Builder — resume-deck.mdx into the user's own .docx2829The user's template is the toolchain; the build copies its look, never a re-styled copy. **Not for** what30the resume says (`manage` step 9 designs `resume-skeleton.md`) or a pptx (`deck-builder`).3132Engine, run from the workspace root: `python3 ${CLAUDE_PLUGIN_ROOT}/skills/resume-builder/scripts/resume.py <cmd>`33(`catalog`, `build`, `render`; one JSON object each). Detail: `references/resume.md`.3435## Process36371. **Catalog.** `catalog --template template/<file>.docx`: paragraph styles (id, name, count, sample,38 suggested role) and `looks` (each distinct size, weight, colour, list once, with its text).392. **Front matter.** In `resume-deck.mdx`: `template:`, `pages:` (the user's budget), and one mapping.40 `styles:` role → paragraph style when the template has real styles; `samples:` role → the opening41 text of the template paragraph whose look it takes when every line is `Normal`.42 Roles: `#` name, `##` section, `###` entry, `-` bullet, plain body; any other `{role} text`.433. **Build.** `build` copies the template, drops its sample body, writes each line in its role's look44 (numbering included), keeps the photo on the first paragraph. A role mapped nowhere, a style the45 template lacks, or a sample text no paragraph starts with is refused before anything is written.464. **Final checks.** The build output carries `warnings` (an unconfirmed `[확인 필요: …]` line is kept47 and named) and `ai_traces: {removed, reported}`: an AI disclaimer left in alt text ("AI-generated48 content may be incorrect") is removed; an AI tool named in the document properties or an AI phrase49 in the visible text is reported and never deleted. Say each `reported` item to the user.50 Nothing is called submittable before `python3 ${CLAUDE_PLUGIN_ROOT}/scripts/office_render.py final-check51 [--dir build] [--allow "Claude Code,Codex"] [--author NAME]` has run over `resume.docx` and `resume.pdf`:52 one verdict per file (`깨끗함` or the list), exit non-zero on any finding. It checks alt-text53 disclaimers (removed), document properties naming an AI tool or a library (`--author` rewrites54 creator and last editor in the docx), and text, notes and PDF metadata for AI phrases and work55 annotations (`[확인 필요`, `TODO`, `FIXME`, `(본인 확인`, `Generated with`, `Co-Authored-By`, a model as56 writer). Findings are reported, never deleted. `--allow` lists the tools the person really lists as57 their own skills. Say every finding; the person decides.585. **Render.** Only when the user says: `render` writes `build/resume.pdf`, counts pages against `pages:`,59 rewrites the page previews `build/pages/resume-p-N.png` (stale ones deleted) and prints the60 `final_check` verdicts.616. **Review.** After every render, not only when over budget, run `render-review` on the PDF and its fresh previews.627. **Fit.** Over budget: `over_lines` is the number of text lines past the last allowed page. Propose63 cuts with their line counts (a section, a block to one bullet) and wait. Cut text, never type size,64 line spacing or margins. Then render and review again.6566The user's material never goes to git: the engine refuses a template, source or output a git repository67would carry (`.gitignore` it or work outside it).6869## Output Template7071```72이력서 <빌드함 | 안 함> — <paragraphs>줄, 템플릿 <file>73매핑: <styles | samples>로 <roles>74최종 검사: final-check <파일별 깨끗함 | n건 (<항목>)> · AI 흔적 <removed>건 제거 · [확인 필요] <n>건75렌더: <pages>쪽 / 예산 <pages>쪽 · 넘친 줄 <over_lines | 없음 | 렌더 안 함>76정하실 것: <잘라낼 후보와 줄 수 | 없음>77```7879## What Claude Does / What You Do8081| Claude | You |82|---|---|83| Lists the template's styles and looks, proposes the role mapping | Confirm the mapping; say which lines are which when the template does not |84| Builds into your template, keeps the photo, runs the final AI-trace check | Provide the template and `resume-deck.mdx`; keep both out of git |85| Reports every unconfirmed line and every reported AI trace | Answer `[확인 필요]` lines; decide what to do with a reported phrase |86| Renders when told, sizes the cut by `over_lines`, waits | Say when to render; choose what to cut |8788## Related Skills8990- `manage` — step 9 designs the resume (`resume-skeleton.md`) and calls this skill to build it91- `render-review` — page-by-page review of the rendered PDF92- `deck-builder` — the pptx counterpart; same renderer and the same final AI-trace check93- `write:like-me` — the voice of every sentence written into the source