How do I install the Linkedin CLI skill?

Run npx skillmds@latest add dvcrn/linkedin-cli-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Linkedin CLI safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: CAUTION, Skill Scanner: PASS. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Linkedin CLI?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Linkedin CLI free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Linkedin CLI?

dvcrn (@dvcrn) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Linkedin CLI by dvcrn — Agent Skill

Name: Linkedin CLI
Rating: 4.666666666666667 (3 reviews)
Author: dvcrn

File contents

linkedin-cli

Post to LinkedIn using the official API v2. This tool is rate-limited by LinkedIn, so only use it when the user explicitly asks you to post, or during scheduled cron tasks. Do not speculatively draft and post content.

Setup

Install (pinned to release tag):

npm install -g github:0xmythril/linkedin-cli#v1.0.0

Create a LinkedIn app at https://www.linkedin.com/developers/apps
- Enable Sign In with LinkedIn using OpenID Connect and Share on LinkedIn products
- Add http://localhost:8585/callback to Authorized redirect URLs
Configure credentials (file is created with restricted permissions):

mkdir -p ~/.config/linkedin-cli
touch ~/.config/linkedin-cli/.env
chmod 600 ~/.config/linkedin-cli/.env
cat > ~/.config/linkedin-cli/.env << 'EOF'
LINKEDIN_CLIENT_ID=your_client_id
LINKEDIN_CLIENT_SECRET=your_client_secret
EOF

Authenticate (opens browser for OAuth):

linkedin-cli auth

Verify: linkedin-cli whoami

Security

Credentials: Stored in ~/.config/linkedin-cli/.env (read by dotenv at runtime). Set chmod 600 to restrict access.
No postinstall scripts: The package has zero install scripts — verify via npm pack --dry-run or inspect package.json.
No telemetry or network calls except to the official LinkedIn API (api.linkedin.com) and OAuth (www.linkedin.com) when you run a command.
Pinned install: The install command pins to a specific release tag. Audit the source at https://github.com/0xmythril/linkedin-cli before installing.
Dependencies: Only 3 runtime deps — commander (CLI parsing), dotenv (env file loading), open (browser launch for OAuth). No transitive dependencies beyond these.

Commands

Verify auth

linkedin-cli whoami

Authenticate

linkedin-cli auth

Post a text update

linkedin-cli post "Your post text here"

Share a URL with commentary

linkedin-cli share "https://example.com/article" "Your commentary here"

Delete a post

linkedin-cli delete <post-id-urn-or-url>
linkedin-cli delete https://www.linkedin.com/feed/update/urn:li:activity:7654321/

Important rules

Do NOT post unless the user explicitly asks or a cron job triggers it. LinkedIn rate-limits API usage.
Always confirm with the user before posting or sharing. Show them the text first.
Keep posts professional — LinkedIn is a professional network.
linkedin-cli accepts raw numeric IDs, full URNs, and LinkedIn post URLs.
If you get a 401 error, the token has expired (~60 days). Ask the user to run linkedin-cli auth to re-authenticate.
This tool is for posting only. It cannot read feeds, search profiles, or send messages.

---name: linkedin-cli-2description: Post to LinkedIn using the official API v2. Uses OAuth tokens so only post when explicitly asked or scheduled.--- # linkedin-cli Post to LinkedIn using the official API v2. This tool is rate-limited by LinkedIn, so **only use it when the user explicitly asks you to post, or during scheduled cron tasks**. Do not speculatively draft and post content. ## Setup 1. Install (pinned to release tag): ```bash npm install -g github:0xmythril/linkedin-cli#v1.0.0 ``` 2. Create a LinkedIn app at https://www.linkedin.com/developers/apps - Enable **Sign In with LinkedIn using OpenID Connect** and **Share on LinkedIn** products - Add `http://localhost:8585/callback` to **Authorized redirect URLs** 3. Configure credentials (file is created with restricted permissions): ```bash mkdir -p ~/.config/linkedin-cli touch ~/.config/linkedin-cli/.env chmod 600 ~/.config/linkedin-cli/.env cat > ~/.config/linkedin-cli/.env << 'EOF' LINKEDIN_CLIENT_ID=your_client_id LINKEDIN_CLIENT_SECRET=your_client_secret EOF ``` 4. Authenticate (opens browser for OAuth): ```bash linkedin-cli auth ``` 5. Verify: `linkedin-cli whoami` ## Security - **Credentials**: Stored in `~/.config/linkedin-cli/.env` (read by `dotenv` at runtime). Set `chmod 600` to restrict access. - **No postinstall scripts**: The package has zero install scripts — verify via `npm pack --dry-run` or inspect `package.json`. - **No telemetry or network calls** except to the official LinkedIn API (`api.linkedin.com`) and OAuth (`www.linkedin.com`) when you run a command. - **Pinned install**: The install command pins to a specific release tag. Audit the source at https://github.com/0xmythril/linkedin-cli before installing. - **Dependencies**: Only 3 runtime deps — `commander` (CLI parsing), `dotenv` (env file loading), `open` (browser launch for OAuth). No transitive dependencies beyond these. ## Commands ### Verify auth ```bash linkedin-cli whoami ``` ### Authenticate ```bash linkedin-cli auth ``` ### Post a text update ```bash linkedin-cli post "Your post text here" ``` ### Share a URL with commentary ```bash linkedin-cli share "https://example.com/article" "Your commentary here" ``` ### Delete a post ```bash linkedin-cli delete <post-id-urn-or-url> linkedin-cli delete https://www.linkedin.com/feed/update/urn:li:activity:7654321/ ``` ## Important rules - **Do NOT post unless the user explicitly asks or a cron job triggers it.** LinkedIn rate-limits API usage. - **Always confirm with the user** before posting or sharing. Show them the text first. - **Keep posts professional** — LinkedIn is a professional network. - linkedin-cli accepts raw numeric IDs, full URNs, and LinkedIn post URLs. - If you get a 401 error, the token has expired (~60 days). Ask the user to run `linkedin-cli auth` to re-authenticate. - This tool is for **posting only**. It cannot read feeds, search profiles, or send messages.

Frequently asked questions

Linkedin CLI