agentleFS
MIt9MIt9/job-search-skills/skills/linkedin/linkedin-job-search/SKILL.md

linkedin-job-search

Skill0 starsChanged 3 months agoNo licenceView on GitHub

Playbook for optimizing a LinkedIn profile and job search strategy to get found by recruiters and land interviews — based on hiring-manager/recruiter-tool insight (LinkedIn Recruiter search behavior, Open to Work mechanics, keyword strategy, search operators, Easy Apply vs. direct application, career-pivot framing, networking, and engagement cadence). Use this whenever the user wants to optimize their LinkedIn profile, headline, or summary; asks how recruiters find candidates on LinkedIn; wants help with job search filters/search operators; is pivoting careers or industries and needs to bridge the language gap on their profile; asks whether to turn on "Open to Work"; wants a LinkedIn networking or posting/engagement plan; or is generally job hunting and mentions LinkedIn, resume-to-profile alignment, or ATS/recruiter keyword matching. Trigger even if the user just pastes their current headline/summary and asks "how's this look" or "why am I not getting responses.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. carsanmilcar/job-search-template★ 1same name
    2. rubenviolinha/linkedin-job-search-skill★ 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 repository2 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

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.