linkedin · acedatacloud — Claude Code skill: posts and installation
Publishes text and link posts to a personal LinkedIn feed through the Posts API. It asks for confirmation before sending.
Apache-2.0 215 installs ★ 17 updated 2026-10-25
npx skills add AceDataCloud/Skills --skill linkedin -a claude-codeWhat linkedin does
This skill gets the member identifier from the OpenID userinfo endpoint, builds the author URN, and sends a post through LinkedIn’s Posts API. A URL stays inside the post text, so LinkedIn can generate its link preview. After creation, the skill reports the post URN or resulting URL.
The workflow uses Bash with curl and jq. It needs LINKEDIN_TOKEN, the w_member_social permission, and a current LinkedIn-Version header. Without w_member_social, posting to the personal feed will fail. Company Page publishing is outside this skill.
What it helps with
- publish text to a personal LinkedIn feed
- share an article link as a LinkedIn post
- retrieve the URN of a created post
- inspect an API error after publishing
Example prompts for the agent
- Publish this text to my personal LinkedIn feed, but show it to me for confirmation first: “A short update about our API testing work.”
- Post the link
https://studio.acedata.cloudto LinkedIn and ask me to confirm the final copy before sending. - Publish this LinkedIn update and return the URL of the created post.
How to install linkedin
1Skills CLI (Vercel)
npx skills add AceDataCloud/Skills --skill linkedin -a claude-code2Manually: put the files in place
~/.claude/skills/linkedin/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/linkedin/
1Skills CLI (Vercel)
npx skills add AceDataCloud/Skills --skill linkedin -a codex2Manually: put the files in place
.agents/skills/linkedin/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add AceDataCloud/Skills --skill linkedin -a cursor2Manually: put the files in place
.cursor/skills/linkedin/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install AceDataCloud/Skills skills/linkedin2Manually: put the files in place
.github/skills/linkedin/SKILL.md1Skills CLI (Vercel)
npx skills add AceDataCloud/Skills --skill linkedin -a gemini-cli2Platform CLI
gemini skills install https://github.com/AceDataCloud/Skills --path skills/linkedinManually: put the files in place
.devin/skills/linkedin/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add AceDataCloud/Skills --skill linkedin -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about linkedin
How do I install linkedin in Claude Code?
Run npx skills add AceDataCloud/Skills --skill linkedin -a claude-code. Then check ~/.claude/skills/linkedin/SKILL.md.
What does linkedin do?
It publishes text and link posts to the user’s personal LinkedIn feed through the Posts API, then reports the created post’s identifier or URL.
What does linkedin need to publish?
It needs LINKEDIN_TOKEN, the w_member_social permission, plus curl and jq. The skill targets a member’s own feed, not company Pages.
Source text
SKILL.md · Apache-2.0
---
name: linkedin
description: Publish text / link posts to your LinkedIn personal feed via the LinkedIn Posts API. Use when the user mentions LinkedIn, sharing or posting an update to LinkedIn, or cross-posting an article / link to their LinkedIn feed.
when_to_use: |
Trigger when the user wants to publish a text or link share to their
own LinkedIn feed. Posting is public on their profile — confirm the
text (and link, if any) before publishing. Requires the
w_member_social scope (granted by the connector at install).
connections: [linkedin]
allowed_tools: [Bash]
license: Apache-2.0
metadata:
author: acedatacloud
version: "1.0"
---
Call the **LinkedIn API** with `curl + jq`. The user's bearer token is in
`$LINKEDIN_TOKEN`; every call needs `Authorization: Bearer $LINKEDIN_TOKEN`.
LinkedIn posts must be authored by the member's URN. Get the member id from the
OpenID userinfo endpoint, then build `urn:li:person:{sub}`.
```bash
SUB=$(curl -sS -H "Authorization: Bearer $LINKEDIN_TOKEN" \
"https://api.linkedin.com/v2/userinfo" | jq -r .sub)
AUTHOR="urn:li:person:$SUB"
echo "$AUTHOR"
```
Errors are JSON with `message` / `serviceErrorCode` — show them verbatim.
`401` → token expired (tokens last ~60 days), re-connect the LinkedIn connector.
## Publish a post (Posts API)
**Confirm the text with the user first.** Use the versioned Posts API; set the
`LinkedIn-Version` header to a recent `YYYYMM` (LinkedIn requires a valid recent
version — if you get `426`/version errors, bump to the current month).
```bash
jq -n --arg a "$AUTHOR" --arg t "My update text. Check out https://studio.acedata.cloud" \
'{author:$a, commentary:$t, visibility:"PUBLIC",
distribution:{feedDistribution:"MAIN_FEED", targetEntities:[], thirdPartyDistributionChannels:[]},
lifecycleState:"PUBLISHED", isReshareDisabledByAuthor:false}' \
| curl -sS -X POST "https://api.linkedin.com/rest/posts" \
-H "Authorization: Bearer $LINKEDIN_TOKEN" \
-H "Content-Type: application/json" \
-H "LinkedIn-Version: 202401" \
-H "X-Restli-Protocol-Version: 2.0.0" \
-d @- -D - -o /dev/null | tr -d '\r' | awk '/^[Xx]-[Rr]estli-[Ii]d:|^[Ll]ocation:/{print}'
```
A successful create returns `201` with the post URN in the `x-restli-id`
(or `Location`) response header — report that URN / the resulting post URL.
> Link posts: put the URL inline in `commentary` (LinkedIn auto-unfurls it).
> Rich article attachments need the assets/images API — out of scope for a
> simple text/link share; keep links inline.
## Fallback: legacy ugcPosts
If the versioned endpoint is unavailable for the app, the older
`POST https://api.linkedin.com/v2/ugcPosts` with a
`specificContent."com.linkedin.ugc.ShareContent"` body also works with
`w_member_social`. Prefer `/rest/posts` above.
## Gotchas
- **Author URN** must match the token's member (`urn:li:person:{sub}`) — you
can't post as someone else.
- `w_member_social` only allows posting to the **member's own feed**; company
Page posts need `w_organization_social` + an admin role (not in this connector).
- The `LinkedIn-Version` header is mandatory for `/rest/*`; a stale value
returns a version error — bump to the current `YYYYMM`.
## Record the output
After you successfully publish and obtain the live result URL, call the built-in
`publish_artifact` tool ONCE so the user can track this deliverable in **My Outputs**:
```
publish_artifact(kind="article", channel="linkedin", title="<title>", url="<the REAL returned URL>", status="delivered")
```
Use the real returned URL — never fabricate one. Call it once per published item,
only after delivery is confirmed; skip it (or use `status="failed"`) if publishing failed.
See `_shared/artifacts.md`.
© acedatacloud · Apache-2.0 · AceDataCloud/Skills
Similar skills
All skills for Marketing and content →linkedin by other authors comes first.