The Cognitive

Find the people search walks past

Some of the best people have a three-line profile: a title, a company, some dates. Keyword search can't match words that aren't there. This skill starts from the work each company does and reads the person from that. Below is the method, the rules for reading a thin profile, the full SKILL.md, and the point where Claude stops.

A dark list · people and companies made up · move the torch
Role: payroll lead who runs weekly payroll for hourly staff in several states
Drag or move over the list, or tap a person. The keyword torch reads only the words on the profile. The company-work torch reads what the company does.
100+ recruiters have shared their feedback
“juicebox, metaview, your looks faster and easier to use but with more relevant profiles”
LinkedIn message: compared with Juicebox and Metaview, faster and easier to use with more relevant profiles

Why thin profiles stay dark

A keyword search matches words people wrote about themselves. A busy payroll supervisor who never wrote a summary has three facts on show: a title, a company and dates. None of them say "multi-state". So the search starts from the company. If the company can't run without the work, someone there does it, whatever their title says.

The method, step by step

Six steps. Steps 1 to 3 take a while the first time for each role family. After that you reuse the company list.

Write the work, not the keywords

Describe what the person does in a normal week, with verbs and objects. Skills lists and adjectives go. If a line could sit on anyone's profile ("detail-oriented", "strong Excel"), delete it.

The work: [verb] [what] for [whom], under [the condition that makes it hard]. Example (made up): Runs weekly payroll for hourly staff spread across several states, files each state's taxes, and fixes errors before payday.

The hard condition is the part that matters. "Runs payroll" fits a thousand people. "Weekly, hourly, several states" points at a handful of company types.

Ask which companies can't exist without that work

Claude is good at this part. It knows how kinds of businesses run. Ask for three bands and make it say why.

Band A · the work is the product

The company sells this work to others. Almost everyone in operations there does it.

Band B · the work is heavy and constant

The company can't operate a week without it, at volume, with the hard condition built in.

Band C · the work is small

It exists, but as a slice of someone's job. Skip this band. It fills the list with people who did it once a month.

Here is the work I need done: "[paste your work line from step 1]" List the kinds of companies where this work is unavoidable. Group them: A. Companies that sell this work to other businesses. B. Companies that can't run a normal week without it, and where the hard part ("[the hard condition]") is built into how they operate. C. Companies where it exists but is a small part of someone's job. For each kind of company give me: - one line on why the work is hard there - the titles people doing this work use inside that kind of company, including vague ones (Specialist, Analyst, Operations, Coordinator, Generalist) - the titles at that company that sound close but do something else (sales, implementation, recruiting) Do not name any specific company yet. If a kind of company only fits under a condition, say the condition.

Turn company types into a real list for your place

Now ask for named companies in the metro. This is where Claude is weakest. It knows big, well-known firms. It may miss small ones, mix up names, or name a company that closed or moved. Treat every name as a lead to check, never a fact.

For [metro, e.g. Phoenix and the towns around it], name companies in bands A and B from your last answer. Rules: - Only companies you believe have real operations in this metro, not only a sales office. - For each: name, band, what they do in one line, and how sure you are (sure / think so / guess). - Say "guess" whenever you are not sure. A short honest list is better than a long one. - Leave out any company I'm not allowed to approach: [your client and no-go list].

Then check each one yourself: open the company's own website and careers page. Keep it only if it still exists, still does the work in this metro, and is big enough to need a person for it. Save the survivors in companies.md, one line each:

[Company] · band A/B · [what they do] · [why the work is hard there] · checked [date]

Search by company, with a wide title net and no skill words

Thin-profile people use their company's in-house title, so the title part stays wide. The skill words stay out, because thin profiles don't have them. Run one search per company or per small group of companies.

Current company: "[Company 1]" OR "[Company 2]" OR "[Company 3]" Title: payroll OR operations OR specialist OR analyst OR accountant OR "HR generalist" OR supervisor OR lead OR administrator Place: [metro and commute towns] Leave out: skills, summary words, "open to work"
  • If a company returns hundreds of people, it's a big employer. Add one work word to the title part ("payroll", "pay") for that company only.
  • If it returns nobody, try the company's older or parent name. Profiles often keep the name from the year the person joined.
  • Run the past-company version too: people who left a band A company in the last few years carry the same work to their next job.

Read the thin profile with these rules

You have title, company, dates and maybe one older job. Each rule below turns those facts into a reading. Write every reading as a guess to check, never as a fact about the person.

If the profile showsRead it asThen
A vague title (Specialist, Operations, Analyst) at a band A companyThey most likely do the company's core work. "Operations" at a payroll firm is processing payrolls.Keep
A title that names the work at a band B companyThey do the work at volume, with the hard condition built in.Keep
3+ years at one company with a title changePromoted inside. Somebody trusted them with more.Keep, rank up
A senior title at a small companyHands-on. They likely do the work themselves.Keep
A senior title at a very large companyMay manage people who do the work. Ask what they still do by hand.Ask
Sales, account, recruiting or marketing title at a band A companyRight company, wrong side. They sell the work.Skip
Implementation or support title at a company that makes software for the workKnows the rules and the setup. May never have run a live payday.Ask
A consultancy or outsourcing firm as the employerThe work happens at clients. You can't tell which work.Ask
A parent or group name ("[Name] Holdings", "[Name] Group")Find which business inside the group they work in before you read anything.Check
Current job started many years ago, nothing else filled inThe profile may be stale. They may have left.Check
Company bought or renamed since they joinedTitle and company may be the old ones. Search the new name too.Check

