⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
General-purpose LinkedIn automation – fetch profiles, search people and companies, send messages, manage connections, create posts, and more. Use when the user wants to interact with LinkedIn.
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
Not yet listed on ClawHub or SkillsMP
// README
linkedin-skills
A collection of LinkedIn skills for AI agents (Claude Code, Codex, Cursor, Windsurf), powered by
LinkedIn CLI (@linkedapi/linkedin-cli) and
Linked API.
Install
One command — detects your installed agents, asks what to install and where, and sets up the prerequisites for you:
npx @linkedapi/skills
Or just hand this to your AI agent:
Read https://linkedapi.io/skills/install.md and follow it.
For a single skill, hand over its own runbook instead — e.g.
https://linkedapi.io/skills/linkedin/install.md or
https://linkedapi.io/skills/linkedin-growth/install.md.
Non-interactive (agents / CI)
# Inspect the environment first (machine-readable)
npx @linkedapi/skills detect --json
# Install one skill in one command
npx @linkedapi/skills add linkedin --yes
# Install specific skills into specific agents
npx @linkedapi/skills add linkedin linkedin-growth \
--agent claude-code --agent codex --scope project --yes --json
Other commands: list, update, remove, doctor (all support --json). See
npx @linkedapi/skills --help.
Exit codes & readiness
add separates two things so a caller never mistakes "needs setup" for "install failed"
(the agent-facing install runbook at linkedapi.io/skills/install.md spells this out for AI agents):
- Exit code reflects only whether the install itself succeeded (files placed +
dependencies installed).
0= installed.1= a real install failure.2= bad arguments. - Readiness is reported in the JSON, not the exit code. Each skill carries
ok(installed) andready(fully configured and usable now). When a skill installed fine but still needs setup — e.g. LinkedIn tokens not connected yet — you get exit 0 withready: falseand apendinglist describing what's left. Always parse the JSON; do not treat a readiness gap as a failure.
{ "success": true,
"data": {
"ready": false,
"pending": [{ "skill": "linkedin-growth", "pending": [{ "name": "db-accounts", "message": "0 accounts in DB — register each linkedin-cli account…" }] }],
"installed": [{ "skill": "linkedin-growth", "ok": true, "ready": false }]
} }
Available skills
| Skill | Description |
|---|---|
| General-purpose LinkedIn automation – fetch profiles, search people and companies, send messages, manage connections, create posts, and more | |
| linkedin-growth | Two-phase lead pipeline – import + qualify leads against your ICP, then send connection invites on a schedule across one or more accounts |
Prerequisites
The installer checks these for you and offers to set them up:
- Node.js ≥ 20
@linkedapi/linkedin-cli(npm install -g @linkedapi/linkedin-cli)- Linked API tokens — get them at app.linkedapi.io, then
linkedin setup(the installer can run this for you).
Manual install (fallback)
Copy the skill folder into your agent's skills directory, e.g. .claude/skills/<skill>/
(project) or ~/.claude/skills/<skill>/ (global). For linkedin-growth, also run
npm install --omit=dev and node scripts/doctor.mjs inside the copied folder.
License
This project is licensed under the MIT – see the LICENSE file for details.
// HOW IT'S BUILT
// FILES
2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.
linkedin/SKILL.md7.8 KBupstream ↗
--- name: linkedin description: General-purpose LinkedIn automation – fetch profiles, search people and companies, send messages, manage connections, create posts, and more. Use when the user wants to interact with LinkedIn. --- # 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 ``` ## Global Flags Always use `--json` and `-q` for machine-readable output: ```bash LINKEDAPI_CLIENT=skill:linkedin linkedin <command> --json -q ``` When using this skill, run every `linkedin ...` example below with the `LINKEDAPI_CLIENT=skill:linkedin` prefix so Linked API can attribute usage to the skill. | Flag | Description | |------|-------------| | `--json` | Structured JSON output | | `--quiet` / `-q` | Suppress stderr progress messages | | `--fields name,url,...` | Select specific fields in output | | `--no-color` | Disable colors | | `--account "Name"` | Use a specific account for this command | ## Output Format Success: ```json {"success": true, "data": {"name": "John Doe", "headline": "Engineer"}} ``` Error: ```json {"success": false, "error": {"type": "personNotFound", "message": "Person not found"}} ``` Exit code 0 means the API call succeeded – always check the `success` field for the action outcome. Non-zero exit codes indicate infrastructure errors: | Exit Code | Meaning | |-----------|---------| | 0 | Success (check `success` field – action may have returned an error like "person not found") | | 1 | General/unexpected error | | 2 | Missing or invalid tokens | | 3 | Subscription/plan required | | 4 | LinkedIn account issue | | 5 | Invalid arguments | | 6 | Rate limited | | 7 | Network error | | 8 | Workflow timeout (workflowId returned for recovery) | ## Commands ### Fetch a Person Profile ```bash linkedin person fetch <url> [flags] --json -q ``` Optional flags to include additional data: - `--experience` – work history - `--education` – education history - `--skills` – skills list - `--languages` – languages - `--posts` – recent posts (with `--posts-limit N`, `--posts-since TIMESTAMP`) - `--comments` – recent comments (with `--comments-limit N`, `--comments-since TIMESTAMP`) - `--reactions` – recent reactions (with `--reactions-limit N`, `--reactions-since TIMESTAMP`) Only request additional data when needed – each flag increases execution time. ```bash # 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 ``` ### Search People ```bash linkedin person search [flags] --json -q ``` | Flag | Description | |------|-------------| | `--term` | Search keyword or phrase | | `--limit` | Max results | | `--first-name` | Filter by first name | | `--last-name` | Filter by last name | | `--position` | Filter by job position | | `--locations` | Comma-separated locations | | `--industries` | Comma-separated industries | | `--current-companies` | Comma-separated current company names | | `--previous-companies` | Comma-separated previous company names | | `--schools` | Comma-separated school names | | `--connection-degrees` | Comma-separated connection degrees: `1st`, `2nd`, `3rd+` | ```bash linkedin person search --term "product manager" --locations "San Francisco" --json -q linkedin person search --current-companies "Google" --position "Engineer" --limit 20 --json -q ``` ### Fetch a Company ```bash linkedin company fetch <url> [flags] --json -q ``` Optional flags: - `--employees` – include employees - `--dms` – include decision makers - `--posts` – include company posts Employee filters (require `--employees`): | Flag | Description | |------|-------------| | `--employees-limit` | Max employees to retrieve | | `--employees-first-name` | Filter by first name | | `--employees-last-name` | Filter by last name | | `--employees-position` | Filter by position | | `--employees-locations` | Comma-separated locations | | `--employees-industries` | Comma-separated industries | | `--employees-schools` | Comma-separated school names | | `--employees-connection-degrees` | Comma-separated connection degrees: `1st`, `2nd`, `3rd+` | | Flag | Description | |------|-------------| | `--dms-limit` | Max decision makers to retrieve (requires `--dms`) | | `--posts-limit` | Max posts to retrieve (requires `--posts`) | | `--posts-since` | Posts since ISO timestamp (requires `--posts`) | ```bash # Basic company info linkedin company fetch https://www.linkedin.com/company/name --json -q # With employees filtered by position linkedin company fetch https://www.linkedin.com/company/name --employees --employees-position "Engineer" --json -q # With decision makers and posts linkedin company fetch https://www.linkedin.com/company/name --dms --posts --posts-limit 10 --json -q ``` ### Search Companies ```bash linkedin company search [flags] --json -q ``` | Flag | Description | |------|-------------| | `--term` | Search keyword | | `--limit` | Max results | | `--sizes` | Comma-separated sizes: `1-10`, `11-50`, `51-200`, `201-500`, `501-1000`, `1001-5000`, `5001-10000`, `10001+` | | `--locations` | Comma-separated locations | | `--industries` | Comma-separated industries | ```bash linkedin company search --term "fintech" --sizes "11-50,51-200" --json -q ``` ### Send a Message ```bash linkedin message send <person-url> '<text>' --json -q ``` Text up to 1900 characters. Wrap the message in single quotes to avoid shell interpretation issues. ```bash linkedin message send https://www.linkedin.com/in/username 'Hey, loved your latest post!' --json -q ``` ### Get Conversation ```bash linkedin message get <person-url> [--since TIMESTAMP] --json -q ``` The first call for a conversation triggers a background sync and may take longer. Subsequent calls are faster. ```bash linkedin message get https://www.linkedin.com/in/username --json -q linkedin message get https://www.linkedin.com/in/username --since 2024-01-15T10:30:00Z --json -q ``` ### Connection Management #### Check connection status ```bash linkedin connection status <url> --json -q ``` #### Send connection request ```bash linkedin connection send <url> [--note 'text'] [--email [email protected]] --json -q ``` #### List connections ```bash linkedin connection list [flags] --json -q ``` | Flag | Description | |------|-------------| | `--limit` | Max connections to return | | `--since` | Only connections made since ISO timestamp (only works when no filter flags are used) | | `--first-name` | Filter by first name | | `--last-name` | Filter by last name | | `--position` | Filter by job position | | `--locations` | Comma-separated locations | | `--industries` | Comma-separated industries | | `--current-companies` | Comma-separated current company names | | `--previous-companies` | Comma-separated previous company names | | `--schools` | Comma-separated school names | ```bash linkedin connection list --limit 50 --json -q linkedin connection list --current-companies "GoREADME.mdupstream ↗
Contents are not inlined in the catalog. Open the upstream file.
Plain-text copy, no login: /skill-bundles/linked-api-linkedin-skills-linkedin.md