egg/skills/resume-tailor/SKILL.md
This skill should be used when the user has already run resume-analyzer and wants to generate the tailored resume.tex. Trigger phrases include "generate resume", "write the resume", "create resume.tex", "tailor the resume now", "build the resume from notes", or when the user asks to proceed after a resume analysis session. It reads the notes.md produced by resume-analyzer and generates a tailored LaTeX resume.
npx skillsauth add luqmannurhakimbazman/ashford resume-tailorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Generate a tailored resume.tex from analysis notes. Reads hojicha/<company>-<role>-resume/notes.md (produced by resume-analyzer) and the master resume (hojicha/resume.tex).
Prerequisite: notes.md must exist in the output directory. If missing, tell the user to run resume-analyzer first.
candidate-context.md, and discoveries persisted during analysis.fed-res.cls document class. Do not modify \documentclass[letterpaper,12pt]{fed-res} or add packages. Copy hojicha/fed-res.cls into the output directory.Required:
- notes.md from the output directory (keyword analysis, gap analysis, recommendations)
- Master resume: hojicha/resume.tex
- Candidate context: hojicha/candidate-context.md
Generate a role-specific summary if space permits. Omit if the resume already speaks for itself.
| Experience Level | Order | |------------------|-------| | <3 years / recent grad | Summary, Education, Experience, Projects, Skills | | 3+ years | Summary, Experience, Education, Projects, Skills |
Use the recommendation from notes.md if present.
Rewrite experience bullets using the XYZ formula:
Accomplished [X] as measured by [Y], by doing [Z]
Keyword placement priority:
Review commented-out sections in the master resume. Uncomment entries that strengthen the application per notes.md recommendations. Comment out entries that weaken the narrative. Link project names to GitHub repos where possible.
Reorder skills categories and items to front-load the most relevant ones. First items in each line are what ATS and recruiters see first.
Create hojicha/<company>-<role>-resume/resume.tex:
\documentclass[letterpaper,12pt]{fed-res}hojicha/fed-res.cls into output directoryVerify: All meaningful content is text (not layout-dependent), special characters render when LaTeX is stripped, acronyms expanded at least once.
Append a "Changes Made" section to notes.md listing all modifications.
| Command | Usage |
|---------|-------|
| \resumeSubheading{Org}{Loc}{Title}{Date} | Experience/education entry |
| \resumeSubheadingShort{Title}{Date} | Entry without location |
| \resumeSubSubheading{Title}{Date} | Sub-position at same org |
| \resumeProjectHeading{Title \| Tech}{Date} | Project entry |
| \resumeItem{text} | Bulleted item |
| \resumeSubItem{text} | Compact bullet variant |
| \resumeSubHeadingListStart/End | Wrap subheading groups |
| \resumeItemListStart/End | Wrap bullet lists |
Skills section pattern:
\section{Skills and Interests}
\begin{itemize}[leftmargin=0.15in, label={}]
{\item{
\textbf{Category}{: item1, item2, item3} \\
\textbf{Category}{: item1, item2, item3}
}}
\end{itemize}
Header pattern:
\begin{center}
\textbf{\Huge \scshape Name} \\ \vspace{1pt}
\underline{email} \ $|$ \ \underline{linkedin} \ $|$ \
\underline{github} \\ \vspace{1pt}
\end{center}
Commenting: Prefix every line with % to hide a section. Remove % to restore.
Do NOT add packages to resume.tex -- all formatting is handled by fed-res.cls.
development
This skill should be used when the user wants a technical interview preparation roadmap, coding interview study plan, or DSA practice plan tailored to a specific company and role. Trigger phrases include "technical interview roadmap", "coding interview prep for", "DSA roadmap for", "DSA study plan", "leetcode prep for", "what problems should I practice for", "interview study plan", "prep me for the technical rounds", "technical prep for", "what should I study for", "coding prep plan", "roadmap from this JD", "prep me for this role [URL]", or providing a JD URL with a request for technical interview preparation.
development
This skill should be used when the user asks to "write a blog post", "draft a blog post", "create a technical blog", "write a deep dive", "write an explainer", "blog about", "write a tutorial post", "turn this into a blog post", or wants to create technical content for a personal blog or static site. Default platform is Jekyll (Gundersen-style) with KaTeX math, BibTeX citations via jekyll-scholar, and custom figure HTML. Covers deep dives, explainers, tutorials, and project showcases on ML, statistics, computer science, finance, math, and quantitative topics. Generates Markdown with SEO frontmatter, code examples, and diagram suggestions.
development
This skill should be used when the user wants to analyze a job description against their resume, extract keywords, identify gaps, or prepare tailoring notes. Trigger phrases include "analyze JD", "analyze this job description", "extract keywords from JD", "gap analysis for", "what does this role need", "compare my resume to this JD", "tailor resume", "optimize resume for JD", "build resume for", "target job description", "customize resume for", "resume for this role", "refactor resume", "update resume for", "match resume to JD", or when a user pastes a job description alongside their resume. It produces a notes.md analysis file that resume-tailor uses to generate the final resume.
development
This skill should be used when the user wants to set up an autonomous coding loop, plan a Ralph loop, prepare for headless Claude execution, create a spec and implementation plan for autonomous coding, or run an autonomous development workflow. Trigger phrases include "ralph", "autonomous loop", "coding loop", "ralph prep", "set up ralph", "headless loop", "autonomous coding", "ralph plan".