Files
jobboard/claude-skills/application-drafter/references/cv-rules.md
T
WolfandClaude Opus 5.5 5d60bd5b30 Add two claude.ai chat skills, application-drafter and application-auditor, with a stdlib checker for dashes, banned phrases, bullets and counts, adapted from ai-job-search (MIT)
The career master and the pitfalls document are facts the user pastes or attaches per chat; every rule lives in the skills. build.sh zips each skill into claude-skills/dist/.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-03 23:29:15 +02:00

5.4 KiB

CV rules

Sources

The career master is the only source of facts. The pitfalls document overrides any phrasing that contradicts it. An earlier tailored CV may be reused for structure and phrasing, never as a source of claims.

Layout: less is more

Two pages, A4, single column.

  • Page one: name and contact line, a profile statement of 3-4 lines, then recent experience. Experience takes at most one page.
  • Page two: earlier experience, education, skills, talks and publications, languages, references.

If in doubt, cut rather than squeeze. Never shrink margins, fonts or spacing to force a fit.

Profile statement

3-4 lines on why the candidate fits this role, focused on what the employer gains. When the role sits outside the candidate's home domain, open with the domain-transfer argument: the one sentence that connects their background to the employer's problem.

Experience

  • Reverse chronological.
  • At most 5 bullets per role, fewer for older roles (for example 5, 3, 2, then 1 or a single summary line).
  • Each bullet at most 2 lines, ideally 1. A bullet that wraps to a third line is split or cut.
  • Lead with the aspect most relevant to the posting. Measurable results where the career master has them; never invent or round up a number.
  • Role titles, employers and dates are exactly as in the career master and the pitfalls document.

Tenure against visible output. A two-year role shown as one project reads as low output. Honest fixes, in order: surface other real work from the career master; make phases explicit (onboarding, then ownership of the named work through delivery); name what made the cycle long (live data collection, validation with domain experts, deployment iterations). Never invent projects and never shorten dates. If the gap survives, prepare the interview answer: what filled the time, and the outcome.

Employment gaps: state them matter-of-factly; name what the candidate did in the period if the career master records it.

Posting terms

  • Use the posting's own term over a synonym wherever it truthfully applies, in experience bullets and in section headings. A posting hiring for "MLOps" should find a heading or label containing "MLOps", not only "ML deployment".
  • The skills section uses 5-7 competency labels, each named in the posting's terms where truthful, each with a short line of evidence.
  • Engage nice-to-haves by name where the career master supports honest adjacency ("conceptually aligned with ").

Education, credentials, talks

  • Highest degrees always; for senior roles titles and years only; a thesis topic only when it serves the posting.
  • In-progress qualifications say so inside the entry: "In progress, expected June 2027". A closed range like 2025-2026 reads as finished. The profile statement, the entry and any availability note give the same date.
  • Publications and talks: 1-3 that match the posting, not all.
  • Evidence links: where the CV names a public artefact (a project, a talk, a publication), carry its link.
  • References: "Available upon request." on one line.

Relevance-weighted cutting

Cut by signal, not by section. Score every candidate line on three things:

  1. Relevance to this posting: does it hit a named tool, keyword or stated responsibility?
  2. Uniqueness: is it the only place the claim appears?
  3. Narrative load: does the cover letter lean on it? If cutting it forces a letter rewrite, it is load-bearing.

Cut the lowest total first, wherever it sits. An older-role bullet that names the posting's core skill outranks a recent-role bullet that does not.

Usual order: redundancy (the same achievement in skills and in a bullet: cut the skills copy); profile-statement sentences that restate a later section; low-relevance bullets anywhere; low-relevance supporting items (a certificate off the posting's stack, a talk on another topic); structural cuts (oldest education entry, an older role down to one line) last. Never cut the one example the letter depends on.

If the CV ends early on page two, restore the highest-relevance line that was cut.

ATS parseability

An applicant tracking system reads the text layer, not the page.

  • Email and phone as plain text in the body. Not only as an icon, a hyperlink label or a Word header or footer.
  • Date ranges as ASCII: 2016-2024, Mar 2016-Jul 2016, 2021-present. Never an en dash (U+2013) or any other Unicode dash in a date range; a Workday import has been seen to drop such dates. Every role has a start and an end; a bare single year imports as a start with no end. Do not invent a start date that is not in the career master.
  • No icon glyphs (phone, envelope, pin symbols, emoji) for contact details or headings.
  • Single column. No sidebars, text boxes or layout tables: multi-column layouts extract in the wrong reading order and interleave sections.
  • Standard section headings (Experience, Education, Skills) in the CV's language.

Checklist

  • Every claim grounded in the career master; no pitfalls entry violated
  • Profile statement tailored to this role
  • Every stated requirement covered or honestly gapped (coverage table)
  • Posting terms in headings and competency labels where truthful
  • Experience takes at most one page; at most 5 bullets per role; bullets at most 2 lines
  • Dates ASCII ranges with start and end; email and phone as text; no icons; single column
  • Headings in the CV's language; British spelling; no em dashes
  • No contradiction with the cover letter