claude-resume-kit: Skill for Claude Code

/setup-build-kb

User input: $ARGUMENTS

Parse $ARGUMENTS:

• Empty → full build (all phases)
• Phase number (e.g., 3) → resume from that phase
• "experience" / "bundles" / "skills" / "pubs" / "reframing" / "significance" → run only that component
• "status" → show what's built and what's missing

---

Startup

1. Read CLAUDE.md — check KB Corrections Log
2. Read config.md — load:
   • Personal Info (positions, institutions, dates)
   • Role Types table (defines which bundles to create)
   • Provenance Flags (propagate to all KB files)
   • Document Preferences (bullet variant defaults)
3. Read knowledge_base/extractions/_INVENTORY.md — verify extractions exist
4. Scan resume_builder/ to see what's already built

Pre-flight check:

• If _INVENTORY.md is empty or has no entries: "No extractions found. Run /setup-extract first." Stop.
• If fewer than 2 extractions: warn "Only [N] extraction(s) found. KB quality improves with more papers. Continue anyway?"

Progress: "Found [N] extractions across [M] positions. Config has [K] role types defined."

---

Phase 1: Build Experience Files

Goal: Create one experience file per position, containing all achievements organized for resume generation.

Read: All extraction files listed in _INVENTORY.md

For each position (from config.md or inferred from extraction metadata):

1. Group extractions by the position they belong to (based on dates, institution, or user clarification)
2. Ask the user to confirm grouping if ambiguous: "I've grouped these papers under [Position]. Correct?"

Experience file format (resume_builder/experience/experience_<position_key>.md):

# Experience: [Position Title] — [Institution]
## [Date Range]

### Cross-Position Section
[Brief narrative connecting this position's work to the user's broader trajectory]
[CL framing content — how this position fits the career arc]

---

### Achievement [ID]: [Short Title]
**Source:** [extraction filename]
**Paper:** [citation or "internal"/"unpublished"]
**User's role:** [first author / contributing / sole developer]
**Status:** [published / under review / draft / internal]

**Context:** [1-2 sentences — what problem, why it matters]

**Bullet variants:**
- **2L:** [Full 2-line bullet text — STAR format, ~180-210 rendered characters]
- **3L:** [Full 3-line bullet text — for CV use, ~270-310 rendered characters]
- **1L:** [Condensed 1-line version — ~90-110 rendered characters, for tight budgets]

**Key skills:** [comma-separated list of skills this achievement demonstrates]
**ATS keywords:** [domain-specific terms an ATS might scan for]
**Reframing notes:** [how to emphasize different aspects for different role types]

---
[Repeat for each achievement]