Repository navigation
blind review
You rewrote your CV, polished your LinkedIn, and now you can't tell anymore how it reads to someone who has never met you. blind-review gives you that read: an AI reviewer that plays a senior recruiter with one role to fill and 30 minutes, sees only what's on the page, and tells you — without softening — whether they'd call you and what would make them pass. Then a coach that does know you turns that read into a plan: a score now and after the changes, and the exact text to paste.
It's part of the kings-career plugin, but it runs on its own: no profile, no pipeline, no other setup.
- Why "blind"
- What you get
- The improvement plan
- What you need
- Setup
- Running a review
- Acting on the result
- Good to know
An assistant that knows you fills in the gaps: it knows you led that project, so it doesn't notice the CV never says so. A recruiter doesn't. The reviewer agent is built to know nothing but what it's handed:
- It gets only the target role, the artifact (your LinkedIn URL, your CV, or a message) and where to write the report — never your history, notes or what you hope to hear.
- When something is unclear, it reports it as a gap. It never fills it in.
- It reviews one artifact per call, so the CV doesn't explain the LinkedIn and vice versa.
- What you know about yourself only enters after the cold read, through a second agent (the coach). Nothing it knows ever goes back to the reviewer — otherwise the read would stop being blind.
One report per artifact, written to a file and shown in the chat:
| Section | What's in it |
|---|---|
| Score and verdict |
n/10 and Yes / Maybe, leaning yes / Maybe, leaning no / No for the role you named |
| 6-second scan | What the top of the page says at a glance: role, seniority, years, last company, location — and whether they'd keep reading |
| Strengths | What would make them call you |
| Red flags | What would make them pass, most serious first: positioning, timeline gaps or overlaps, seniority that's claimed but not shown |
| Claims I'd question | Numbers and statements they'd probe in an interview, and why |
| Keyword gaps | What this kind of role usually asks for that they didn't find |
| Fixes ranked by impact | What to change, where, and why |
With both a LinkedIn URL and a CV, you also get a cross-check: where the two disagree (titles, dates, companies, numbers, stack) and what one has that the other lacks. A CV is also checked for format problems an applicant tracking system would trip on.
It can review messages too — a connection note, a DM, an application email, a reply to a recruiter — as the person receiving it would: would they open it, accept, reply, or scroll past?
Once every cold report is in, a second agent — the coach — reads them together with what is known about you: your CV, your LinkedIn and the answers you give (or, with the full plugin, your facts file). For the CV and the LinkedIn you get:
| Part | What's in it |
|---|---|
| Score |
n/10 now and n/10 after the changes, and what still holds it below 10 |
| Fixes by impact | Where, the current text, a ready-to-paste rewrite, why (which finding it answers) and the fact it's based on |
| Questions | Only those that unlock a fix — e.g. "how many users did that app have? With the number, this bullet reads: …" |
| Honest gaps | What the role asks that you don't have, and how to address it in an interview — never added to the page |
| Reviewer misreads | Where the page is right but a recruiter may read it wrong, with a wording change that prevents it |
Answer the questions in the chat and the coach updates the plan once more.
flowchart LR
A[Your CV and LinkedIn] --> B[Blind reviewer<br/>knows nothing about you]
B --> C[Cold reports]
C --> D[Coach<br/>knows your facts]
D --> E[Plan: score now → after<br/>fixes with text to paste]
| Piece | Why |
|---|---|
| Claude Code | Runs the review |
The kings-career plugin |
Holds the skill and the reviewer agent |
| The Claude in Chrome extension, logged in to LinkedIn | Only to review a LinkedIn profile: the reviewer reads it in your browser. Not needed for a CV alone |
| Your CV as a PDF (or any file Claude can read) | Only to review the CV |
The reviewer and the coach run on Opus — judgment with no context, and rewrites that must stay true to the facts.
claude plugin marketplace add Kings-Platform/KingsAI
claude plugin install kings-career@kingsai --scope userRestart Claude Code after installing. That's all — no profile is needed for this review.
Open Claude Code in any folder and say what you want reviewed and for which role:
Review my LinkedIn and my CV as a recruiter would, for a Senior Backend Engineer role
at a bank in São Paulo. LinkedIn: https://www.linkedin.com/in/<your-handle>
CV: ~/Documents/cv.pdf
Other ways to ask: "what would a recruiter think of my CV?", "blind review of my LinkedIn for a tech lead role, remote", "would a recruiter answer this message?" followed by the text.
If something is missing, it asks once — the role, the URL or the file — and reviews whatever you gave it. Name the role as a job, not as you: "Senior iOS engineer, remote, international", not "me, with 7 years of iOS".
The language matters: a profile reviewed for an international role is read in English, one for a local role in the local language. A role covering two markets gets one review per language.
The plan is ordered by impact: change the top items first (headline, summary, anything that made the recruiter pass), then the rest. Nothing is edited for you: the CV and the profile are yours to change, and every proposed line is built only from what is already true about you.
Run it again after the changes — with the earlier report and plan in the same folder, the new ones say what moved: score, what was fixed, what's new.
- It only reads. The reviewer never clicks Connect, Follow, Like, Message or Edit on LinkedIn, and closes its tab at the end.
- Logged in as yourself: the browser shows LinkedIn as the owner sees it. The reviewer ignores what only you see (edit buttons, analytics, profile views) and says when a section may still be showing your own language instead of the recruiter's.
- The reports are yours. Without a profile they go to the session's scratch folder; ask Claude to copy them anywhere you like.
- Going further: the full kings-career plugin uses the same reviewer on your outreach templates and, with a profile, checks every finding against your own facts file automatically.