regional-cv-formats
Skill0 starsChanged 20 days agoMITView on GitHub
Convert or check a CV against country conventions. Covers UK and Ireland, US, Canada, Australia and NZ, Europe, Germany/Austria/Switzerland, UAE and the Gulf, and India, including paper size, spelling, photo, visa status, personal details, declaration and signature. Use when the user is applying in another country or asks for a UAE, Gulf, German, Indian, US or Europass-style CV.
In this repository7 other files it gives its agents.
- ats-scoreSkill
- cover-letter-writerSkill
- cv-tailorSkill
- finance-transformation-cvSkill
- interview-prep-coachSkill
- job-match-analyzerSkill
- resume-genieSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Check the CV against that region's rules:
- Distinctive: line 20
Ask the user for any personal details the region expects that they haven't given: visa status, nationality, photo, languages with levels, …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Regional CV formats
The same CV can be right in Dublin and wrong in Dubai. Follow references/regions.md.
Workflow
- Identify the target region from the job location or the user's request.
- Check the CV against that region's rules:
- paper size and spelling
- photo: expected, optional or not used
- which personal details belong (and which must be removed, for example date of birth in the US or UK)
- visa or right-to-work line
- languages with levels
- declaration or signature
- Ask the user for any personal details the region expects that they haven't given: visa status, nationality, photo, languages with levels, notice period. Never invent them.
- Rebuild the CV as Word in the right format. If there's no structured
output.jsonyet, convert the CV into one first (seereferences/output-schema.json), changing no facts. Examples:# UAE: photo and visa status expected python scripts/build_docx.py output.json --page a4 --photo photo.jpg --header "Visa status: Employment visa (transferable)" --detail "Nationality=Indian" --detail "Notice period=30 days" --languages "English (C2), Arabic (A2)" # Germany: CEFR languages, place, date and signature python scripts/build_docx.py output.json --page a4 --languages "German (B2), English (C1)" --signature --place Berlin # India: personal details and declaration python scripts/build_docx.py output.json --page a4 --detail "Date of birth=..." --declaration --place Bengaluru # US: Letter paper, no photo or personal details python scripts/build_docx.py output.json --page letter - Reply with:
- what changed for this region and why
- anything removed for legal or convention reasons
- the file
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.

