linkedin-search
Skill4 starsChanged 2 months agoApache-2.0View on GitHub
Generate ready-to-click LinkedIn Boolean search links (job board, feed posts, people search) from data/sources.yaml's tracks — no fetching or scraping, just deep-links the candidate opens themselves. Use when the candidate wants LinkedIn covered on top of the scout's ATS/board feeds ("linkedin search links", "знайди мене на linkedin").
8 other projects use a version of this.
Adopted by
Most recently taken up by
- Mateus-Nogueira-GT/ai-job-search-brasiltheir own version, first seen Nov 16, 2026
- MadsLorentzen/ai-job-searchtheir own version, first seen Nov 9, 2026
- ai-job-search-dev/ai-job-searchtheir own version, first seen Oct 25, 2026
- aranculleton/last-job-searchtheir own version, first seen Oct 17, 2026
- syftdata/linkedin-claude-plugintheir own version, first seen Sep 25, 2026
- JiemsLBJ/offer-harvestertheir own version, first seen Sep 5, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- ai-job-search-dev/ai-job-search★ 72ksame name
- MadsLorentzen/ai-job-search★ 72ksame name
- aranculleton/last-job-search★ 6same name
- JiemsLBJ/offer-harvester★ 4same name
- syftdata/linkedin-claude-plugin★ 4same name
- Mateus-Nogueira-GT/ai-job-search-brasil★ 2same name
- arafat1023/job-application-assistant★ 0same name
- fn-jakubkarp/crocthejob★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/agents.mdcCursor rule
- add-from-urlSkill
- boardSkill
- communication-logSkill
- cover-letterSkill
- cv-reviewSkill
- cv-targetedSkill
- cv-universalSkill
- engagement-fitmentSkill
- fitmentSkill
- interview-prepSkill
- onboardSkill
- pitchSkill
- prioritizeSkill
- reconcileSkill
- scoutSkill
- surface-defineSkill
- update-surfaceSkill
- workspace-validateSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 6
Read and follow playbooks/linkedin-search.md in full.
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Read and follow playbooks/linkedin-search.md in full. It is the single source of truth for
this skill — don't duplicate its instructions here, don't skip steps because they seem implied.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

