Receber por email
← Voltar para o catálogo

linkedin-cli

Interacts with LinkedIn via the cli-web-linkedin command-line tool — search people/jobs/companies, view profiles and feed, create/edit/delete posts, react and comment, manage connections and invitations, read and send messages, view notifications, follow companies. Use when the user asks about LinkedIn or wants to search, post, network, or message on LinkedIn from the terminal. Prefer this CLI ove

201estrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add ItamarZand88/CLI-Anything-WEB

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/linkedin-cli-itamarzand88/svg)](https://www.skillteca.com.br/skills/linkedin-cli-itamarzand88)

Skills relacionadas

Ver todas de Pesquisa e Web →

Alerta por categoria

Receba novas skills de Pesquisa e Web toda segunda

1 email curto, só com as skills novas de Pesquisa e Web. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

cli-web-linkedin

Full LinkedIn client: search, profiles, feed, posting, reactions, comments, network, and messaging. All commands require auth login first. Install: pip install cli-web-linkedin

Commands

| Group | Commands | |-------|----------| | search | all\|people\|jobs\|companies QUERY [--limit N] (default 10) | | profile | me, get USERNAME | | feed | feed [--count N] | | company | company NAME (view page), company follow\|unfollow COMPANY_URN | | jobs | search QUERY [--limit N], get JOB_ID (full description) | | post | create TEXT, edit POST_URN TEXT, delete POST_URN, react POST_URN [--type LIKE\|PRAISE\|EMPATHY\|INTEREST\|APPRECIATION\|ENTERTAINMENT], unreact POST_URN, comment POST_URN TEXT, edit-comment COMMENT_URN TEXT, delete-comment COMMENT_URN | | notifications | notifications [--limit N] | | network | connections [--limit N], invitations [--limit N], accept\|decline INVITATION_URN, connect PROFILE_URN [-m MESSAGE] | | messaging | list [--limit N], read CONVERSATION_URN [--limit N], send RECIPIENT TEXT (conversation or profile URN) | | auth | login, status, logout |

Examples

# Find people (returns name, headline, profile URL per result)
cli-web-linkedin search people "python developer" --limit 10 --json

# Job search, then full description
cli-web-linkedin jobs search "software engineer" --limit 5 --json
cli-web-linkedin jobs get 4388202530 --json

# Publish a post
cli-web-linkedin post create "Hello LinkedIn!" --json

# Pending invitations, then accept one (URN from the list)
cli-web-linkedin network invitations --json
cli-web-linkedin network accept "urn:li:invitation:123" --json

# Read recent messages
cli-web-linkedin messaging list --json
cli-web-linkedin messaging read "urn:li:msg_conversation:123" --json

JSON output

Every command accepts --json. Reads return the data object directly; writes return {"success": true, ...}. Errors return {"error": true, "code": "...", "message": "..."}.

Auth

cli-web-linkedin auth login      # browser-based LinkedIn login, stores li_at cookie
cli-web-linkedin auth status --json

Cookies live in ~/.config/cli-web-linkedin/auth.json; on 401/403 the CLI reloads them from disk, then refreshes via headless browser. For CI, set CLI_WEB_LINKEDIN_AUTH_JSON with the cookies JSON. Run doctor to diagnose auth problems.

Utilities

cli-web-linkedin doctor [--json] self-diagnoses the local setup (install, auth, dependencies). cli-web-linkedin mcp-serve serves the commands as MCP tools over stdio.

Agent tips

LinkedIn flags automated access aggressively; keep usage human-paced to protect the account:

  • Add sleep 3 between scripted invocations instead of tight loops — built-in inter-request delays only apply within a single process.
  • Stay under roughly 50 profile views and 150 searches per day.
  • URNs (post, comment, invitation, conversation) come from the JSON output of list/read commands — fetch them rather than constructing by hand.
Compartilhar X LinkedIn