esscott1/job-search-assistant / skills/job-search-assistant/tailored-resume-builder
tailored-resume-builder
VerifiedOn demand only, never scheduled: when the user says 'build ticked resumes' (tracker rows ticked in Build Resume), names tracker rows, or pastes a job description: picks the most relevant true content from the user's full resume and renders a .docx and PDF of at most 3 pages (or fewer when the user asks) in the user's own resume style (resume-style.md, or the plugin's default), plus a Google Doc of the same resume saved straight to the job's Drive folder. Never invents experience; reports gaps instead. Not for scoring (that's job-fit-rubric), not for editing the master inventory, and not for setting up the resume style (that's job-search-profile).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 15.9 KB |
| check_content.py | script | 7.7 KB |
| check_doc_text.py | script | 2.6 KB |
| default-style.md | markdown | 1.3 KB |
| extract_style.py | script | 19.8 KB |
| render_resume.py | script | 32.4 KB |
| resume-style-format.md | markdown | 3.5 KB |
| test_check_content.py | script | 6.3 KB |
| test_check_doc_text.py | script | 2.5 KB |
| test_extract_style.py | script | 7.7 KB |
| test_render_resume.py | script | 14.7 KB |
resume-style-format.md
View on GitHub# Resume style file format (version 1)
A user's resume look is a small Markdown file, `resume-style.md`, kept in their job-search folder next to `job-search-profile.md`. `render_resume.py` reads it and builds the .docx (and PDF) from scratch, so any user's look works and no Word template has to travel through the Drive connector. `default-style.md` in this folder is the style used when the profile names none, and is a complete example.
Like the profile, it's plain text: one `- Key: value` line per setting under a section heading. A skill writes it, and the user can edit it by hand. `render_resume.py` rejects an unknown section, key or value with exit code 2 and names the line.
## Header
- `# Resume style` on the first line.
- `Style format: 1`: required. The renderer refuses other versions.
- `Source: <template file it was converted from, or "plugin default">, <date>`: informational.
- Any other text before the first `##` section is ignored.
## `## Page`
| Key | Value |
|---|---|
| Size | `Letter` or `A4` |
| Margins (in) | `top 0.5, bottom 0.5, left 0.6, right 0.6`, or one number for all four |
## `## Text`
Each line styles one kind of text. The value is a comma-separated list, in any order, of:
- a font name, such as `Calibri` or `Garamond`;
- a size in points, such as `10.5`;
- `bold`, `italic`, `caps`, `underline`;
- `color RRGGBB`, a hex colour such as `color 1F3864`;
- `rule`, for **Section headings** only: a line under the heading.
Anything not given is taken from **Body**: its font, size and colour. Bold, italic, caps and underline are off unless listed.
| Key | Styles |
|---|---|
| Body | Summary, bullets, everything not listed below. Must give a font and a size |
| Name | The name at the top |
| Headline | The role-aligned line under the name |
| Contact | The contact line |
| Section headings | Section titles |
| Company | Employer name on the company line |
| Company description | Accepted so older style files still load, but not used: tailored resumes don't show company descriptions |
| Role | Job title on the role line |
| Location | Locations on company and role lines |
| Dates | Dates on company and role lines |
## `## Layout`
| Key | Value |
|---|---|
| Header alignment | `left` or `center`: name, headline and contact line |
| Header order | `name, headline, contact` in any order |
| Section heading alignment | `left` or `center` |
| Contact separator | Text between contact items. Quote it to keep spaces: `" · "` |
| Section order | Comma-separated, from: `summary, competencies, highlights, experience, education, certifications, additional`. Sections left out aren't shown |
| Section titles | `section = Title` pairs separated by `;`. An empty title (`summary = `) shows the section without a heading. Sections not listed use a plain default title |
| Competencies | `grid N`: a borderless table with N columns (1-4). Or `inline "<separator>"`: one line |
| Bullet | The bullet character, such as `•`, `▪`, `–` |
| Dates | `right`: dates right-aligned on the company and role lines. Or `inline`: after the title, separated by ` \| ` |
| Accomplishments label | A line before each role's bullets, such as `Key Accomplishments:`. Empty for none |
| Space after section heading (pt) | A number |
| Space between roles (pt) | A number |
## `## Not carried over`
A free-form list. When the style was converted from a Word template, this names anything the renderer can't reproduce: images, text boxes, sidebar columns, header or footer content, unusual fonts. The renderer ignores it; it's there so the user knows.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| canvas-designanthropics/skillsCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| docxanthropics/skillsUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| pdfanthropics/skillsUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| pptxanthropics/skillsUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |