cv-intake
Skill1 starsChanged 2 months agoMITView on GitHub
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.
In this repository37 other files it gives its agents.
- wsb-data-pipelineSkill
- docx-exportSkill
- harvard-mdxSkill
- humanise-docx-reportSkill
- make-pdfSkill
- bom-builderSkill
- ring-testSkill
- batch-draftSkill
- cold-emailSkill
- cv-upgradeSkill
- find-contactSkill
- followupSkill
- humanize-emailSkill
- log-outreachSkill
- outreach-statusSkill
- target-researchSkill
- erc-statusSkill
- log-sessionSkill
- score-auditSkill
- submission-checkSkill
- sumo-statusSkill
- trial-runSkill
- vr-statusSkill
- academic-registerSkill
- aviation-data-sourcesSkill
- business-frameworksSkill
- consultancy-registerSkill
- excel-deliverablesSkill
- forecasting-methodsSkill
- operations-frameworksSkill
- secondary-data-sourcesSkill
- archive-indexSkill
- event-proposalSkill
- meeting-minutesSkill
- read-boxnoteSkill
- captureSkill
- new-scriptSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Find the CV: Look in <person>/cv/. PDF, DOCX, or an image.
- Distinctive: line 16
Read the whole thing: Every section, including the ones that look like boilerplate.
- Distinctive: line 24
Every project: what it does, the stack, their role, the outcome, any link
- Distinctive: line 25
Every internship or job: employer, title, dates, what they actually did
- Very specific: line 74
Never invent a fact the CV does not contain.
- Distinctive: line 75
Never copy anything from the other person's profile.
- Distinctive: line 76
Never soften or inflate a CV claim when moving it into the profile.
- Distinctive: line 77
If the CV contradicts something already in the profile, surface the contradiction and ask.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/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
- 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. - 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.
- 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
- 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. - Write
<person>/profile.mdusing the structure in the existing<Person Name>/profile.md. Mark anything the CV does not answer asTBDrather than filling it in. - 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 whatprofile_matcherreads, and it is where most of the value of this skill ends up. - Write
<person>/signature.md— the exact signature block, from the CV's contact details, in the format inrules/email_format.md. - Update
rules/voice_rules.mdwith a section for this person: their one-sentence position, what to lead with, how to phrase their strongest project, and their honest caveats. - 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.
- 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.
TBDis 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

