Boolean keys out. One sentence in.
How to write a search as one plain sentence about the person, the 10 best sentences, and a Claude skill that turns any job post into one. Plus the honest part: where a sentence still needs something to run on.
Why every string breaks
A Boolean string matches words. The person you want is described by work. Three ways that gap shows up.
Titles drift
The same job is written a dozen ways. Every title you didn't list is a person you never see, and the list is never finished.
Words aren't work
A word in a skills list matches the same as five years of doing it. The string can't tell “ran it in production” from “went to a talk”.
NOT cuts good people
One old line removes them. A NOT on “consultant” drops the engineer who consulted for one year a decade ago.
The four parts of a search sentence
Brief the search the way you'd brief a sharp colleague. Four parts, in this order, in one sentence of 15 to 35 words.
1 · Who
The job in plain words, plus level if it matters. One title, the most common one. Never a list of titles.
2 · Where
The place and how they'd work there. Say the range the way a person would.
3 · Proof
One thing they have done, as a verb with context. Something you could quote from a profile. Two at most, joined by “and”.
4 · No-go
Only one, and only if it decides who fits. Say it as a kind of person, not a banned word.
Cut a key
Pick a role, a place and the one thing they must have done. The machine cuts the sentence and shows the Boolean string it replaces, struck out, with where that string breaks. Roles and examples are made up for practice.
The string it replaces
“juicebox, metaview, your looks faster and easier to use but with more relevant profiles”

The 10 best sentences
Each one follows the four parts. Copy one, change the place and the proof to your role, and keep the shape.
“In production” separates the people who ran it from the people who listed it.
Two proofs joined by “and”, both things a profile can show. The limit is two.
“Written” code, not “maintained” it. The verb does the filtering.
Shift and setting are the real must-haves. “Registered nurse” alone finds every nurse in the city.
The no-go names a kind of seller, so it removes account managers without a list of banned titles.
“Only” matters. Someone who did two years in audit and three in industry still fits.
For remote roles, the time zone is the place. “From first sketch to release” rules out people who only did one stage.
Size and shifts tell you more than any title. A “site lead” and a “general manager” can both fit.
The language goes last. The work is the must-have; the language is a tie-breaker.
Who they partnered with, how many, and the hard moment. Three facts, one clause.
Make Claude write them for you
The skill reads a job post or the hiring manager's notes and writes the sentence, with the parts labelled and what it left out.
Add the sentence-writer skill
Save this as SKILL.md in a folder called search-sentence, zip the folder, and add it in Claude's settings under Skills. If skills aren't open on your plan, paste the text into a Project's instructions.
Feed it the role
Paste the full job post or your intake notes. The hiring manager's own words beat the post every time; paste them if you have them.
Rewrite an old string
Got a saved string that worked once? Turn it back into the person it was trying to describe, then check the sentence against the role you have today.
Check the sentence before you use it
Read it out loud. A colleague who heard it once should be able to name a person who fits. Then run these traps.
“pretty good … especially for semiconductor, because it's much harder to find semiconductor talent”

The wall
Claude can think, but it can't see people. Plain Claude writes a great sentence and then has nowhere to run it: it has no profiles to search.
Most people-search boxes still want keywords, so the sentence turns back into a Boolean string, with every break above. That's why the skill has a fallback. And because plain Claude never saw the people, it can't tell you why any of them matched.
The same sentence, two ways
Plain Claude
- Run the skill to get the sentence.
- Ask for the fallback string, because the search box needs keywords.
- Paste the string into a people search and fix what it misses.
- Run it again for each title variant and each commute town.
- Open each profile and check the proof by hand.
- Paste the good ones into Claude to write a reason for each.
Same job in The Cognitive
- Type the sentence into the search. If it leaves out something that changes who to look for, it asks one question with 2 to 4 answers before it spends anything.
- People appear in under a minute and settle into a list ranked by fit, including people with other titles.
- Every card says why the person fits, with a quote from their profile.
- Or let Claude run it: add The Cognitive as a custom connector in Claude with
https://app.thecognitive.io/mcp, sign in on the Connect page and allow it.
“My front runner is … The Cognitive … Yours really beat JuiceBox, PIN, and Metaview”

Type your first sentence today
Make a free account and paste one of the ten sentences with your own role and place. People come back ranked, each with the line from their profile that shows why they fit.