Use the `linkedin-cli` repository to operate LinkedIn from the terminal. Trigger on requests to inspect the LinkedIn feed, search people or posts, fetch a profile, fetch profile posts, inspect an activity, export LinkedIn data as JSON, run `linkedin` commands, or decide which `linkedin-cli` command to use. Also use when the user mentions this repo or the `linkedin` CLI directly.
Use this skill for read-heavy and command-selection workflows with the public linkedin-cli repo.
Prefer the first working option:
uv run linkedin ...
linkedin ...
.venv/bin/linkedin ...
Run commands from the repository root when using uv run or .venv/bin/linkedin.
uv run linkedin auth-status.--json when another tool or script will consume the output.--output <file> for feed, search, and profile-posts when the user wants an artifact on disk.$linkedin-cli-auth when the problem is mainly auth, cookies, browser extraction, proxying, or redirects.$linkedin-cli-write when the task is mainly posting, reacting, saving, unsaving, or commenting.| Need | Command |
|---|---|
| Verify session and probes | uv run linkedin auth-status |
| Read home feed | uv run linkedin feed --max 10 |
| Search people and posts | uv run linkedin search "AI engineer" --max 10 |
| Fetch one profile | uv run linkedin profile lebrero-juan-francisco |
| Fetch recent posts from a profile | uv run linkedin profile-posts lebrero-juan-francisco --max 10 |
| Inspect one activity | uv run linkedin activity urn:li:activity:123 --json |
satyanadella or a full LinkedIn profile URL to profile and profile-posts.activity and write-side commands.--json before downstream processing when the request involves filtering, summarizing, or saving structured output.$linkedin-cli-auth for session recovery and runtime troubleshooting.$linkedin-cli-write for authenticated mutations and browser fallback behavior.