agentleFS
liftli-ailiftli-ai/linkedin-agent-skills/AGENTS.md

linkedin-agent-skills

AGENTS.md1 starsChanged 29 days agoMITView on GitHub

- Each skill is one folder under skills/<name>/ with a SKILL.md. The folder name must equal the name in the YAML header. Quote any header value that contains : . - plugins/liftli/skills is GENERATED. Never edit it by hand. After changing anything under skills/, run python3 scripts/build_liftli_plugin.py, then python3 scripts/build_liftli_plugin.py --check. - CI also runs claude plugin validate . --strict and claude plugin validate ./plugins/liftli --strict. - When you add a skill, add its row to the matching table in…

The file

We split this AGENTS.md into the rules it gives an agent

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

  • ≈1

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When you add a skill, add its row to the matching table in README.md.

    line 8
  2. Common:

    Do not add anything that automates the LinkedIn website or needs an API key.

    line 9
  3. Distinctive:

    Write plainly. No em-dashes in new text.

    line 10

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

Notes for AI agents working in this repository

  • Each skill is one folder under skills/<name>/ with a SKILL.md. The folder name must equal the name in the YAML header. Quote any header value that contains : .
  • plugins/liftli/skills is GENERATED. Never edit it by hand. After changing anything under skills/, run python3 scripts/build_liftli_plugin.py, then python3 scripts/build_liftli_plugin.py --check.
  • CI also runs claude plugin validate . --strict and claude plugin validate ./plugins/liftli --strict.
  • When you add a skill, add its row to the matching table in README.md.
  • Do not add anything that automates the LinkedIn website or needs an API key.
  • Write plainly. No em-dashes in new text.

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.