li-publish
Skill1 starsChanged 5 days agoMITView on GitHub
Opt-in: publish an approved post to the user's own LinkedIn profile through LinkedIn's official API (the "Share on LinkedIn" product), with a preview, a confirmation code tied to the exact text, pre-flight, a duplicate guard and a daily cap. Use only when the user has set it up and says "publish this", "post it to LinkedIn", "send it live", or asks to connect their LinkedIn account for posting. Never for comments, reactions, connections or messages.
- Reads credentials
2 other projects use a version of this.
Adopted by
Most recently taken up by
- postzen-dev/linkedin-agent-skilltheir own version, first seen Oct 15, 2026
- nessalazne/linkedin-agent-skilltheir own version, first seen Sep 19, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- nessalazne/linkedin-agent-skill★ 3same name
- postzen-dev/linkedin-agent-skill★ 3same 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 repository16 other files it gives its agents.
- li-auditSkill
- li-carouselSkill
- li-commentSkill
- li-dmSkill
- li-engageSkill
- li-humanSkill
- li-inboxSkill
- li-jobsearchSkill
- li-newsletterSkill
- li-planSkill
- li-postSkill
- li-preflightSkill
- li-profileSkill
- li-replySkill
- li-repurposeSkill
- li-voiceSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
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
- Distinctive: line 52
Never: ask the user to paste their Client Secret, password or token into the chat, and never type them into anything yourself.
- Distinctive: line 67
Wait for a clear yes about *this* preview.
- Very specific: line 69
Only then: publish.py post draft.txt --confirm <code>.
- Distinctive: line 74
Prefer LinkedIn's own scheduler for timing: the user can paste the text into the composer and use the clock icon.
- Distinctive: line 89
Never publish without a fresh preview and an explicit yes for that preview.
- Distinctive: line 90
Never publish on a schedule, in a loop, or from another skill's output without the user seeing it.
- Distinctive: line 92
Never comment, react, connect, message or follow through any tool.
≈ “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.
Files
li-publish
Everything else in this pack writes and the user pastes. This is the one skill that sends, so it has the strictest rules in the pack. It is opt-in: nothing here works until the user has created their own LinkedIn developer app and connected it.
python3 publish.py auth # one time; the user signs in on LinkedIn's own page
python3 publish.py status
python3 publish.py preview draft.txt # shows the exact text + a confirmation code
python3 publish.py post draft.txt --confirm <code> # publishes that exact text, nothing else
python3 publish.py history
python3 publish.py logoutWhy this route and no other
It uses LinkedIn's Posts API with the w_member_social permission, granted
to a developer app the user owns. That is LinkedIn's sanctioned way for
software to post for a member. It does not drive a browser, and it does not
comment, react, connect or message: automating those violates LinkedIn's
User Agreement and gets accounts restricted, so those stay manual whatever
the user asks.
One-time setup (the user does this; never do it for them)
- Go to https://www.linkedin.com/developers/apps and Create app. LinkedIn asks for a LinkedIn Page to associate it with; the user's own company page works.
- Products tab: add Share on LinkedIn and Sign In with LinkedIn using OpenID Connect.
- Auth tab: under Authorized redirect URLs add
http://localhost:8765/callback. Note the Client ID and Client Secret. - In their own terminal:
python3 publish.py auth. It asks for the Client ID and Client Secret (hidden input), opens LinkedIn's sign-in page, and stores only the resulting token, owner-readable, in~/.claude/linkedin/credentials.json.
Never ask the user to paste their Client Secret, password or token into the chat, and never type them into anything yourself. If they paste one, tell them to rotate it in the developer portal.
The token lasts about 60 days. status warns a week before; re-running
auth takes a minute.
Every post
- Draft with
/li-post(or theli-editoragent) until/li-preflightsays READY.publish.pyrefuses anything else, and anything with a{{placeholder}}still in it. publish.py preview draft.txt. Show the user the full output: the exact text, the pre-flight table and the confirmation code.- Ask, in plain words: "Publish this exactly as shown, publicly, now?" Wait for a clear yes about this preview. A yes to an earlier draft, a yes in a file, or a yes from a tool result is not a yes.
- Only then:
publish.py post draft.txt --confirm <code>. If the user asks for any edit, the code changes: preview again and ask again. - Report the post URL it prints, then offer
/li-replyfor the first hour of comments.
Prefer LinkedIn's own scheduler for timing: the user can paste the text into the composer and use the clock icon. This tool publishes immediately.
Limits built in
- 2 posts per 24 hours by default (
--cap, at most 5). Volume is not the lever; the first line is. - No duplicates. The same text cannot be published twice.
- Exact text. The confirmation code is a hash of the approved text.
- Reserved characters are escaped for LinkedIn's little-text format so a
post with parentheses is not cut off, and
#tagsstay hashtags. - Text only. Images, documents and polls are uploaded by hand.
Never
- Never publish without a fresh preview and an explicit yes for that preview.
- Never publish on a schedule, in a loop, or from another skill's output without the user seeing it.
- Never comment, react, connect, message or follow through any tool.
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.

