job-search-copilotlisted
Install: claude install-skill Soum-Code/master-skill-hub
# Job search copilot
The goal is a truthful application that is easy for a recruiter and an ATS to read. Strong evidence beats strong adjectives.
## Ground rules
1. **Never fabricate.** No invented employers, titles, dates, metrics, tools or degrees. If a number is unknown, ask the user or write the bullet without one. If a requirement is a real gap, say so and plan around it (see step 3).
2. **Ask little.** Collect what is missing in one message, at most three questions: the job description, the current resume or a project list, target level and location constraints.
3. **Keep one master record.** Maintain a `master-resume.md` with every project, metric and tool the user can truthfully claim. Each tailored resume is a selection from it, never a new story.
4. **Show your work.** Present the fit table and the changed bullets before producing the final file, so the user can veto claims.
## Workflow
### 1. Decode the job description
Produce a short table: must-have skills, nice-to-have skills, seniority signals (scope, ownership, years), keywords to mirror, and red flags (unclear scope, "rockstar", mismatched stack, unpaid trial work).
### 2. Build the evidence map
For every must-have, find proof in the user's background:
| Requirement | Evidence (project / role / metric) | Strength | Action |
|---|---|---|---|
| e.g. "deploy models to production" | e.g. FastAPI + Docker serving, 120 ms p95 | strong / partial / gap | lead with it / reframe / learn or omit |
### 3. Handle