find-jobs
Skill0 starsChanged 26 days agoMITView on GitHub
Find, count or look up open job postings with the Headcount Labs tools. Use when the user asks who is hiring, how many jobs match a role or place, or for job listings with apply links.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- robbiehaynes/job-searchtheir own version, first seen Oct 20, 2026
- mukewl/jobkittheir own version, first seen Oct 20, 2026
- kevinmmiddleton/recruiter-bfftheir own version, first seen Oct 17, 2026
- ClarvAI/job-search-hqtheir own version, first seen Oct 15, 2026
- khadinakbarlabs/vibejobs-plugintheir own version, first seen Oct 13, 2026
- lecegues/hitapply-plugintheir own version, first seen Oct 11, 2026
Used with
Projects with it also use apply-to-job.
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.
mukewlSkillapply-to-job
End-to-end prep for one job application - read the posting, produce a tailored page-checked CV in the user's own formatting, find 5-10 named people worth contacting at that company, and draft LinkedIn messages for the user to send by hand. Use when given a job URL or job description and asked to apply, prepare an application, tailor a CV for a role, or find who to reach out to about a job.
Also in 3 projects that use this
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- kevinmmiddleton/recruiter-bff★ 3same name
- mayankasthana/applymate★ 1same name
- mukewl/jobkit★ 1same name
- ClarvAI/job-search-hq★ 0same name
- DhruvPrajapati4/apply-kit★ 0same name
- khadinakbarlabs/vibejobs-plugin★ 0same name
- lecegues/hitapply-plugin★ 0same name
- QaliAI/ai-job-agent★ 0same name
- robbiehaynes/job-search★ 0same name
- sree-data/job-search-agent★ 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.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
If you are unsure which filter fits (pay, work arrangement, seniority, dates), call list_fields with a keyword first.
- Very specific: line 9
When the user asks how many jobs match, call count_jobs.
- Very specific: line 14
When the user wants listings, call search_jobs with the narrowest filters that fit the request and the smallest limit (10) unless they ask …
“Common” is measured: kept by at least 6 in 10 of the 10 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
Find jobs with Headcount Labs
- If you are unsure which filter fits (pay, work arrangement, seniority, dates), call
list_fieldswith a keyword first. - When the user asks how many jobs match, call
count_jobs. Counts don't use the user's monthly jobs. For a market question (what a role pays, which employers or metros have the most jobs, the remote share, jobs by state, the most common roles, new postings this week, which states show pay, how long jobs stay posted, employers hiring in the most states), callmarket_insightswhen it is listed, and give itsas_ofdate andopen_jobscount with the answer. If it returnsavailable: false, runcount_jobswith the filters it returns. - When the user wants listings, call
search_jobswith the narrowest filters that fit the request and the smallestlimit(10) unless they ask for more (up to 100 a page). - For one job's full record, call
get_jobwith itsjob_id. - In the answer, give each job's title, employer, location, pay as the employer published it (say when none is
listed), and the posting link from
postings[].posting_url, so the user can check the original and apply there. - These tools only read job data. They can't apply to jobs or contact employers. Say so if the user asks for that.
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.