Skip to content

Blog

Why Cooked Shows Your Skill Gaps Instead of Hiding Them

By Nwuba Joshua · Updated 8 November 2026

When an AI tailors a CV, there's a quiet temptation built in. The job asks for GraphQL, your CV doesn't mention it, and the easiest way to raise the match score is to slip in something vague that suggests you've used it.

I decided early that Cooked shouldn't do that. Here's why, and what it does instead.

A faked skill costs you the interview

Getting past the filter is only step one. The next step is a person asking, "Tell me about a time you used GraphQL." If the CV implied something you can't talk about, you lose the job at the moment you were closest to getting it, and you lose that recruiter's trust too.

What Cooked does instead

  • It only rewrites what's already in your CV: rewording, reordering and using the job's terms where your real experience supports them.
  • If the job asks for something your CV doesn't show, it's listed under gaps, not worked into the text.
  • Every rewritten bullet is traced back to the line in your original CV it came from, so you can check in seconds that nothing was invented.
  • It flags any new numbers or skills that weren't in your original, so you can catch mistakes.

Gaps are useful information

A list of gaps tells you something real: whether this role is a good fit now, what to learn next, or what to address honestly in a cover letter. If you do have the skill but left it off your CV, the gap is a reminder to add it properly, in your own words.

Why this matters for AI tools in general

AI writing tools are very good at producing confident text. That's exactly why a CV tool needs guardrails: your CV is a factual document that you'll be asked to stand behind. I'd rather Cooked gave you a slightly lower score that's true than a perfect one that falls apart in an interview.

Try it on your own CV: paste a job link and see the tailored version, your gaps, and where every bullet came from.

Try Cooked free

Related