# Cv Intake

> Parse a CV or resume that has been dropped into a person's cv/ folder and turn it into their profile.md, evidence.md and signature.md. Use when a new CV arrives, when a CV is updated, or when a person's profile still contains TBD placeholders. Run this before any email is drafted for that person.

- Skill: `faaz17/cv-intake` (Agent Skill)
- Install (CLI): `npx skillmds@latest add faaz17/cv-intake`
- Raw SKILL.md: https://api.skillmd.com/api/skills/faaz17/cv-intake/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: Faaz17 (https://skillmd.com/u/faaz17)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/faaz17/cv-intake

---


# /cv-intake, turn a CV into a usable profile

Usage: `/cv-intake "<Second Person>"` or `/cv-intake "<Person Name>"`

Everything downstream depends on this. A profile with `TBD` in it blocks drafting entirely, by design.

## Steps

1. **Find the CV.** Look in `<person>/cv/`. PDF, DOCX, or an image. If the folder is empty, say so and stop — do not proceed on remembered or inferred information.

2. **Read the whole thing.** Every section, including the ones that look like boilerplate. Skills lists and coursework often carry the detail that makes an email specific.

3. **Extract into structured fields:**
   - Full name, exactly as they write it
   - Degree title, university, year of study, expected graduation
   - GPA or CGPA and its scale, but only if they put it on the CV
   - Contact: email, phone, LinkedIn, GitHub, portfolio
   - Location and work authorisation, if stated
   - Every project: what it does, the stack, their role, the outcome, any link
   - Every internship or job: employer, title, dates, what they actually did
   - Awards, competitions, publications, certifications
   - Leadership, societies, volunteering
   - Skills, grouped by domain rather than in one flat list

4. **Separate hard facts from soft claims.** A CV bullet saying "improved efficiency by 40%" is a soft claim unless the person can substantiate it — mark it `(unverified from CV)`. A published paper with a venue is hard. Hard facts can go in emails; soft claims need confirmation first.

5. **Write `<person>/profile.md`** using the structure in the existing `<Person Name>/profile.md`. Mark anything the CV does not answer as `TBD` rather than filling it in.

6. **Write `<person>/evidence.md`** — the story bank. For each significant project or role, write the two-sentence version that would go in an email, the proof link, and the role types it is relevant to. This is what `profile_matcher` reads, and it is where most of the value of this skill ends up.

7. **Write `<person>/signature.md`** — the exact signature block, from the CV's contact details, in the format in `rules/email_format.md`.

8. **Update `rules/voice_rules.md`** with a section for this person: their one-sentence position, what to lead with, how to phrase their strongest project, and their honest caveats.

9. **List the open questions.** Anything a good email would want that the CV does not say: availability dates, preferred role types, target companies, whether they have a portfolio, whether soft claims can be backed up. Ask these rather than guessing.

10. **Cross-check against any second source of truth** the sender keeps — a notes vault, a portfolio site, an existing project log. Where it disagrees with the CV, remember the CV is what a company will actually see, so flag the difference rather than silently picking one.

## Output format

```
## CV intake: <person>

**Source:** <filename>, <n> pages

**Written**
- profile.md — <n> projects, <n> roles, <n> awards
- evidence.md — <n> story-bank entries
- signature.md
- voice_rules.md — section added

**Strongest assets**
1. <thing> — <why it will land>

**Soft claims needing confirmation**
- <claim> — <what would substantiate it>

**Still TBD**
- <field>

**Questions for <person>**
1. <question>

**Ready to draft?** yes | no — <what is missing>
```

## Rules

- Never invent a fact the CV does not contain. `TBD` is the correct output for a gap.
- Never copy anything from the other person's profile. Two candidates, two folders, no bleed.
- Never soften or inflate a CV claim when moving it into the profile. Move it verbatim and mark its confidence.
- If the CV contradicts something already in the profile, surface the contradiction and ask. Do not silently overwrite.
- The CV file stays in `cv/`. It is not moved, renamed, or edited.