# Car Resume

> Write or tailor a resume to a specific target role with metric-driven impact bullets that pass ATS and recruiter skim.

- Skill: `matrixx0070/car-resume` (Agent Skill)
- Install (CLI): `npx skillmds add matrixx0070/car-resume`
- Raw SKILL.md: https://api.skillmd.com/api/skills/matrixx0070/car-resume/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Matrixx0070 (https://skillmd.com/u/matrixx0070)
- Updated: 2026-08-19
- Page: https://skillmd.com/skills/matrixx0070/car-resume

---


## When to use

Reach for this when you are the candidate building a resume from scratch, tailoring an existing one to a specific posting, or rewriting weak duty-based bullets into quantified impact. Use before applying and before car-cover-letter so both draw from the same evidence.

**Not for:** the employer side. Screening or scoring candidate resumes is hr-recruiting-pipeline; deriving what the role needs is hr-interview-prep; benchmarking pay is hr-comp-analysis. This skill argues *your* case, not the hiring team's.

## Method

1. **Extract the target** — paste the job posting; pull the top 8-12 required skills, tools, and outcomes in their exact wording. These become your keyword and priority list.
2. **Inventory your evidence** — for each past role, list what you owned, changed, and the result. Decision point: if you have no metric, estimate a defensible range (%, $, time, volume, count) and mark it to verify — never fabricate.
3. **Match and rank** — map your evidence to the target list. Decision point: if a required skill has zero matching evidence, either surface a transferable proxy or drop the claim; do not keyword-stuff skills you cannot defend in an interview.
4. **Write impact bullets** — use `Action verb + what + quantified result + how`. Lead with the number when it is strong. 3-5 bullets per recent role, fewer for older ones.
5. **Order for the reader** — summary tuned to the role, then most-relevant experience first. Keep to one page under 10 years' experience, two beyond.
6. **ATS pass** — single column, standard section headers, no tables/images/text-boxes, real dates. Mirror the posting's exact skill terms.

## Example

Posting wants "reduced infrastructure cost" and "Terraform." Weak: "Responsible for AWS infrastructure." Strong: "Cut AWS spend 34% ($210K/yr) by migrating 40 services to spot instances and codifying provisioning in Terraform, eliminating manual drift." The number leads, the tool is named verbatim, the how is defensible in an interview.

## Pitfalls

- Duty bullets ("Responsible for…") instead of outcomes — recruiters skim for numbers, not job descriptions.
- One generic resume for every posting — tailoring to the target list beats volume every time.
- Invented metrics you cannot defend under questioning; use verifiable estimates and flag them.
- ATS-hostile formatting (columns, tables, graphics) that parses into garbage before a human ever sees it.

## Output format

```
Target keywords: [8-12 exact terms from posting]
Summary: 2-3 lines, role-tuned, states level + specialty + headline metric
Experience (per role):
  Title | Company | Dates
  - [Action verb] + [what] + [quantified result] + [how]  x3-5
Skills: [ATS terms matching posting, grouped]
Education / Certs
Gap notes: [required skills with no evidence + chosen proxy or drop]
```