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…
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,542 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository31 other files it gives its agents.
- ai-search-visibilitySkill
- ai-sounding-post-checkerSkill
- devlog-to-linkedin-postSkill
- hot-take-risk-checkSkill
- linkedin-about-generatorSkill
- linkedin-agentSkill
- linkedin-best-time-to-postSkill
- linkedin-carousel-outlineSkill
- linkedin-character-limitsSkill
- linkedin-comment-generatorSkill
- linkedin-contrarian-takesSkill
- linkedin-engagement-rateSkill
- linkedin-follower-growthSkill
- linkedin-ghostwriter-costSkill
- linkedin-headline-analyzerSkill
- linkedin-headline-generatorSkill
- linkedin-hook-generatorSkill
- linkedin-image-sizesSkill
- linkedin-line-break-fixerSkill
- linkedin-poll-generatorSkill
- linkedin-post-analyzerSkill
- linkedin-post-generatorSkill
- linkedin-post-ideasSkill
- linkedin-post-previewSkill
- linkedin-post-rewriterSkill
- linkedin-profile-checklistSkill
- linkedin-publishSkill
- linkedin-text-formatterSkill
- linkedin-to-xSkill
- linkedin-voiceSkill
- meeting-notes-to-linkedin-postSkill
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
- Distinctive: line 8
When you add a skill, add its row to the matching table in README.md.
- Common: line 9
Do not add anything that automates the LinkedIn website or needs an API key.
- Distinctive: line 10
Write plainly. No em-dashes in new text.
≈ “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.
Files
Notes for AI agents working in this repository
- Each skill is one folder under
skills/<name>/with aSKILL.md. The folder name must equal thenamein the YAML header. Quote any header value that contains:. plugins/liftli/skillsis GENERATED. Never edit it by hand. After changing anything underskills/, runpython3 scripts/build_liftli_plugin.py, thenpython3 scripts/build_liftli_plugin.py --check.- CI also runs
claude plugin validate . --strictandclaude 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.
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.

