linkedin-search
Skill6 starsChanged 22 days agoMITView on GitHub
Use this skill whenever the user wants to search for jobs in any location or market, find job listings, or look up a specific job posting - in any country, city, or remotely. Invoke for open positions, vacancies, and hiring across any sector or role (software, data, design, marketing, finance, legal, operations, etc.). The location is always supplied explicitly by the user. Trigger phrases: find a job, job search, search for jobs, job openings, vacancies, hiring, positions open, remote jobs, "are there any X jobs in <place>", look up this job posting.
8 other projects use a version of this, 6 of them edited.
Adopted by
Most recently taken up by
- Mateus-Nogueira-GT/ai-job-search-brasiledited, first seen Nov 16, 2026
- MadsLorentzen/ai-job-searchedited, first seen Nov 9, 2026
- eggs-gd/career-spacetheir own version, first seen Nov 8, 2026
- ai-job-search-dev/ai-job-searchedited, first seen Oct 25, 2026
- syftdata/linkedin-claude-plugintheir own version, first seen Sep 25, 2026
- JiemsLBJ/offer-harvesteredited, first seen Sep 5, 2026
Used with
Projects with it also use jobbank-search, jobdanmark-search and 2 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
mikkelkrogsholmSkilljobbank-search
Make sure to use this skill whenever the user mentions anything related to job searching on Akademikernes Jobbank, jobbank.dk, or looking for academic or highly educated positions in Denmark — even if they don't mention jobbank.dk explicitly. Also invoke this skill for questions about Danish job listings, graduate trainee positions, Ph.d. jobs, or finding work in specific industries or regions in Denmark. Trigger phrases include: jobbank, akademikernes jobbank, jobs denmark, academic jobs denmark, find job denmark, highly educated jobs, graduate job denmark, trainee position denmark, ph.d. position denmark, postdoc denmark, studiejob, fuldtidsjob, deltidsjob, vikariat, freelance job, praktikplads, job søgning, jobsøgning, søg job, ledige stillinger, nye jobs, it jobs denmark, engineering jobs denmark, marketing jobs denmark, finance jobs denmark, healthcare jobs denmark, remote job denmark, fjernarbejde, job københavn, job aarhus, job odense, nyuddannede job, job til nyuddannede, international job denmark, jobbank søgning, find stilling, data scientist job, software developer job, projektleder stilling, konsulent job, data analyse job.
Also in 3 projects that use this
mikkelkrogsholmSkilljobdanmark-search
Make sure to use this skill whenever the user mentions anything related to Danish job listings, job search in Denmark, finding work in Denmark, or job vacancies on Jobdanmark — even if they don't explicitly mention jobdanmark.dk. Also invoke this skill for questions about specific Danish job categories, municipalities, job types, or salaries in a job-search context. Trigger phrases include: danish jobs, jobs in denmark, find job denmark, job search denmark, danish job listings, jobdanmark, job opslag, find job, jobsøgning, ledige stillinger, stillingsopslag, job i Danmark, fuldtidsjob, deltidsjob, studiejob, praktikplads, elev, fleksjob, IT job denmark, sygeplejersker job, håndværker job, ingeniør job, pædagog job, kontor job, leder job, salg job, hotel job, kirke job, job aarhus, job københavn, job odense, job aalborg, job sjælland, job jylland, job fyn, jobkategorier denmark, ledige job, ansøgningsfrist, søg job, job opslaget, jobopslag, danish vacancies, work in denmark, employment denmark, job denmark, jobs near me denmark, apprentice denmark, internship denmark, part-time denmark, full-time denmark.
Also in 3 projects that use this
- +2 more from mikkelkrogsholm
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 6
- ai-job-search-dev/ai-job-search★ 72k94% same
- MadsLorentzen/ai-job-search★ 72k94% same
- JiemsLBJ/offer-harvester★ 496% same
- Mateus-Nogueira-GT/ai-job-search-brasil★ 296% same
- arafat1023/job-application-assistant★ 096% same
- fn-jakubkarp/crocthejob★ 094% same
Wrote their own version · 2
- eggs-gd/career-space★ 4same name
- syftdata/linkedin-claude-plugin★ 4same 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 repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- profile.example/CLAUDE.mdCLAUDE.md
- tests/CLAUDE.mdCLAUDE.md
- tools/CLAUDE.mdCLAUDE.md
- freehire-searchSkill
- appSkill
- job-application-assistantSkill
- scrapeSkill
- networkingSkill
- upskillSkill
The file
We split this skill into the rules it gives an agent
4 rules. 2 are common, 0 are distinctive, and 2 are very specific to this project.
2
Common
Most of the 8 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
Search live job listings from LinkedIn's public job board for any country/region (and remote).
- Common: line 33
Run it on your own responsibility.
- Common: line 43
Search for job openings in a given location (any country/city) or remotely
- Very specific: line 104
All errors are written to stderr as { "error": "...", "code": "..." } and the process exits with code 1.
“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
LinkedIn Search Skill
Search live job listings from LinkedIn's public job board for any country/region
(and remote). No authentication, no API key, and zero runtime dependencies - it runs
with just bun. The location is always passed explicitly, so the same skill works for a
forker in any market out of the box.
This is a country-agnostic worked example of the repo's job-portal-skill pattern. LinkedIn's
jobs-guestendpoints are global and the HTML parsing is country-independent; only the--locationyou pass changes per market.
⚠️ Personal use only
This uses LinkedIn's public job pages; automated access is against LinkedIn's Terms of Service, so keep volume low and don't use it commercially or for bulk data collection. Run it on your own responsibility.
It ships on, and the person should know what that means. LinkedIn's robots.txt
disallows these endpoints for crawlers it does not name, and a tools/run_round.py round
sends a portal thousands of requests. It is on because it is where most postings are; a
person who would rather not turns it off in profile/search.py PORTALS
(tools/portals.py has the detail).
When to use this skill
- Search for job openings in a given location (any country/city) or remotely
- Filter by recency (posted today / last 7 / 14 / 30 days) or workplace type (remote/hybrid/onsite)
- Get the full description of a specific job listing
Commands
Search job listings
bun run .agents/skills/linkedin-search/cli/src/cli.ts search --location "<place>" [flags]Key flags:
--location <text>/-l <text>- required. A LinkedIn place string, e.g."Mumbai, Maharashtra, India","Berlin, Germany","London, United Kingdom", or"Remote".--query <text>/-q <text>- keyword search (title, skill, role). Recommended.--jobage <days>- posted within N days:1,7,14,30. Omit for all postings.--jobage-minutes <n>- posted within N minutes (sub-day precision, e.g.30). Conflicts with--jobage- pass only one.--remote <mode>-remote,hybrid, oronsite(workplace-type filter).--page <n>- page number (1-indexed, 10 results per page).--limit <n>/-n <n>- cap total results emitted (client-side).--format json|table|plain- defaultjson.
Fetch full job detail
bun run .agents/skills/linkedin-search/cli/src/cli.ts detail <id|url> [--format json|plain]id is the job ID from search results (e.g. 4426311357). You may also pass a full
LinkedIn jobs/view/... URL or a urn:li:jobPosting:... URN. Returns the full description,
seniority, employment type, job function, and industries. The JSON also carries
descriptionHtml, the description as the page marks it up, so the round can take out what the
page hides from a reader (tools/hydrate.py).
Usage examples
# Data engineer roles in Bengaluru, last 30 days
bun run .agents/skills/linkedin-search/cli/src/cli.ts search -q "data engineer" -l "Bengaluru, Karnataka, India" --jobage 30 --format table
# Product manager roles in Berlin, remote
bun run .agents/skills/linkedin-search/cli/src/cli.ts search -q "product manager" -l "Berlin, Germany" --remote remote --format table
# Any role, fully remote
bun run .agents/skills/linkedin-search/cli/src/cli.ts search -q "paralegal" -l "Remote" --format table
# Engineer roles, remote, posted in the last 30 minutes
bun run .agents/skills/linkedin-search/cli/src/cli.ts search -q "engineer" -l "Remote" --jobage-minutes 30 --format table
# Full details for a specific job
bun run .agents/skills/linkedin-search/cli/src/cli.ts detail 4426311357 --format plainOutput formats
| Format | Best for |
json | Default - programmatic use, passing IDs to detail |
table | Quick human-readable scanning |
plain | Reading a single job's full detail (detail command) |
All errors are written to stderr as { "error": "...", "code": "..." } and the process exits with code 1.
Notes
- Data is from LinkedIn's public
jobs-guestendpoints - no credentials required. - Page size is fixed at 10 results per page.
- LinkedIn may rate-limit; the CLI retries 429/5xx with exponential backoff. Keep volume low (see ToS note above).
- Job IDs are numeric (e.g.
4426311357) - pass them as-is todetail.
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.

