agentleFS
mayankasthanamayankasthana/applymate/.agents/skills/find-jobs/SKILL.md

find-jobs

Skill1 starsChanged 47 days agoMITView on GitHub

Find job postings relevant to the candidate's dossier and preferences, score them, and present a shortlist for approval.

11 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use apply-to-job and interview-prep.

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.
  • mukewlSkill

    apply-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

  • AnthropicSkill

    interview-prep

    Create structured interview plans with competency-based questions and scorecards. Trigger with "interview plan for", "interview questions for", "how should we interview", "scorecard for", or when the user is preparing to interview candidates.

    Also in 3 projects that use this

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 11 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
  1. Very specific:

    Discover in the browser when the harness has one: Before browsing a site, read its recipe in docs/portal-recipes/ (AGENTS.md "Browser …

    line 12

“Common” is measured: kept by at least 6 in 10 of the 11 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Find relevant jobs

  1. Load the candidate's filters: node bin/applymate.ts prefs list. If companyType, salaryFloor, workMode, locations, or seniority are missing, ask before searching. Respect them strictly — e.g. skip service-based shops when the candidate prefers product-based companies.
  2. Discover in the browser when the harness has one. Before browsing a site, read its recipe in docs/portal-recipes/ (AGENTS.md "Browser recipes" rule) — and when a browsing difficulty gets solved, write the recipe back there and commit. Search job boards and company career pages with the browser tools: official search boxes and filters, unhurried, page by page — never bulk scraping or parallel crawls. Capture each promising JD's full text. Without browser tools, work from postings you are given. For each: node bin/applymate.ts job add --company ... --title ... --file jd.md --url <posting url>.
  3. Evidence before moving on — postings vanish: screenshot the posting page (harness browser tools save PNG) and file it: node bin/applymate.ts job evidence <jobId> shot.png --kind jd-screenshot --url <posting url>. For tricky pages also save print-to-PDF/HTML with --kind jd-snapshot.
  4. Score every posting: node bin/applymate.ts job match <jobId>. The toolbelt refuses applications below config minMatchScore; report the gate, do not route around it.
  5. Shortlist in chat (chat reply): company — title — score/grade — one-line "why it fits" — notable missing skills. Let the candidate choose; only then run node bin/applymate.ts app start <jobId>.

$ARGUMENTS

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.