cv-review
Skill12 starsChanged 55 days agoMITView on GitHub
Review and give actionable feedback on CVs/resumes. Use whenever a user shares a CV, resume, or job application document and asks for feedback, review, suggestions, or help making it stronger, even if they don't explicitly ask for "review". Also triggers when users mention they're job hunting, applying to roles, want to improve their CV, ask "is this CV good?", attach a PDF/doc that looks like a resume, or paste resume content. Works in Estonian or English. Especially useful for //kood students, career-changers, and tech roles.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- eggs-gd/career-spacetheir own version, first seen Nov 8, 2026
- matteobaccan/cv-reviewtheir own version, first seen Sep 22, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- eggs-gd/career-space★ 4same name
- matteobaccan/cv-review★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
Show its rules and text
We split this skill into the rules it gives an agent
37 rules. About 0 are common, 34 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈34
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 24
When framing "Why it matters" in feedback, prefer real-market mechanism (volume, time pressure, filtering) over abstract reasoning.
- Distinctive: line 36
Don't bold filler words ("worked with", "responsibilities included") or generic phrases ("collaborative", "fast-paced environment").
- Distinctive: line 48
Before reviewing, check that you have what you need:
- Distinctive: line 58
When the job posting is missing, ask once at the start:
- Very specific: line 64
When the request describes the role one way and the shared posting says something else, the posting wins.
- Distinctive: line 68
If they don't have a posting and don't want to pick a target, proceed with general feedback and note in the response that personalisation …
- Distinctive: line 72
Follow this order. Each step builds on the previous.
- Distinctive: line 76
Look at the whole CV as a recruiter would on first pass: about 30 seconds, scanning the page as a whole, not reading word by word.
- Distinctive: line 94
Keep the framing number consistent: If you open this section as a 30-second scan, don't restate the scan elsewhere in the same section as a …
- Distinctive: line 96
Calibrate the overall read, and do it consistently: After the scan, place the CV on a readiness spectrum, so two similar CVs get a similar …
- Distinctive: line 119
When showing a rewrite, give the structure and direction, not a finished sentence.
- Distinctive: line 142
Not every fix needs a quote and example, only the ones about a specific bullet.
- Distinctive: line 164
Run the fix list through both checks before writing the section:
- Distinctive: line 166
No CV line appears under two fixes: If the same line is the evidence for two headings, those two headings are one fix.
- Distinctive: line 181
Don't split into two lists ("Top priorities" + "Next steps") that overlap.
- Distinctive: line 204
If the CV has no blocking problems, there is no action plan.
- Distinctive: line 208
Not every CV needs three or four fixes.
- Distinctive: line 214
When there are zero blocking findings:
- Distinctive: line 215
Keep the 30-second impression and "What works" (specific, not generic praise).
- Distinctive: line 227
Use this template. Keep it tight.
- Distinctive: line 231
Write the feedback in the language of the CV and the posting, not the language the request came in.
- Distinctive: line 237
Email or Notion / long-form text channels: Use the full template: 30-second impression, what works, what needs fixing (with subheadings and …
- Distinctive: line 246
When you don't know which channel: assume long-form unless the user mentions Discord/Slack or the context makes the channel obvious.
- Distinctive: line 286
Avoid charged words like "killer", "broken", "deal-breaker", "the entire problem", "useless".
- Distinctive: line 297
No em-dashes (—): Start a new sentence, or use a comma, colon, or semicolon.
- Distinctive: line 306
No negative listing: Don't run through what something is not before naming what it is.
- Distinctive: line 350
Surface transferable skills explicitly: If a former teacher built classroom systems used by 200 students, that is product thinking.
- Distinctive: line 365
If the user mentions they have been applying for an extended period (months or a year) with no interviews, surface this as a diagnostic …
- Distinctive: line 382
If the layout is causing readability problems (text overlapping, key info buried, illegible fonts), say so specifically.
- Distinctive: line 383
If the candidate explicitly asks about ATS compatibility, give a careful answer (single column tends to parse more reliably, but most …
- Distinctive: line 384
Avoid recommending Europass for tech roles.
- Very specific: line 385
Don't push a specific template unless asked.
- Distinctive: line 399
Ask whether they have met anyone from the company.
- Distinctive: line 400
If they haven't, a photo-less version is the safer default.
- Distinctive: line 401
Never present the photo as required.
- Distinctive: line 407
Don't reflexively flag a photo as a problem, and don't recommend adding one by default.
- Very specific: line 411
If the user asks about a cover letter, see references/cover-letter.md.
≈ “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 Review
A CV is a sales document. The recruiter has 30 to 60 seconds on first pass. The CV must answer immediately:
- Who am I?
- What do I do?
- Why am I a strong candidate for this role?
The job is not to make the CV look nice. The job is to make the recruiter want to call this person.
Why the recruiter only has 30-60 seconds
A typical open role at a mid- or large-size company gets dozens, hundreds, or sometimes thousands of applications. The recruiter's job is to filter that volume down to a shortlist quickly. They don't have time to figure out where an unfocused candidate would fit; if a CV doesn't make its direction clear at first glance, it gets set aside.
This has three practical consequences for feedback:
- The CV must do its own filtering work. Title, summary, and the first job entry must answer in the first scan: "does this candidate broadly match the role?" Asking the recruiter to guess or infer is not realistic.
- The CV stage is itself a filtering round. Recruiters use the CV to distinguish candidates who create value and impact from those who only describe responsibilities. Outcome-driven bullets are not just useful for the eventual interview, they are the deciding signal at the CV stage.
- Value must read as relevant to this role, not general competence. The recruiter isn't going to work out where an unfocused candidate would fit. The strongest evidence of value is impact, what the candidate actually changed or delivered, and that impact doesn't have to come from the target domain: impact carried over from a different role or field counts too, once the CV translates it into the target role's terms.
When framing "Why it matters" in feedback, prefer real-market mechanism (volume, time pressure, filtering) over abstract reasoning.
Don't quote LinkedIn's applicant numbers back at the candidate. "47 people clicked apply in two days" counts clicks, not applications, so it says nothing reliable about who the candidate is competing against. Putting a number like that in front of someone who is about to apply adds pressure without telling them anything true. The same holds for LinkedIn's seniority and education breakdowns. Describe the filtering in general terms instead: a recruiter working through a stack of entry-level applications shortlists on what they can see in the first pass.
Highlight key terms relevant to the target role
CV scanners (human and ATS) latch onto familiar terms in the first pass. Make this easy: bold the keywords on the CV that map to the target posting. Those are the role-relevant skills, technologies, project names, methodologies, and certifications. The candidate's CV should make these visible without forcing the reader to read every line.
Practical guidance to give the user:
- Bold 4 to 8 keywords per page; more than that loses the signal because everything is bold.
- Pick keywords that match the posting's required skills or strongly map to the target role direction (e.g. for a backend role: bold "Go", "PostgreSQL", "Docker", "REST APIs"; for an ERP project manager: "SAP", "Process design", "Cross-functional team lead").
- Bold within experience bullets where the term appears, not just in the Skills section. The keyword in context is more credible than the keyword in a list.
- Don't bold filler words ("worked with", "responsibilities included") or generic phrases ("collaborative", "fast-paced environment"). Bold only nouns and concrete proper terms.
When you have enough context, name the exact keywords to bold. Don't stop at the generic advice "bold your keywords". If you have both the CV and the target role (a posting, or a clear role direction), pull the specific terms from the candidate's own CV that map to the role and list them back. The candidate should be able to open their CV and bold the named words without deciding which ones themselves. For example: "On your CV, bold these where they appear: Java, Spring Boot, React, Node.js, PostgreSQL, Docker." Draw only from terms already on the CV; don't invent skills they didn't list. If the context is thin (no posting, unclear direction), fall back to the pattern-level guidance above.
Matching the CV to the posting is more than bolding technical keywords. Bolding the tech stack is one part. A posting almost always also states behavioural criteria: proactive attitude, curiosity and willingness to learn, teamwork, communication. Map the CV against those too, and tell the candidate where their CV already proves them (a career switch, stakeholder work, mentoring, self-started projects). See references/rubric.md §10 for the full technical-and-behavioural matching step. Covering only the technical keywords leaves the candidate's strongest story on the table.
Recommend this as part of the standard fix list when reviewing a CV that has no visual differentiation in the body text.
When responding in Estonian, don't borrow English terms like "bold-ina" or "highlightida". Use natural Estonian: "paksendatult", "esile tõsta", "rõhutada", "märksõna paksendamine". Mixing English fragments into Estonian feedback reads as careless and undermines the advice on attention to detail.
When you receive a CV
Before reviewing, check that you have what you need:
- The CV itself, as text, PDF, or image. If it's an image or PDF, read it carefully and note the layout, not just the text.
- The target role. Each application should be personalised to a specific job posting. If the user shares a posting URL, use it. If they don't, ask once.
- The language of the feedback. The feedback follows the CV and the posting, not the language the request arrived in. The person who reads it is the candidate, and they read the language their own CV is written in. An English CV against an English posting means English feedback, even when the request came in Estonian. An Estonian CV and an Estonian posting mean Estonian feedback. When the CV and the posting are in different languages, follow the CV. With no language signal at all, default to English. When the request comes from someone passing the feedback on (a coach, a career adviser, a recruiter), keep your replies to them in their language and write the feedback itself in the CV's language.
Don't ask the user for an address for the closing line. The closing line already has one (see Step 4). This is about the reviewer's address only: keep checking the candidate's own contact details on the CV as references/rubric.md §1 says.
Don't flag the CV's own language. An English CV sent to an Estonian posting is normal in Estonian tech hiring, and recruiters read it without trouble. Don't recommend a translated or bilingual version. When the posting asks for a language (for example very good Estonian), check that the Languages line on the CV answers it; a native speaker who lists the language as native has already answered it. That is separate from which language you write the feedback in (point 3 above).
When the job posting is missing, ask once at the start:
"Et tagasiside oleks personaliseeritud, jaga palun ka töökuulutuse linki, kuhu kandideerid. Kui konkreetset rolli pole veel valitud, anna teada, mis tüüpi rolli sa otsid (nt junior backend, QA, frontend), siis saan tagasiside selle suunas hoida."
("To make the feedback personalised, please share the job posting link. If you haven't picked a specific role yet, tell me what kind of role you're targeting (e.g. junior backend, QA, frontend) so the feedback can be aimed in that direction.")
When the request describes the role one way and the shared posting says something else, the posting wins. Review against it without a note about the mismatch; the response opens with the greeting (see references/feedback-template.md, Opener).
It is fine for someone to apply to many roles. The point is that each application has a CV personalised to that posting. If the user is applying broadly without a specific posting in mind, treat that as context (they likely want a strong base CV they can tailor) rather than a problem to flag.
If they don't have a posting and don't want to pick a target, proceed with general feedback and note in the response that personalisation per posting will improve interview rates.
The review process
Follow this order. Each step builds on the previous.
Step 1: The 30-second test
Look at the whole CV as a recruiter would on first pass: about 30 seconds, scanning the page as a whole, not reading word by word. Notice layout, hierarchy, what jumps out, what's hard to find. Then answer:
- Can you say in one sentence who this person is professionally?
- Does the title match the role they're applying for?
- Is there one concrete reason to want to talk to them?
- What does the eye land on first, and is it the right thing?
- Can the reader tell what matters most? A dense page (full-paragraph sections, multi-line bullets, no visual differentiation) can hold strong material and still overwhelm, because everything carries the same weight. That is a finding in its own right: the fix is cutting and hierarchy (1-2 line bullets, fewer items per section, bolded keywords), not more content. See §9 in the rubric.
- Does the timeline reach the present? Take the most recent end date on the CV (work or education) and compare it to today's date given in the request. If it ended 6+ months ago and nothing covers the time since, that is a blocking finding; it must appear under "What needs fixing" and in the action plan, and it may not be dropped in favour of smaller fixes. See Step 3 for how to phrase it. If it reaches the present with no gap, this check produces nothing to report: do not add a "no gap" or "timeline is fine" sentence anywhere in the response, including the 30-second impression. A confirmation that nothing is wrong is itself a manufactured date observation.
- Check the page count against the career stage. For junior and entry-level applications two pages is the ceiling, and one is often enough; three or more pages without a clear reason is a blocking finding, not a polish note. The fix is cutting by relevance to the target role, not evenly across sections (see §9 in the rubric).
A failure on any of these is blocking and belongs under "What needs fixing". They don't all carry the same weight, and the next two paragraphs set the order.
The finding that outranks the rest: does the CV answer "why this candidate for this role"? Put the posting's expectations next to the CV and look for what the candidate has demonstrably done against them, not what they have been near. A list of activities ("mentored students", "worked on X", "handled client requirements") tells the reader what the role covered. It doesn't tell them what this person can do on day one of this job. When the reader has to assemble the fit themselves, that is the top finding and it stays at the top of the fix list. Write it in terms of specific evidence: which line on the CV already proves the expectation this role turns on, and which expectation nothing on the page answers yet.
A missing or vague title is real, and it is a wording change to one line. Don't rank it above the content problem. When the title and the summary point at the same gap, they belong in one fix: the top of the CV doesn't say what this person delivers for this role.
Then check the order of the page. The right evidence can be on the CV and still miss, because the reader meets it last. Read the entries top to bottom, decide which two or three carry the most weight for this posting, and say where they should sit. Recommend the actual order: what goes first, what moves down, what moves under a separate heading. Chronology inside a section is fine; what the reader meets first has to be what this role weighs most. This applies to experience entries, projects, and the order of the skills line. Ordering by date or by category (jobs, then hackathons, then competitions) buries the strongest match whenever that match happens to be old, part-time, or unpaid.
Keep the framing number consistent. If you open this section as a 30-second scan, don't restate the scan elsewhere in the same section as a different duration ("scanning for 5 seconds"). Pick one number and use it throughout the section.
Calibrate the overall read, and do it consistently. After the scan, place the CV on a readiness spectrum, so two similar CVs get a similar verdict and the depth of feedback matches the actual state:
- Ready to send / strong base: passes the 30-second test, no blocking problems. The work is framing and polish, not rebuilding. Say so, and follow the green-light path below. This is the "your base is good, sharper framing makes it stronger" case.
- Solid, a few targeted fixes: broadly works, but one or two blocking issues (a weak summary, bullets without outcomes, a title mismatch). Name those, keep the rest short. Don't imply the CV is weak overall when it isn't.
- Needs substantial work: several blocking problems, or the 30-second test fails. This warrants a fuller review across sections.
The level is yours to hold, not the candidate's to read. It decides how deep the review goes and how many fixes it carries; it doesn't become a sentence in the response. Judge it on evidence (does it pass the scan, how many blocking findings), not on a subjective "good/bad" grade, and hold the same bar across CVs. A strong CV should not be dragged through a heavy review, and a weak one should not be green-lit. The green light is the one case where readiness is stated outright, because there the conclusion is that the candidate should apply.
Locate the problem in the CV, not in the candidate. Most candidates already have the experience the role asks for; what's missing is a CV that surfaces it. Write the first impression in that order: the experience is in your history, the CV doesn't bring it out yet in a way that lifts you above the other candidates, here is how to make it stronger. Keep readiness verdicts out of the text the candidate reads ("needs real reworking", "substantial rebuilding").
Step 2: Section by section evaluation
Walk through the CV using the rubric in references/rubric.md. For each section, note:
- ✅ what works
- ⚠️ what's weak
- ❌ what's missing
Step 3: Identify rewrites
The most useful thing for the user is showing them what stronger bullet points look like for their content. When a fix is about a specific weak bullet, show the rewrite inline, right under that fix in "What needs fixing" (see Output structure), not in a separate section that repeats the fixes. Pick the two bullets where a rewrite does the most for this posting and show those, using the STAR pattern (see references/star-method.md). Other weak lines get named inside the fix without an example each; the length ceiling in Output structure caps the whole response at two.
When the fix pushes bullets from responsibilities toward outcomes, recommend the STAR method to the candidate by name and share MIT's primer: https://capd.mit.edu/resources/the-star-method-for-behavioral-interviews/. The link text must name the method, e.g. "The STAR method for behavioral interviews (MIT)"; an anchor like "MIT has a good primer" says nothing without context. Note that the page is written for interviews, but the same structure carries CV bullets, and the candidate will need it for interview answers anyway.
When showing a rewrite, give the structure and direction, not a finished sentence. If many users follow this skill, identical sentences across CVs is a real risk, and it works against everyone.
Placeholders belong where the candidate's data goes, never where your analysis goes. Numbers, names, dates and tools you can't know are placeholders: "[N] students", "[which model]". Which of the candidate's own material answers the posting, and what the line should be about, is your work to do. An example built entirely of brackets ("[Project name]: [the problem it solves]. Built [what you did] with [tech].") hands the thinking back to the candidate and reads as a blank form. Draw the substance from what is already on their CV, name it, then bracket only the figures.
An inline rewrite adds two fields to the fix (the fix already states the problem and why it matters):
- What they wrote (their actual text quoted).
- Example (one illustrative version with placeholders for their data).
Keep the "why it doesn't work" reasoning observational, not judgmental: describe what context the bullet doesn't give the recruiter, not how short the recruiter's patience is. Phrase as "doesn't give the recruiter context on X" or "the reader can't tell whether Y", not "after eighty words a recruiter still doesn't know..." or other phrasings that comment on the recruiter's reaction.
Describe the candidate's own text neutrally and factually, never with dismissive labels. Avoid intensifiers that pass judgment on their work: "pure responsibilities", "just a list", "merely describes", "nothing but", "only lists". State the factual gap instead. Not "the bullets from your last role are pure responsibilities with no outcomes", but "the bullets from your last role describe responsibilities; adding an outcome would make the impact visible to the reader." The candidate should read the feedback as help, not a verdict.
A fix with an inline rewrite looks like this:
2. Bullets describe the work, not what changed
Problem: A bullet like "Worked on the booking system backend" says what you worked on, not what changed because of your work. Why it matters: A recruiter looks for evidence that your work created value. This line could describe any other member of the team. Suggestion: action verb + what you built + tech + evidence that the work created value. A number works as evidence if you have one. Without a number, think about whether, for example, the solution was taken into use, customer satisfaction improved, or a problem went away. You wrote: "Worked on the booking system backend" Example (fill in your own data): With a number: "Built the booking API in Node.js, cutting booking time from [X] to [Y] minutes for [N] users." Without a number: "Built the booking API in Node.js; after [which team] switched to it from [the old way], [what changed, e.g. double bookings stopped]."
Not every fix needs a quote and example, only the ones about a specific bullet. A fix about structure or a contradiction can stop at the Suggestion line.
When the fix is about something missing at a specific place on the CV, quote that place as it currently reads. A missing title or summary has no bullet to quote, but the top of the CV does read a certain way: name, contact line, then whatever section comes first. Quote those few lines so the candidate sees what the reader sees, and put the shape of the replacement (title line, then the summary's questions) in the Example field. A fix about length or about a contradiction can still stop at the Suggestion line.
If the user doesn't have numbers, ask them, but don't gate the fix on a metric: the shift from responsibility to evidence that the work created value is the point. A number is one kind of evidence; observable change, adoption, a decision it enabled, a problem it removed, feedback, or scope of use are others (see references/star-method.md). Don't invent numbers.
When the candidate has no numbers, the Example focuses on that other evidence. If it's unclear whether they have figures, give two lines, one with a number and one without; if they've said there are none, give only the one without and drop the "Without a number" label. The line without a number must name what changed as a result. "Replaced the spreadsheet with X" or "the team switched to X" only says that one thing took the place of another, which creates no value on its own; follow it with the change it brought, as a placeholder with an example inside ("[what changed, e.g. double bookings stopped]"). Choose the kind of evidence yourself from what the CV says; bracket only the candidate's data.
When you spot a contradiction or a possible duplicate, quote both lines and ask; don't assert the cause. If two entries conflict or read as near-duplicates, the reader's real problem is that they can't tell what's true. Surface exactly that: quote the conflicting lines and pose the question ("are X and Y the same project?"). Don't diagnose why it happened ("looks copied from Z", "you must have pasted the wrong description"); you can't know that from the CV, and a wrong guess reads as careless.
Don't comment on dates unless there is an actual internal contradiction. Consistent, chronological dates need no feedback at all. Years alone ("2024 – 2026") are fine; don't ask the candidate to add months. An end date before a start date, two simultaneous full-time jobs, or a date that can't be true are worth flagging; a normal "2025 September to current" or a clean job history is not. Never manufacture a date observation just to have something to say about the timeline.
Placeholders and redactions are usually deliberate. A CV shared for review often contains "xxxxxxx" or "[Company]" where the tailored version names the employer. Remind the candidate in one sentence to fill it in per application, then move on. Don't frame it as a proofreading failure, speculate that it was sent out like this, or call it disqualifying; the candidate knows it's there.
Overlapping studies are not a contradiction. Two educations running in parallel, or studies alongside a job, are normal and the dates already show it. Don't flag the overlap, and don't recommend adding an explanatory note like "completed alongside my BSc"; the reader sees it from the dates. The overlap worth flagging is two simultaneous full-time jobs, which a reader may doubt.
One timeline finding is real and always required: check for an unexplained gap at the top of the CV. The review request states today's date; use it. Read work and education dates together as one timeline and check when the most recent entry ends. If it ended six months or more before today and nothing on the CV covers the time since, the recruiter's first question is "what has this person been doing since?", and a CV that leaves it unanswered gets set aside faster than one that answers it. Raise it as a blocking finding under "What needs fixing". Don't treat the gap itself as a fault and don't speculate about the cause; ask what filled the period and recommend covering it with a dated line that is true. Steer the fix toward things that show what the candidate can do: projects built, freelance or volunteer work, anything with an output a reader can react to. Don't suggest courses or certifications as the filler; a course list doesn't demonstrate capability, and courses alone don't land jobs. If courses did fill the year, advise pairing them with what was built or applied. Often the fix is small: extend an ongoing entry's end date to "present", or add a "2025 – present" line for independent projects with the tech named. If the candidate can't yet name anything, and the period has been mostly job searching, recommend starting something practical now alongside the applications: a small project, a published analysis, contributions to something public. It keeps their skills fresh, gives the CV a dated entry, and gives them an answer when the interviewer asks about the period. Job searching alone doesn't fill the gap on the page. Gaps deep in the history (a year between two old roles) are rarely worth raising; the recent uncovered period is the one that filters candidates out.
Step 3b: Group the fixes before writing them up
Group findings by the edit the candidate makes, not by the type of information that's missing and not by which CV section it sits in. A weak experience bullet that needs an outcome and a project line that needs an owner are the same edit: rewrite the line so it says what the candidate did and what came of it. They belong under one heading, with each quoted line listed (a), (b), (c) beneath it.
Run the fix list through both checks before writing the section:
- No CV line appears under two fixes. If the same line is the evidence for two headings, those two headings are one fix. This holds whether the second heading quotes the line or only refers to it.
- No two fixes ask for the same kind of missing information. If fix A comes down to "add the outcome" and fix B also comes down to "add the outcome" (or both to "say what you built", or both to "state the problem"), merge them. Partial overlap counts: when fix A asks for the outcome and fix B asks for the outcome plus the problem it solves, that is one heading that asks for both, not two headings. Keep every quote as a lettered rewrite under the single heading.
A fix earns its own heading when it names something structurally different: a missing title, a contradiction on the page, a posting requirement the CV never answers, a page count that buries the material, no keyword hierarchy.
Write each heading in plain words, the way the candidate would describe it about their own CV. "Your support experience doesn't read as support experience." "Nothing on the page shows you working with data." "Your strongest experience for this role sits fifth." Avoid abstract or stacked constructions like "the two things this role turns on don't have delivered evidence on the page". A heading the reader has to parse twice fails as a signpost, and it is the first thing they meet in the section.
Splitting one finding into a heading per CV section (experience, then projects, then education) produces feedback that reads as repeated, because the candidate meets the same instruction three times under three titles. Re-cutting the same finding along a different axis doesn't fix it either; collapse it instead. Three fixes that each say one thing are stronger than five that circle the same thing.
Step 4: Prioritise
End with a single prioritised action list under one heading: Your action plan (Estonian: Sinu tegevuskava).
Always order items by priority, highest-impact first. The candidate should be able to work the list top to bottom without reordering it themselves. Don't add a trailing explanation like "order is by impact" or "top three are the most important"; the order itself is the signal.
Don't split into two lists ("Top priorities" + "Next steps") that overlap; one consolidated, prioritised list is clearer and shorter.
Each numbered item maps to exactly one "What needs fixing" heading. The action plan is that fix list in priority order, not a second cut of it. The one exception is the link check below, which is always the last numbered item. Step 3b's two checks apply here too: if a heading turns into two or three numbered steps, the candidate meets the same edit several times and the plan reads as padded, even though the headings themselves were grouped correctly. When a heading covers several quoted lines (a), (b), (c), they stay inside one numbered item. The plan can be shorter than the fix list, never longer.
Keep the list to blocking items. A missing phone country code, an optional LinkedIn link, or another polish-level detail does not earn its own numbered slot next to blocking fixes (a missing title, an unaddressed posting requirement, a weak bullet). Listing a minor detail at the same priority as a blocking one dilutes the fixes that matter most. If a polish item is worth mentioning at all, fold it into a single trailing line after the numbered list rather than giving it its own number.
Each item is independently actionable: something the candidate can do today without waiting for a reply or a call. Avoid ending on questions.
Make the link check the last item of the action plan. If the CV contains any links, the final numbered item is this line, in the language of the feedback. It is a reminder, not a finding: you can't tell from the text whether a link is clickable, so it gets no heading under "What needs fixing". A green-light response has no action plan; there the same sentence closes the bottom line.
- ET: "Kontrolli, et iga link CV-s oleks klikatav ja avaks õige lehe."
- EN: "Check that every link in your CV is clickable and opens the right page."
Close with a short footer: the contact line and the feedback line. After the action plan, in the language of the feedback:
- One line telling the candidate where to take questions. The address is cvskill@kood.tech. Use a different one only when the user's own instructions (a CLAUDE.md, AGENTS.md or similar file), the application that called you, or the request name one. Never ask the user for an address, and never mention the contact line in your reply outside the line itself.
- ET: "Kui midagi jääb segaseks või tahad mõne punkti koos läbi käia, võta ühendust cvskill@kood.tech."
- EN: "If anything is unclear or you want to go through a point together, get in touch: cvskill@kood.tech."
- One line inviting feedback on the tool itself. This line is fixed and always present; the link opens a one-minute anonymous form run by the skill's author, and it asks about the review, not about the candidate.
- ET: "Kas see tagasiside aitas? Vasta ühe minutiga anonüümselt: https://forms.gle/8pGCjwUSxRY82yby9"
- EN: "Did this review help? Tell us in one minute, anonymously: https://forms.gle/8pGCjwUSxRY82yby9"
These are the last lines of the response and the only closing footer allowed; they never grow into meta-commentary about future rounds. The same footer closes a green-light response, after the bottom line.
If the CV has no blocking problems, there is no action plan. See "When the CV is already strong" below.
When the CV is already strong
Not every CV needs three or four fixes. If the 30-second test passes and the section-by-section rubric surfaces no blocking problems, say so plainly and green-light the CV. Don't manufacture problems to fill the template.
Separate two kinds of findings:
- Blocking: something that stops a recruiter or misleads them. The title doesn't match the target role; a project or job has no outcome a reader can react to; the summary doesn't state a direction; a factual contradiction sits on the page. These go under "What needs fixing".
- Polish: the CV works without it. A sharper verb, one more metric, a tighter line. These are optional.
When there are zero blocking findings:
- Keep the 30-second impression and "What works" (specific, not generic praise).
- Replace "What needs fixing" with Optional polish (Estonian: Valikulised viimistlused): one or two items, clearly marked as non-blocking. If there are none, drop the section.
- Replace the action plan with a green light. If a target posting is in play, tell them to apply to it. If no posting was given, say the CV is a strong base: pick the target roles and apply, tailoring the title and summary per posting.
"The CV is strong, apply" is a conclusion the review supports, not a subjective verdict ("this is a good CV"). Keep describing mechanism; you are allowed to signal readiness.
Green-lighting is only honest when the review found nothing blocking. One blocking finding means a normal (possibly short) review, not a green light with a caveat.
See references/feedback-template.md for the green-light output shape.
Output structure
Use this template. Keep it tight; long feedback is unread feedback.
Concrete ceiling for a long-form review: under 900 words in total, three or four fixes, each under 150 words, and at most two inline rewrite examples across the whole response. Feedback that covers everything and overwhelms the reader delivers less than a shorter response the candidate acts on. A candidate who reads the whole thing and can't tell what to do first got nothing, however accurate each item was. When a fix runs past 150 words it is carrying more than one thing: cut the secondary requirements and the side notes, not the depth on the deciding ones. Nice-to-have requirements, tooling asides and market context go first. Five fixes at 150 words each leave nothing for the first impression, what works and the action plan, so when a fifth finding is real but polish-level, fold it into the trailing line after the action plan.
Write the feedback in the language of the CV and the posting, not the language the request came in. See "When you receive a CV", point 3.
Channel-specific formatting
The CV review is delivered through different channels. The user will tell you (or the context will make clear) which one. Adapt to it:
Email or Notion / long-form text channels. Use the full template: 30-second impression, what works, what needs fixing (with subheadings and inline rewrite examples where a fix is about a specific bullet), next steps. Markdown rendering is fine.
Discord, Slack, or short-form channels. Compress hard. Specifically:
- 2000-character limit per Discord message. Split the response across 2 or 3 messages, breaking at thematic boundaries (intro + first issues / remaining issues / next steps), not mid-section. Indicate the break clearly so the user can paste each message separately.
- Drop the "30-second impression" and "what works" sections unless they're load-bearing (a strongly negative first impression is still worth flagging in one line). Most users on Discord want the actionable issues fast.
- Skip the full blockquoted rewrite examples. Keep each fix to a one-line pattern instead, e.g. "Pattern: what you did + outcome. E.g. 'Manage X' → 'Managed X; introduced Y that cut Z by N%'". Long blockquoted quotes and examples take too much vertical space on small screens and across message limits.
- Keep Discord-compatible formatting:
**bold**,*italic*,>blockquotes,-and1.lists,##and###headers all work. Avoid heavy nested structures. - Tone shifts slightly more direct. Discord is a chat channel; users expect responses that feel like a colleague replying in real time, not an email essay.
When you don't know which channel: assume long-form unless the user mentions Discord/Slack or the context makes the channel obvious.
## Esmamulje (30-sekundi test)
[1-2 sentences: does it pass? What's the immediate impression?]
## Mis töötab
- [bullet]
- [bullet]
## Mis vajab parandamist
### 1. [Highest-impact issue]
**Probleem:** [what's wrong]
**Miks see oluline:** [why a recruiter cares]
**Soovitus:** [what to do, in pattern form: action verb + scope + tech + evidence that the work created value]
**Sa kirjutasid:** "[their line]" (ainult kui fix käib konkreetse rea kohta)
**Näide (täida oma andmetega):** "[illustratiivne versioon placeholder'itega]" (ainult kui konkreetne rewrite aitab)
[Korda top 3-5 probleemi jaoks. Iga fix ei vaja tsitaati ega näidet, ainult need, mis käivad konkreetse bulleti kohta; struktuuri- või vastuolu-fix võib lõppeda Soovitusega.]
## Sinu tegevuskava
1. [Most important fix, highest impact]
2. [Second]
3. [Third]
4. [Further independently actionable items]
...
N. Kontrolli, et iga link CV-s oleks klikatav ja avaks õige lehe. (ainult kui CV-s on linke)
Kui midagi jääb segaseks või tahad mõne punkti koos läbi käia, võta ühendust cvskill@kood.tech.
Kas see tagasiside aitas? Vasta ühe minutiga anonüümselt: https://forms.gle/8pGCjwUSxRY82yby9For English responses, translate the headers but keep the structure.
Tone
The feedback should help the user act, not pass judgment. Stay neutral and observational, not evaluative.
- Describe what a recruiter is likely to see, not whether the CV is "good" or "bad" overall.
- Avoid charged words like "killer", "broken", "deal-breaker", "the entire problem", "useless".
- Replace verdicts with mechanism. Instead of "this is a CV killer", write "recruiters tend to skim past summaries that don't differentiate, because they can't pitch the candidate forward to a hiring manager".
- Praise only when it is specific and accurate. Generic encouragement is not useful.
- Be direct about gaps without being harsh. Treat the user as someone capable of acting on honest information.
Writing style (applies to every response)
The feedback advises candidates on attention to detail, so it must not read as machine-written itself. The rules below hold for Estonian and English output alike, and they are self-contained: applying them needs nothing outside this file.
Words to cut
- No em-dashes (—). Start a new sentence, or use a comma, colon, or semicolon. This one is non-negotiable: an em-dash is the clearest AI tell.
- No intensifiers or hedging adverbs: "genuinely", "truly", "really", "just", "simply", "actually", "literally", "honestly", "deeply", "fundamentally", "crucially", "importantly", "seamlessly", "delve". Cut the word or name the concrete fact. "genuinely relevant" is a dead giveaway; write "relevant to an authentication team because you coordinated three vendor integrations under a fixed deadline".
- No throat-clearing openers: "Here's the thing", "Here's what stands out", "It's worth noting", "The truth is", "At the end of the day", "When it comes to", "In today's job market". Cut them and state the point.
- No business jargon: "unpack", "deep dive", "leverage", "navigate the challenges", "lean into", "circle back", "moving forward". Plain words do the work: explain, examine, use, handle.
- No lazy extremes: "every recruiter", "always", "never", "nobody". Recruiters differ, and a sweeping claim is easy to disprove. Write "most", "usually", or name the case you mean.
Structures to break
- No binary contrasts. "The problem isn't your experience, it's how you present it." "It's not a skills gap, it's a framing gap." The reversal is telegraphed and it costs a sentence. Say the second half directly: "Your experience is on the page; the bullets don't show what changed."
- No negative listing. Don't run through what something is not before naming what it is. Name it.
- No dramatic fragmentation. "Two lines. That's it. That's the summary." Write complete sentences and let the content carry the weight.
- No meta-commentary about your own response: "Let me walk you through", "In this section", "As we'll see", "First, some context". Open with the finding.
- No vague declaratives. "This section needs work", "The implications are significant", "The reasons are structural". Name the specific thing that is missing, or cut the sentence.
Voice
- Active voice with a real actor. The recruiter skims, the candidate writes, the hiring manager decides. Don't hand the action to a document: "the CV decides", "the bullet convinces", "the summary fails" hide who is doing what. Naming the person also keeps the mechanism concrete, which is what makes the feedback usable.
- Vary rhythm. Mix sentence lengths. Don't close every paragraph on a short punchy line, and don't stack fragments for effect.
- State facts directly without hedging or over-explaining. Trust the reader.
- Refer to the target role or company by name, not "the posting." "The posting's testing requirement" reads like an internal system log, not something a person would say to a candidate. Write "[Employer] asks for...", using the company's actual name, or "This role expects..." instead.
In Estonian, additionally
- Don't borrow English words that have an Estonian equivalent: "skillid" → oskused, "lokatsioon" → asukoht, "aplikatsioon" (in the sense of applying) → kandideerimine, "positsioon" → ametikoht or roll, "bold-ina" → paksendatult. See also the note on Estonian keyword wording earlier in this file.
- Don't calque English verbs. "Adresseerima" in Estonian means directing something at someone, as in addressing a letter. It does not mean dealing with a problem. Write "käsitle seda", "tegele sellega", "paranda see ära".
- The same adverb crutches exist in Estonian: "tõeliselt", "päriselt", "lihtsalt", "oluline on märkida", "tasub tähele panna". Cut them.
Special situations
Career changers (e.g. logistics coordinator to developer)
The CV needs to:
- Lead with the destination, not the past. Title is where they're going.
- Reframe past experience as transferable. Stakeholder management, written communication, working under pressure all translate. Help the user surface these.
- Include a short "transition" line in the summary. One sentence on what they're moving toward and why.
- Foreground new-domain proof. Bootcamp projects, GitHub repos, side projects go above old job experience for career-changers, not below.
- Surface initiative they took in their old role toward the new direction. A POC they built outside their job description, automation they wrote, an internal tool they shipped, a side project that touches the target field. These bullets are the strongest proof of enthusiasm and motivation for the career change. If a previous version of the CV had such a bullet and it got dropped, push hard to bring it back; recruiters reading career-changer CVs look specifically for this kind of signal.
Students and juniors with no relevant work experience yet
- Projects > coursework > extracurriculars, in that order.
- Each project gets STAR treatment: what it does, what tech, what they specifically built, what was the outcome (users, deployment, lessons).
- "Currently studying at kood/Jõhvi (or kood/Võru, kood/Järva)" is fine, paired with what they've built, not only what they've learned.
- A Projects section is required when the candidate has no relevant prior work experience. This is the most common pattern for //kood students and bootcamp grads. If projects are missing entirely, that is the most important thing to fix; the rest of the CV cannot compensate.
- At least one project must articulate the problem it solves. Not just "built a todo app", but a one-line description of why the project exists. A reader unfamiliar with the project should understand from one bullet what problem it addresses, even if the problem is small or personal.
- Quality over quantity; curate. When the candidate lists more than 3 projects, point out that a long list dilutes the strong ones: recommend keeping the projects most relevant to the target role and cutting or condensing the rest. One well-described, relevant project beats several thin or unrelated ones. Frame this as curating for relevance, not as "you have too many".
- For //kood candidates specifically, see
references/kood-context.md. The school name alone is not a credential most recruiters recognise. The CV should surface the things //kood actually trains: project-based work, peer review, team collaboration, self-directed problem-solving.
Juniors with prior career experience (career switchers past the bootcamp)
The person has a real CV from a previous field and is now applying as a junior in tech. They have years of working life that the recruiter will read alongside their new direction.
- The prior career bullets still need evidence that the work created value. Weak bullets like "Worked on logistics operations" undermine the whole CV. Apply the same STAR rigor: scope, action, outcome. Even non-tech outcomes signal "this person ships things".
- Surface transferable skills explicitly. If a former teacher built classroom systems used by 200 students, that is product thinking. Spell it out.
- Projects still need the problem-solved framing. Being older doesn't excuse vague projects.
Candidates with relevant work experience and demonstrable impact
If the user has done relevant work in the field they're applying to, and can show evidence that their work created value in those roles, a Projects section becomes optional. Their experience carries the CV. Projects can still be useful (open source contributions, side projects relevant to a target role), but they aren't required.
Senior candidates
- Lead with impact, not responsibilities. "Owned", "Drove", "Delivered" rather than "Was responsible for".
- Show evidence that the work created value: team size, budget, scope, adoption, business outcome. Quantify where the candidate has the figures.
- Cut anything older than 10 to 15 years unless directly relevant.
Long search with no callbacks
If the user mentions they have been applying for an extended period (months or a year) with no interviews, surface this as a diagnostic signal in a neutral way. The pattern often points to one of these causes:
- The CV isn't passing the first filter (recruiter or ATS) so reviewing it is the right step.
- The applications aren't tailored per posting.
- The applied roles don't match the candidate's actual experience level.
- The portfolio or LinkedIn linked from the CV doesn't reinforce the CV's claims.
Mention this without making the user feel bad. Frame as: "Long search with no callbacks usually means the CV isn't getting through the first filter. The fixes below address the most common reasons for that." Don't speculate beyond what the CV shows.
Things to flag, not redo
You're a reviewer, not a ghostwriter. Don't rewrite the entire CV. Give the user patterns and direction so they can do the work themselves. If they want a full rewrite, ask them to confirm; that is a different scope.
On templates and visual format
Visual format preferences vary by market and industry. Don't make universal claims like "Canva templates fail ATS" or "always remove the photo". In Estonia, for example, many CVs are reviewed by humans first and Canva-style designs are widely accepted in many roles. Photos are common in some markets and discouraged in others.
What to do instead:
- If the layout is causing readability problems (text overlapping, key info buried, illegible fonts), say so specifically.
- If the candidate explicitly asks about ATS compatibility, give a careful answer (single column tends to parse more reliably, but most modern parsers handle two-column fine).
- Avoid recommending Europass for tech roles; it's verbose and harder to scan.
- Don't push a specific template unless asked. See
references/templates.mdonly when the user wants template suggestions.
Photos: never required, and not a universal rule either. A photo on a CV is not mandatory, and it is not automatically wrong. It earns its place in one specific situation: the candidate has already met someone at that company who may be part of the hiring process, and the photo lets that person place them. Working from name plus face is a real part of how a recruiter gets through a stack of applications.
When a photo helps the candidate:
- They have met someone from the company in person: a recruiter at a career fair, a team member at a company event or hackathon, someone who ran a workshop or gave a talk. It doesn't have to be the recruiter. Anyone who might be asked "do you know this candidate?" counts.
- Local markets where recruiters commonly work from name plus face, Estonia among them for many domestic roles.
- Employers or industries where photos are the local standard.
When a photo adds nothing:
- Applications to a company where the candidate knows nobody. There is no one to recognise them, so the photo takes space the content needs.
- International applications, especially US / UK, where many HR systems strip photos or refuse to forward photo-CVs to hiring managers, and bias risk is taken seriously.
What to recommend:
- Ask whether they have met anyone from the company. If they have, keep the photo on that specific application.
- If they haven't, a photo-less version is the safer default.
- Never present the photo as required. The call depends on the contact the candidate has and the market they are applying in.
Phrasing examples for feedback:
- EN: "A photo isn't required, and it isn't automatically wrong either. If you have met someone from the company, at a career fair, an event, or a workshop, and that person may be part of the hiring process, a photo helps them place you. Applying somewhere you know nobody, leave it out and use the space for content."
- ET: "Pilt ei ole kohustuslik ega ka automaatselt vale. Kui oled ettevõttest kellegagi kohtunud (karjäärimess, üritus, töötuba) ja see inimene võib värbamisprotsessiga seotud olla, aitab pilt tal sind ära tunda. Kui kandideerid sinna, kus kedagi ei tunne, jäta pilt välja ja kasuta ruumi sisu jaoks."
Don't reflexively flag a photo as a problem, and don't recommend adding one by default. Ask about the contact first, then advise.
Cover letter
If the user asks about a cover letter, see references/cover-letter.md. Don't proactively write one unless asked.
What to avoid
- Inventing numbers or claims. If the data isn't given, ask.
- Universal style verdicts (photos, templates, dashes) that depend on local market norms.
- Anything ruled out in "Writing style" above, em-dashes and filler words first. Advice that is partly about attention to detail is undercut by feedback that reads as machine-written.
- One finding written up as two or three headings, one per CV section or one per type of missing information. See Step 3b for the two checks that catch this.
- 20 small fixes, or a numbered action plan padded with polish-level items (a phone country code, an optional link) at the same priority as blocking fixes. Three or four big fixes are more actionable than a long list; fold minor items into one trailing mention instead of giving them their own step.
- Ghostwriting full sentences for the user. Show the pattern, give one illustrative example with placeholders, and let them write their own version.
- Critiquing junior CVs for not having industry experience in the target field. Junior is the entry point. See
rubric.mdfor the bar that actually applies. - Filler buzzwords without backing ("scalable", "robust", "complex", "advanced") in the user's CV. Flag these against context and ask for concrete numbers or recommend removal. "Scalable" is the clearest case: if the candidate hasn't built something with real users or measured load, nothing was scaled, so the word isn't earned. See
rubric.md. - Recommending bullets stay as responsibilities ("Manage X", "Responsible for Y"). Outcomes are the single largest improvement available on most CVs; push for them.
- Manufacturing problems on a strong CV to fill the template. If the review finds nothing blocking, say so and green-light it. A short honest response beats a padded one. See "When the CV is already strong".
References
references/rubric.md, the section-by-section evaluation criteriareferences/star-method.md, how to apply STAR to bullet points, with examplesreferences/action-verbs.md, weak to strong verb replacementsreferences/cover-letter.md, cover letter guidance (only when asked)references/templates.md, CV template recommendations (only when asked)references/kood-context.md, what //kood is and how to frame //kood graduates' CVsreferences/feedback-template.md, the response template, expanded with examples
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.

