Resume Creator
A comprehensive resume creation skill that uses first-principles thinking, Google XYZ format, web research, and iterative visual refinement to craft tailored, professional resumes.
When to Use This Skill
- User wants to create a new resume
- User wants to update/optimize an existing resume
- User mentions a job application, job posting, or target company
- User asks about resume formatting or CV creation
- User wants to tailor their resume for a specific role
Process Overview
Phase 1: Information Gathering
Read existing materials (if available):
- Existing resume (PDF, Word, or text)
- LinkedIn profile screenshots (Claude cannot directly access LinkedIn URLs)
- LinkedIn posts for achievements and speaking engagements
- Portfolio or personal website
Understand the target:
- Job description (if provided)
- Target company and role
- Industry/role type
- Career goals
Research the target company using web search:
- Company culture and values
- Tech stack and engineering practices
- Recent news, funding, products
- What they look for in candidates
- Company AUM/size/metrics for context
- Example searches:
- "{company} engineering blog hiring"
- "{company} careers culture values"
- "{role} at {company} interview what they look for"
- "{company} AUM assets under management" (for finance)
Gather missing information by asking the user:
- Recent experience not on resume
- Specific achievements with metrics
- Skills and technologies used
- Projects and speaking engagements
- Time spent on projects (for speed metrics)
- Client details (AUM, size, industry)
Phase 2: Google XYZ Format Analysis
The XYZ Formula: "Accomplished [X] as measured by [Y] by doing [Z]"
- X = Achievement/outcome (action verb: Built, Architected, Shipped, Led)
- Y = Quantifiable metric (%, time, money, users, accuracy)
- Z = How you did it (method, technology, approach)
Before writing, analyze each bullet:
| Bullet |
X (What) |
Y (Metric) |
Z (How) |
Score |
| Example |
Built connector |
2 weeks, 1000s docs |
Delta API, Redis |
3/3 ✓ |
Target: 100% of bullets should score 3/3
Common metrics to extract from user:
- Time to build ("in 2 weeks", "in 1 week")
- Accuracy improvements ("125% improvement", "90% accuracy", "<3% error rate")
- Scale ("1000s of docs", "400+ rounds", "90+ companies")
- Cost savings ("reducing time from hours to minutes", "50% faster")
- Client context ("$100B+ AUM client", "Fortune 500")
- Audience size ("150+ builders", "100+ attendees")
Phase 3: First-Principles Analysis
Before writing, analyze from first principles:
Research what hiring managers look for:
- Web search: "{role} resume what hiring managers look for 2024"
- Web search: "Google XYZ resume format"
- Understand the <8 second resume scan reality
Alignment analysis:
Create a table mapping:
| Job Requirement | User's Experience | Gap/Strength |
Paul Graham / YC style considerations (for startup roles):
- Lead with what you BUILT, not job titles
- Show speed of execution ("shipped in X weeks", "built in 2 weeks")
- Quantify everything (%, numbers, scale)
- Builder tone: "Built", "Shipped", "Architected", "Won" not "Responsible for"
- Remove corporate buzzwords
Avoid redundancy:
- Check if metrics in bullets duplicate header/subheader info
- Example: Don't say "Fortune 500 clients" in bullet if header says "Serving Fortune 500 clients"
Phase 4: LaTeX Resume Creation
Use the Harvard-style LaTeX template with:
- Clean header (name, location, contact, links)
- No colored header bars - clean white background
- Section order: Experience → Projects & Speaking → Skills → Education → Leadership
- € symbol for currencies
- 1 page maximum (critical)
Key formatting:
- Font: Helvetica Neue (or similar sans-serif)
- Colors: Navy blue (#14-2D-4B / RGB 20,45,75) for sections
- Margins: ~0.5 inches
- Line spacing: 1.05
- Use
\setstretch{1.05} for readability
Punctuation guidelines:
- Use commas or semicolons to connect clauses, NOT em dashes (--)
- Em dashes (--) only for date ranges in headers (e.g., "Sept 2025 -- Present")
- Use semicolons to separate distinct achievements in one bullet
Link formatting:
- Add
[link] in small navy text next to items with LinkedIn/external proof
- Format:
{\color{sectioncolor}\footnotesize[\href{URL}{link}]}
Phase 5: Iterative Visual Refinement
Critical: After creating the LaTeX file, iterate visually:
Compile to PDF:
xelatex -interaction=nonstopmode resume.tex
Check page count: Must be exactly 1 page
- If 2 pages: reduce spacing, tighten text, combine bullets
- Adjust
\titlespacing*{\section}{0pt}{6pt}{2pt} if needed
- Adjust
\setlist[itemize]{itemsep=1pt, parsep=0pt, topsep=1pt}
Check for issues:
- Does it fit on 1 page?
- Is spacing balanced?
- Are there overflow issues?
- Is typography clean?
- Any redundant information?
Iterate until perfect
Phase 6: Final Delivery
- Save final PDF:
Resume_[Name]_[Role]_[Year].pdf
- Keep .tex source file with same naming
- Clean up temp files (.aux, .log, .out)
- Open PDF for user
Content Guidelines
Experience Bullets - XYZ Examples
Strong XYZ bullets:
- Built SharePoint connector in 2 weeks enabling auto-indexing of 1000s of enterprise docs, reducing admin setup from hours to minutes
- Architected Snowflake sub-agent for NL-to-SQL, improving query accuracy by 125%; embedded at $100B+ AUM client, drove 4+ validation cycles
- Built agentic funding extraction with <3% error rate on 400+ rounds, validated against hand-labeled data and proprietary providers
- Delivered DSPy live optimization talk to 150+ builders, featured in global newsletter (50K+ subscribers)
Weak bullets to avoid:
- Responsible for platform development (no metric, no how)
- Worked on various projects (vague)
- Built connector using Redis (no metric, no outcome)
Combining Related Bullets
When two bullets are related, combine them:
- Before: "Architected Snowflake agent" + "Embedded as Field Engineer at client"
- After: "Architected Snowflake sub-agent for NL-to-SQL, improving accuracy by 125%; embedded at $100B+ AUM client, drove 4+ validation cycles"
Skills Organization
- AI/ML: LangChain, LangGraph, DSPy, MCP, OpenAI/Anthropic/Google APIs, RAG, Vector DBs, Embeddings
- Full-Stack: Next.js, React, TypeScript, Tailwind, Node.js, Python, REST APIs
- Data & Infra: Postgres, Snowflake, Redis, Microsoft Graph, GCP, Azure, Docker
- Languages: German (native), English (fluent)
How Users Should Use This Skill
For best results, provide:
- Your current resume (PDF or text)
- LinkedIn screenshots (profile, experience, posts) — Claude cannot directly access LinkedIn URLs
- The job posting or target company/role
- Any recent achievements not on your resume
- Metrics: time spent, accuracy numbers, scale, client details
Example:
Help me update my resume for the AI Engineer role at [Company].
Here's my current resume: [attach PDF]
LinkedIn posts: [attach screenshots]
Some context:
- Built the SharePoint connector in 2 weeks
- Client has $100B+ AUM
- Achieved 90% accuracy after 4 validation cycles
1---2name: resume-creator3description: Create professional resumes using first-principles thinking, Google XYZ format, company research, LaTeX Harvard-style formatting, and iterative visual refinement. Use when the user wants to create, update, or optimize a resume/CV for a specific job, company, or career goal.4---5
6# Resume Creator
7
8A comprehensive resume creation skill that uses first-principles thinking, Google XYZ format, web research, and iterative visual refinement to craft tailored, professional resumes.
9
10## When to Use This Skill
11
12- User wants to create a new resume
13- User wants to update/optimize an existing resume
14- User mentions a job application, job posting, or target company
15- User asks about resume formatting or CV creation
16- User wants to tailor their resume for a specific role
17
18## Process Overview
19
20### Phase 1: Information Gathering
21
221. **Read existing materials** (if available):
23 - Existing resume (PDF, Word, or text)
24 - LinkedIn profile screenshots (Claude cannot directly access LinkedIn URLs)
25 - LinkedIn posts for achievements and speaking engagements
26 - Portfolio or personal website
27
282. **Understand the target**:
29 - Job description (if provided)
30 - Target company and role
31 - Industry/role type
32 - Career goals
33
343. **Research the target company** using web search:
35 - Company culture and values
36 - Tech stack and engineering practices
37 - Recent news, funding, products
38 - What they look for in candidates
39 - Company AUM/size/metrics for context
40 - Example searches:
41 - "{company} engineering blog hiring"
42 - "{company} careers culture values"
43 - "{role} at {company} interview what they look for"
44 - "{company} AUM assets under management" (for finance)
45
464. **Gather missing information** by asking the user:
47 - Recent experience not on resume
48 - Specific achievements with metrics
49 - Skills and technologies used
50 - Projects and speaking engagements
51 - Time spent on projects (for speed metrics)
52 - Client details (AUM, size, industry)
53
54### Phase 2: Google XYZ Format Analysis
55
56**The XYZ Formula**: "Accomplished [X] as measured by [Y] by doing [Z]"
57
58- **X** = Achievement/outcome (action verb: Built, Architected, Shipped, Led)
59- **Y** = Quantifiable metric (%, time, money, users, accuracy)
60- **Z** = How you did it (method, technology, approach)
61
62Before writing, analyze each bullet:
63
64| Bullet | X (What) | Y (Metric) | Z (How) | Score |
65|--------|----------|------------|---------|-------|
66| Example | Built connector | 2 weeks, 1000s docs | Delta API, Redis | 3/3 ✓ |
67
68**Target: 100% of bullets should score 3/3**
69
70Common metrics to extract from user:
71- Time to build ("in 2 weeks", "in 1 week")
72- Accuracy improvements ("125% improvement", "90% accuracy", "<3% error rate")
73- Scale ("1000s of docs", "400+ rounds", "90+ companies")
74- Cost savings ("reducing time from hours to minutes", "50% faster")
75- Client context ("$100B+ AUM client", "Fortune 500")
76- Audience size ("150+ builders", "100+ attendees")
77
78### Phase 3: First-Principles Analysis
79
80Before writing, analyze from first principles:
81
821. **Research what hiring managers look for**:
83 - Web search: "{role} resume what hiring managers look for 2024"
84 - Web search: "Google XYZ resume format"
85 - Understand the <8 second resume scan reality
86
872. **Alignment analysis**:
88 Create a table mapping:
89 | Job Requirement | User's Experience | Gap/Strength |
90
913. **Paul Graham / YC style considerations** (for startup roles):
92 - Lead with what you BUILT, not job titles
93 - Show speed of execution ("shipped in X weeks", "built in 2 weeks")
94 - Quantify everything (%, numbers, scale)
95 - Builder tone: "Built", "Shipped", "Architected", "Won" not "Responsible for"
96 - Remove corporate buzzwords
97
984. **Avoid redundancy**:
99 - Check if metrics in bullets duplicate header/subheader info
100 - Example: Don't say "Fortune 500 clients" in bullet if header says "Serving Fortune 500 clients"
101
102### Phase 4: LaTeX Resume Creation
103
104Use the Harvard-style LaTeX template with:
105- Clean header (name, location, contact, links)
106- No colored header bars - clean white background
107- Section order: Experience → Projects & Speaking → Skills → Education → Leadership
108- € symbol for currencies
109- 1 page maximum (critical)
110
111Key formatting:
112- Font: Helvetica Neue (or similar sans-serif)
113- Colors: Navy blue (#14-2D-4B / RGB 20,45,75) for sections
114- Margins: ~0.5 inches
115- Line spacing: 1.05
116- Use `\setstretch{1.05}` for readability
117
118**Punctuation guidelines**:
119- Use commas or semicolons to connect clauses, NOT em dashes (--)
120- Em dashes (--) only for date ranges in headers (e.g., "Sept 2025 -- Present")
121- Use semicolons to separate distinct achievements in one bullet
122
123**Link formatting**:
124- Add `[link]` in small navy text next to items with LinkedIn/external proof
125- Format: `{\color{sectioncolor}\footnotesize[\href{URL}{link}]}`
126
127### Phase 5: Iterative Visual Refinement
128
129**Critical**: After creating the LaTeX file, iterate visually:
130
1311. **Compile to PDF**:
132 ```bash
133 xelatex -interaction=nonstopmode resume.tex
134 ```
135
1362. **Check page count**: Must be exactly 1 page
137 - If 2 pages: reduce spacing, tighten text, combine bullets
138 - Adjust `\titlespacing*{\section}{0pt}{6pt}{2pt}` if needed
139 - Adjust `\setlist[itemize]{itemsep=1pt, parsep=0pt, topsep=1pt}`
140
1413. **Check for issues**:
142 - Does it fit on 1 page?
143 - Is spacing balanced?
144 - Are there overflow issues?
145 - Is typography clean?
146 - Any redundant information?
147
1484. **Iterate** until perfect
149
150### Phase 6: Final Delivery
151
1521. Save final PDF: `Resume_[Name]_[Role]_[Year].pdf`
1532. Keep .tex source file with same naming
1543. Clean up temp files (.aux, .log, .out)
1554. Open PDF for user
156
157## Content Guidelines
158
159### Experience Bullets - XYZ Examples
160
161**Strong XYZ bullets**:
162- Built SharePoint connector in 2 weeks enabling auto-indexing of 1000s of enterprise docs, reducing admin setup from hours to minutes
163- Architected Snowflake sub-agent for NL-to-SQL, improving query accuracy by 125%; embedded at $100B+ AUM client, drove 4+ validation cycles
164- Built agentic funding extraction with <3% error rate on 400+ rounds, validated against hand-labeled data and proprietary providers
165- Delivered DSPy live optimization talk to 150+ builders, featured in global newsletter (50K+ subscribers)
166
167**Weak bullets to avoid**:
168- Responsible for platform development (no metric, no how)
169- Worked on various projects (vague)
170- Built connector using Redis (no metric, no outcome)
171
172### Combining Related Bullets
173
174When two bullets are related, combine them:
175- Before: "Architected Snowflake agent" + "Embedded as Field Engineer at client"
176- After: "Architected Snowflake sub-agent for NL-to-SQL, improving accuracy by 125%; embedded at $100B+ AUM client, drove 4+ validation cycles"
177
178### Skills Organization
179
180- **AI/ML**: LangChain, LangGraph, DSPy, MCP, OpenAI/Anthropic/Google APIs, RAG, Vector DBs, Embeddings
181- **Full-Stack**: Next.js, React, TypeScript, Tailwind, Node.js, Python, REST APIs
182- **Data & Infra**: Postgres, Snowflake, Redis, Microsoft Graph, GCP, Azure, Docker
183- **Languages**: German (native), English (fluent)
184
185## How Users Should Use This Skill
186
187For best results, provide:
1881. Your current resume (PDF or text)
1892. LinkedIn screenshots (profile, experience, posts) — Claude cannot directly access LinkedIn URLs
1903. The job posting or target company/role
1914. Any recent achievements not on your resume
1925. **Metrics**: time spent, accuracy numbers, scale, client details
193
194Example:
195```
196Help me update my resume for the AI Engineer role at [Company].
197Here's my current resume: [attach PDF]
198LinkedIn posts: [attach screenshots]
199
200Some context:
201- Built the SharePoint connector in 2 weeks
202- Client has $100B+ AUM
203- Achieved 90% accuracy after 4 validation cycles
204```