Resume Builder

Build, rewrite, and tailor premium white-collar resumes from real candidate information, then render the final resume to PDF with Typst. Use when the user wa...

Security Scan

The skill's code and instructions largely match a resume-to-PDF workflow, but there are coherence problems (notably a missing Typst template asset) that should be resolved before trusting or running it.

Purpose & Capability

The name, description, SKILL.md, and scripts all describe building a resume and compiling it to PDF with Typst, which is coherent with requiring python3 and typst. However, the renderer script expects a bundled template at assets/resume.typ (skill_root/assets/resume.typ), but that file is not present in the manifest. The claim of a "bundled renderer" is therefore inconsistent with the provided files.

Instruction Scope

SKILL.md instructions are narrowly scoped to: collect candidate facts, produce a JSON following the provided schema, run the included renderer script, and compile with typst. The agent is directed to create and report files in an output directory only. The runtime instructions do not request unrelated files, credentials, or external endpoints. The only runtime action of note is invoking the local typst binary via subprocess, which is expected for PDF compilation.

Install Mechanism

There is no install spec (instruction-only), and included code is a small Python script. No external downloads, package installs, or unusual install locations are specified. This is low-risk from an install mechanism perspective.

Credentials

The skill requests no environment variables, no credentials, and no config paths. This is proportionate for a resume renderer that runs locally.

Persistence & Privilege

The skill is not always-enabled, has no special persistence or system-wide config modification, and writes only to the output directory provided by the user. It does invoke an external binary (typst) but that is expected and not itself a privilege escalation.

What to consider before installing

This skill appears to do what it says (generate a structured resume JSON, produce Typst source, and compile a PDF), but the package is missing the Typst template it expects (assets/resume.typ). Before installing or running: - Verify typst is installed from a trusted source, since the script invokes the local typst binary to compile PDFs. - Ensure the missing template (assets/resume.typ) is present and review it for unwanted network calls or placeholders. Without that file the renderer will fail or be unusable. - Inspect scripts/render_resume.py (already small and readable) yourself — it reads the input JSON, writes files to the provided output directory, copies a local template, and runs typst; it does not contact external endpoints or require credentials. - Provide input only for candidates whose PII you are comfortable writing to disk; the script writes resume.json and resume.pdf to the output directory. - Run the tool in a sandbox or controlled environment if you cannot confirm the template or repository provenance. If the owner/homepage are important to you, validate the upstream repo and packaging before use.

Use this skill when the user wants a premium, professional white-collar resume.

This skill is for:

• building a resume from raw experience notes
• rewriting an existing resume
• tailoring a resume to a target job description
• generating a polished PDF resume with Typst

It supports white-collar roles such as:

• software engineering, data, AI, QA, DevOps
• product and project management
• operations, growth, and e-commerce
• marketing, branding, and campaign roles
• sales, presales, and customer success
• HR, recruiting, finance, and administration

Outcome

The task is only complete when the final resume has been rendered to PDF with Typst.

Produce:

• a structured resume draft
• a Typst source file
• a final PDF resume

If PDF compilation fails, do not present the task as complete.

Workflow

1. Determine the resume task

Identify whether the user needs:

• a new resume from scratch
• a rewrite of an existing resume
• a JD-targeted resume
• a formatting refresh with PDF output

2. Extract only real candidate facts

Build a structured candidate profile from the provided material:

• name and contact details
• target role
• summary highlights
• work experience
• project experience
• education
• skills, tools, certifications, languages, links

Do not invent missing facts.

If key information is missing, ask for it or generate a conservative version that makes the gaps obvious.

3. Rewrite for white-collar hiring standards

Apply the writing rules from role-writing-guidelines.md.

Prioritize:

• business impact over task lists
• strong verbs over weak phrasing
• clear ownership and scope
• concrete outcomes when provided
• concise, executive-grade tone

Avoid:

• empty buzzwords
• student-style filler
• unsupported metrics
• generic claims like "good communication skills"

4. Tailor to the target job when a JD is provided

Read the JD and align the resume by:

• prioritizing the most relevant experience first
• reflecting the user's real match to the role
• emphasizing keywords that are already supported by the candidate's background

Do not insert technologies, industries, achievements, or responsibilities the user did not provide.

5. Structure the resume before rendering

Use the schema in resume-schema.md.

Default section order:

1. Header
2. Professional Summary
3. Core Skills
4. Experience
5. Selected Projects
6. Education
7. Certifications, Languages, or Links when relevant

Keep the result compact and premium. Default target length is one page for early to mid-career profiles and at most two pages for senior profiles.

6. Render with Typst and compile to PDF

Use the bundled renderer:

python3 scripts/render_resume.py --input candidate.json --output-dir out

The renderer will:

• normalize the input data
• generate resume.typ
• compile resume.pdf with typst

Success requires resume.pdf to exist.

Output Rules

• Return a concise summary of what was generated.
• State the output file paths clearly.
• If the PDF was compiled successfully, say so explicitly.
• If compilation failed, report the error and stop short of claiming completion.

Style Rules

Default visual style is premium executive:

• restrained, expensive-looking, high-trust layout
• no cheap template effects
• no progress bars, stars, or decorative charts
• strong hierarchy, controlled spacing, and readable density

The final resume should look credible for senior white-collar hiring, not like an auto-generated template.

Scope Boundaries

This skill is for factual resume generation and professional PDF rendering.

It is not for:

• fabricating experience
• inventing metrics or promotions
• guaranteeing interviews or ATS outcomes
• creating overly decorative portfolio layouts