Skip to content
* CASE STUDY Nº 04 · PERSONAL · 2026

Resume Skills Toolkit

Claude Code skills that turn resume-building into a declarative pipeline - from the design in Pencil to a PDF compiled with LaTeX and Tectonic, ATS-parseable and bilingual by construction.

3 CHAINED SKILLS
2 LOCALES (PT-BR / EN)
1 COMMAND TO PDF
ATS PARSEABLE OUTPUT
i THE PROBLEM

A resume that impresses a human usually confuses a machine.

Almost every vacancy passes through an ATS first, and ATS parsers read the PDF top to bottom by following coordinates. Two-column layouts, text boxes, and pretty icons turn into scrambled text: the title detached from the company, a date stuck in the wrong place, a whole section vanishing because it was an image. The document looks great and still arrives broken on the other side.

And there was the repetitive friction: each vacancy wanted a slightly different version, in Portuguese or English, emphasizing different keywords. Hand-editing everything, keeping two languages in sync, and still exporting a PDF the parser understands - that doesn't scale.

ii THE IDEA

Treat the resume like a build: one source, written rules, reproducible output.

  • - Personal project: I wanted to stop hand-editing my resume every time a different vacancy showed up.
  • - A good-looking resume is almost never a parseable one - a graphical editor exports a PDF the ATS can't read properly.
  • - The idea was to turn resume assembly into a declarative pipeline: one data source, written rules, the same output every time.
  • - And to let Claude Code drive that pipeline via skills, from .pen to PDF, in both pt-BR and English.
iii STACK & ARCHITECTURE
AGENT
Claude CodeSKILL.mdHooks
SOURCE & TYPESETTING
Pencil (.pen)LaTeXTectonic
OUTPUT & STANDARDS
PDFSingle columnStandard headingsBilingual
iv PROCESS
01

Treat the skill as a contract, not a throwaway prompt.

Each SKILL.md has frontmatter with a name and description, versioned instructions, and the files it needs. Claude Code loads only what matters when it matters - so you can trust the behavior to repeat.

02

The .pen as the source of truth for content and structure.

The Pencil document holds the data and the layout decisions. The skill reads from it and generates the .tex - no copying text by hand between design and resume.

03

LaTeX for typography, Tectonic so I never fight TeX Live.

Tectonic is a self-contained TeX/LaTeX engine: it fetches missing packages on demand, runs the right number of passes on its own, and produces a reproducible build. No full distribution to install just to compile a PDF.

04

Match keywords to the vacancy without inventing experience.

The last skill compares the resume against the job description and suggests where to reinforce real terms. It adjusts emphasis and ordering, never the truth of what I actually did.

v RESULTS

Building a resume stopped being manual work and became a pipeline I run, trust, and repeat - fast, consistent, and ATS-safe.

  • - From .pen to a typographically correct PDF in one command - repeatable, with no manual copy-and-paste step.
  • - Single-column output with standard headings: the ATS parser reads in the right order instead of scrambling columns and ignoring graphics.
  • - The pt-BR and EN versions come from the same source, so the two never drift apart by accident.
  • - Keyword tailoring makes each submission more aligned to the vacancy without rewriting the document from scratch.
NEXT CASE STUDY

Research MCP Server