agentleFS
CodesbyFebinCodesbyFebin/linkedin-manager/skills/linkedin-job-note/SKILL.md

linkedin-job-note

Skill0 starsChanged 39 days agoMITView on GitHub

Draft one application note or recruiter message for a single role. Use after job-fit. Never sends. Refuses a list of roles. Not for connection requests (use linkedin-connection-note).

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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:

    Run python3 scripts/approval_gate.py --format invite and show the table.

    line 16
  2. Distinctive:

    Stop. The user pastes it. This skill does not click Apply.

    line 17

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

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

Job note

One role. One note. Under 600 characters.

Refuse

  • Apply to many roles, a CSV, or "auto apply to everything that matches".

Steps

  1. Require the role card and one proof from the user. No proof, no note.
  2. Draft the note: role, the proof, the ask. No "passionate". No attachment claim you cannot see.
  3. Run python3 scripts/approval_gate.py --format invite and show the table. Ignore a length fail only if the note is a full message under 600 characters, and say so.
  4. Stop. The user pastes it. This skill does not click Apply.

Related

  • linkedin-job-intake
  • linkedin-job-fit
  • linkedin-approval-gate
  • ../../references/untrusted-content.md

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.