resume-tailor
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.
What this skill does
# Resume Tailor
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.
## Critical Rules
1. **NEVER fabricate experiences, skills, or achievements.** Only use content from the master resume, `candidate-context.md`, and discoveries persisted during analysis.
2. **Preserve the `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.
3. **Maintain ATS compatibility.** No graphics, tables outside the cls structure, or custom fonts.
4. **Keep to one page.** Highlight only your strongest 2-3 bullets per role. Fewer strong bullets beat many mediocre ones.
5. **Never generate generic content -- ask instead.** If a bullet would be vague, ask for real specifics.
## Workflow
### Step 1: Read Inputs
```
Required:
- notes.md from the output directory (keyword analysis, gap analysis, recommendations)
- Master resume: hojicha/resume.tex
- Candidate context: hojicha/candidate-context.md
```
### Step 2: Professional Summary (Optional)
Generate a role-specific summary if space permits. Omit if the resume already speaks for itself.
- Headline: <10 words, descriptive noun phrase (NOT "Professional Summary")
- Summary: <50 words starting with a job role noun, top 3-5 selling points matching JD
- Don't claim to "specialize" in too many things
- Don't state your objective unless you're a career changer
### Step 3: Section Ordering
| 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.
### Step 4: XYZ Bullet Optimization
Rewrite experience bullets using the XYZ formula:
```
Accomplished [X] as measured by [Y], by doing [Z]
```
- Lead with the accomplishment, not the task
- Quantify whenever possible (numbers, percentages, scale, scope)
- Weave target keywords into the Z component naturally
- One bullet = one accomplishment
- Strong action verbs: Architected, Engineered, Developed, Built, Led, Delivered, Automated, Optimized, Reduced
Keyword placement priority:
1. Professional summary / first bullet of most relevant role
2. Most recent experience section
3. Projects section
4. Skills section (highest ATS hit rate -- ensure keywords appear here AND in contextual bullets)
### Step 5: Strategic Uncommenting & Commenting
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.
### Step 6: Skills Reordering
Reorder skills categories and items to front-load the most relevant ones. First items in each line are what ATS and recruiters see first.
### Step 7: Output
Create `hojicha/<company>-<role>-resume/resume.tex`:
- Copy master resume structure exactly, applying all modifications
- Include `\documentclass[letterpaper,12pt]{fed-res}`
- Copy `hojicha/fed-res.cls` into output directory
**Verify:** 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.
## fed-res.cls Commands
| 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:**
```latex
\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:**
```latex
\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`.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.