linkedin-cli — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited linkedin-cli (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
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.
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:
npm install -g @linkedapi/linkedin-cliIf a command fails with exit code 2 (authentication error), ask the user to set up their account:
Once the user provides the tokens, run:
linkedin setup --linked-api-token=TOKEN --identification-token=TOKENUse this skill when you need to orchestrate LinkedIn actions from scripts or an AI agent instead of clicking through the web UI:
Always respect LinkedIn’s terms of service, local regulations, and your organisation’s compliance policies when using automation against real accounts.
Always use --json and -q for machine-readable output:
linkedin <command> --json -q| 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 |
Success:
{ "success": true, "data": { "name": "John Doe", "headline": "Engineer" } }Error:
{
"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) |
linkedin person fetch <url> [flags] --json -qOptional 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.
# 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 -qlinkedin person search [flags] --json -q| Flag | Description
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.