Agent skill

linkedin-cli

Use when automating LinkedIn via CLI: fetch profiles, search people/companies, send messages, manage connections, create posts, and Sales Navigator.

Nick44,086★ · +407/wk · 1 repos on radarProfile →
claude-codecodexcursorMIT
Install
npx skills add sickn33/agentic-awesome-skills --skill linkedin-cli --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 22 KB
Bundled scripts: none
Path: skills/linkedin-cli/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 44,414 · +328 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

Review
written from the skill's own SKILL.md · Aug 5, 2026

What it does

The skill enables automation of LinkedIn tasks using a CLI tool called linkedin. It supports fetching person and company profiles, searching people and companies, sending messages, managing connections, creating and interacting with posts, and using Sales Navigator features. All operations route through the Linked API via a cloud browser, and results can be output in JSON using --json -q. It includes commands to fetch profiles, search, send messages, manage connections, post creation, reactions, comments, and Sales Navigator access.

How it works

  • Use the linkedin command for various actions (person fetch, person search, company fetch, company search, message send, connection status/send/list, post fetch/create/react/comment, stats, navigator actions).
  • Each command is executed with flags and outputs JSON when using --json -q.
  • If authentication fails with exit code 2, users are prompted to set up accounts and tokens via app.linkedapi.io, then run linkedin setup --linked-api-token=TOKEN --identification-token=TOKEN.
  • Global flags require --json and -q for machine-readable output. Output includes a structured JSON with success, data, or error fields.
  • Operations may take 30 seconds to minutes depending on complexity as they rely on a real cloud browser.
  • Usage examples are provided for basic and advanced scenarios, including fetching profiles with extras, searching with filters, and posting with attachments.

When to use it

Use this skill when you need to orchestrate LinkedIn actions from scripts or an AI agent instead of clicking through the web UI, such as building outreach, research, recruitment workflows, enriching leads, or coordinating multi-step Sales Navigator workflows where JSON output and exit codes are required.

What it can touch

  • The skill interacts with the linkedin CLI tool and expects tokens for authentication via the setup flow. It assumes access to the Linked API through the CLI and does not manipulate files other than invoking commands and parsing JSON output.

Caveats

  • Operations are subject to LinkedIn’s terms of service and applicable compliance policies when automating real accounts. Authentication failures indicate missing or invalid tokens. Exit codes 0-8 are defined to reflect success, general errors, token issues, subscription needs, account issues, invalid arguments, rate limits, network errors, and workflow timeouts.
From the SKILL.md

## When to Use Use this skill when you need to automate LinkedIn tasks such as profile fetching, connection management, or post creation via CLI, especially when integrated into automated workflows. # LinkedIn Skill You have access to `linkedin` – a CLI tool for LinkedIn automation. Use it to fetch profiles, search people and companies, send messages, manage connections, create posts, react, comment, and more. Each command sends a request to Linked API, which runs a real cloud browser to perform the action on LinkedIn. Operations are **not instant** – expect 30 seconds to several minutes depending on complexity. If `linkedin` is not available, install it: ```bash npm install -g @linkedapi/linkedin-cli ``` ## Authentication If a command fails with exit code 2 (authentication error), ask the user to set up their account: 1. Go to [app.linkedapi.io](https://app.linkedapi.io) and sign up or log in 2. Connect their LinkedIn account 3. Copy the **Linked API Token** and **Identification Token** from the dashboard Once the user provides the tokens, run: ```bash linkedin setup --linked-api-token=TOKEN --identification-token=TOKEN ``` ### When to Use Use this skill when you need to **orchest

What's inside
Steps it walks through
  1. When to Use
  2. Authentication
  3. Global Flags
  4. Output Format
  5. Commands
  6. Fetch a Person Profile
  7. Search People
  8. Fetch a Company
  9. Search Companies
  10. Send a Message
  11. Get Conversation
  12. Connection Management
  13. Posts
  14. Statistics
Commands it runs
npm install -g @linkedapi/linkedin-cli
linkedin setup --linked-api-token=TOKEN --identification-token=TOKEN
linkedin <command> --json -q
linkedin person fetch <url> [flags] --json -q
Basic profile
linkedin person fetch https://www.linkedin.com/in/username --json -q
With experience and education
linkedin person fetch https://www.linkedin.com/in/username --experience --education --json -q
With last 5 posts
linkedin person fetch https://www.linkedin.com/in/username --posts --posts-limit 5 --json -q
More from agentic-awesome-skills
All skills →
About this skill
What does the linkedin-cli skill do?

Use when automating LinkedIn via CLI: fetch profiles, search people/companies, send messages, manage connections, create posts, and Sales Navigator.

How do I install it?

Run `npx skills add sickn33/agentic-awesome-skills --skill linkedin-cli --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going