Use when automating LinkedIn via CLI: fetch profiles, search people/companies, send messages, manage connections, create posts, and Sales Navigator.
84%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
High
Do not use without reviewing
The canonical home for this skill is linkedin-cli in administrakt0r/AI-Agents-Safe-Coding-Skills
The skill handles credentials insecurely by requiring the agent to include secret values verbatim in its generated output. This exposes credentials in the agent’s context and conversation history, creating a risk of data exfiltration.
The skill prompt instructs the agent to ask the user for tokens and pass them directly as command-line arguments via the CLI (`linkedin setup --linked-api-token=TOKEN --identification-token=TOKEN`), which causes the LLM to handle and output sensitive credential values directly.
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
The workflow consumes outsider-authored content via LinkedIn profiles, posts, messages, and comments fetched through CLI commands.
The skill fetches instructions or code from an external URL at runtime, and the fetched content directly controls the agent’s prompts or executes code. This dynamic dependency allows the external source to modify the agent’s behavior without any changes to the skill itself.
The skill references an external npm package installation command (`npm install -g @linkedapi/linkedin-cli`) which constitutes an unverifiable runtime external dependency from an unverified publisher tier.
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.