Write the first line from the company

The profile gives you nothing to quote, so don't pretend it does. Open with the company's work, and put your one guess as a question. People with quiet profiles reply when the message shows you understand their job without flattering them.

[Name], your team at [Company] [does the work] for [whom]. My guess is that means [the hard condition] most weeks. Is that your day too? I'm hiring a [role] for [company or type] where that is the whole job, with [one thing they'd gain]. Worth a short reply either way?
  • One guess only. Two guesses read like a script.
  • If the guess comes from a rule marked Ask above, the question is the guess. Don't state it.
  • Never name another employee or a client of their company.

The skill file

Save this as SKILL.md in a folder called thin-profile-finder, and add it to Claude as a skill. Keep companies.md next to it so the list grows with each role.

--- name: thin-profile-finder description: Finds people with thin profiles (title, company, dates, little else) by starting from the work their company does. Use when a role is hard to fill by keywords, or when the user asks for "quiet" or "hidden" people. --- # Thin-profile finder ## Inputs - The role: a job post or a few lines from the user. - The place: metro plus commute towns, or remote. - companies.md, if it exists (companies already checked). - No-go list: clients and companies we can't approach. ## Step 1. The work line Write one line: [verb] [what] for [whom], under [the hard condition]. No skills lists, no adjectives. Show it to the user and stop if they change it. ## Step 2. Company types List kinds of companies in three bands: - A: they sell this work to others. - B: they can't run a normal week without it, and the hard condition is built in. - C: it is a small part of someone's job. Name band C, then drop it. For A and B: why the work is hard there, the in-house titles people use (include vague ones), and the titles that sound close but sell, implement or recruit. ## Step 3. Named companies Name companies in A and B for the place. Mark each sure / think so / guess. Never present a guess as a fact. Remove anything on the no-go list. Tell the user to check every company on its own website before searching. Add checked companies to companies.md. ## Step 4. The search Company list + wide title net + place. No skill words. - Too many results at one company: add one work word to the title for that company only. - None: try the company's older or parent name. - Also run past employees of band A companies who left in recent years. If you cannot run a people search, write the search for the user to run, and ask them to paste the profiles back. ## Step 5. The reading For each person, use only title, company, dates and any older jobs. - Vague title at band A: likely does the core work. Keep. - Work-named title at band B: keep. - 3+ years with a title change: promoted inside. Rank up. - Senior title, small company: hands-on. Keep. - Senior title, very large company: ask what they still do by hand. - Sales, account, recruiting or marketing at band A: skip. - Implementation or support at a company that makes software for the work: ask. - Consultancy or outsourcing employer: ask. - Group or parent name: find the business first. - Old start date, empty profile: may be stale. Check. - Company bought or renamed: search both names. ## Output One block per person, best first: Name · title · company · start year Known: only what is on the profile. Read: what the company's work suggests, marked as a guess. Ask: the one question that confirms or kills the guess. Grade: Keep / Ask / Skip, with the rule that decided it. Then a list of the people you skipped, one line each, with the rule. ## Never - Never invent a company, a person or a fact. - Never write a guess as if it were on the profile. - Never contact anyone or reveal contact details without the user saying yes.
100+ recruiters have shared their feedback
“pretty good … especially for semiconductor, because it's much harder to find semiconductor talent”
Chat: search quality pretty good, especially for semiconductor talent

The wall

Claude can think, but it can't see people. Plain Claude has no profiles. It can write the work line, the company types and the search. Then you run every search yourself, open each profile, and paste it back in.

And this skill has its own wall. Claude's company knowledge is old and patchy, and thinnest on small local firms, which is where many quiet people work. Every company it names has to be checked by hand, and it can't tell you whether a three-line profile is current.

The same search, two ways

Plain Claude, by hand

  1. Write the work line and get the company types from Claude.
  2. Get named companies, then check each one on its own website.
  3. Build one search per company group and run each yourself.
  4. Run the past-employee version for band A companies.
  5. Open every thin profile and paste it into Claude to read.
  6. Sort Keep, Ask and Skip by hand, and keep companies.md current.
  7. Find each email and write each first line yourself.

Same job in The Cognitive

  1. Add The Cognitive as a connector in Claude: https://app.thecognitive.io/mcp. Make a free account, sign in on the Connect page and allow it.
  2. Keep this skill. Claude writes the work line, then runs the search in The Cognitive as one or two plain sentences: the role, the place, and what they must have done.
  3. People come back ranked by fit, including people with other titles. Every card says why the person fits, with a quote from their profile.
  4. Claude asks before anything that spends credits or contacts someone.
100+ recruiters have shared their feedback
“My front runner is … The Cognitive … Yours really beat JuiceBox, PIN, and Metaview”
LinkedIn message: my front runner is The Cognitive.ai; it really beat JuiceBox, PIN, Metaview and Fabric

Run the torch on the whole market

Make a free account and add the connector. Claude keeps the skill and writes the work line. The Cognitive runs the search and brings back people with other titles, each with the reason they fit.

7-day free trial, 50 sourcing credits, no card.