linkedin-cli-write
Use this skill for authenticated LinkedIn mutations in the linkedin-cli repository.
Preflight
Run uv run linkedin auth-status first. Do not attempt write actions against a degraded session.
Write Commands
uv run linkedin post "Hello from linkedin-cli" --visibility connections
uv run linkedin react urn:li:activity:123 --type like
uv run linkedin unreact urn:li:activity:123
uv run linkedin save urn:li:activity:123
uv run linkedin unsave urn:li:activity:123
uv run linkedin comment urn:li:activity:123 "great post"
Operating Rules
- Confirm the target activity identifier before sending a mutation.
- Keep write volume conservative; do not automate repeated posting or engagement loops.
- Prefer
connectionsvisibility unless the user explicitly requestspublic. - Use
$linkedin-cli-authimmediately when writes fail because of session health, redirects, or missing cookies. - Read the reference doc before relying on browser fallback behavior.
Read Next
- Read write-workflows.md for command coverage, fallback behavior, and failure mapping.
- Use
$linkedin-clifor read-side inspection before mutating unknown activities.
Source: frizynn/linkedin-cli — distributed by TomeVault.