Menu

Individual skill

lookalike-candidate-sourcing

0upvotes

Use this skill when a role worked and you want more of that person, or when you are backfilling someone strong and a job-board post is not going to find them. Takes one exemplar profile and returns a ranked, scored shortlist with the reasoning behind each score visible.

skills/amir-baldiga/lookalike-candidate-sourcing/SKILL.md

Read pinned source

Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
237
Repository last updated
Oct 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

Use this when one hire worked and you want more like them. It produces a ranked shortlist where every score decomposes into title, skills, seniority, and location, so a hiring manager can argue with it.

## The play

1. **Take one exemplar, not a job description.** A JD describes what someone wrote down. A person who is actually good in the role describes what worked. Start from the exemplar's real current title, skills, and location.

2. **Push filters into the search, not into post-processing.** Role family, country, city, and current-role-only belong in the query. Filtering a large result set client-side wastes lookups and hides how narrow you actually were.

3. **Start broad, then tighten once.** Role family plus two skills plus a country is a good opening net. Stacking an exact title, an all-skills-match, and a city returns zero and looks like "nobody exists" when it is really a bad query.

4. **Decide whether to enrich.** Without enrichment you get a cheap keyword-ordered list. With it you get skills, education, and geography per candidate, at one extra lookup each. Enrich 20, not 200, until the shortlist direction is confirmed.

5. **Score transparently out of 100:**
   - **Title match, 40** — exact title 40, same role family at any seniority 25, different family 0.
Back to top