Omentir Linkedin Outreach
sickn33/agentic-awesome-skills
Run LinkedIn prospecting and outreach through the Omentir MCP server: find people, score fit, draft messages, and check campaigns.
Rules for using the bundled LinkedIn MCP server for profile, company, job, post, feed and inbox work, with explicit authorization required for messages and connection requests.
Install LinkedIn MCP Usage Rules
$ npx skills add stickerdaniel/linkedin-mcp-server --skill linkedin-mcp -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install stickerdaniel/linkedin-mcp-server linkedin-mcp --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/stickerdaniel/linkedin-mcp-server.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/linkedin-mcp-server/skills/linkedin-mcp .claude/skills/linkedin-mcp && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "linkedin-mcp" agent skill from https://github.com/stickerdaniel/linkedin-mcp-server/tree/main/plugins/linkedin-mcp-server/skills/linkedin-mcp into .claude/skills/linkedin-mcp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-mcp", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/stickerdaniel/linkedin-mcp-server/tree/main/plugins/linkedin-mcp-server/skills/linkedin-mcpType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add stickerdaniel/linkedin-mcp-server --skill linkedin-mcp -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install stickerdaniel/linkedin-mcp-server linkedin-mcp --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stickerdaniel/linkedin-mcp-server.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/linkedin-mcp-server/skills/linkedin-mcp .agents/skills/linkedin-mcp && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "linkedin-mcp" agent skill from https://github.com/stickerdaniel/linkedin-mcp-server/tree/main/plugins/linkedin-mcp-server/skills/linkedin-mcp into .agents/skills/linkedin-mcp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-mcp", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add stickerdaniel/linkedin-mcp-server --skill linkedin-mcp -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install stickerdaniel/linkedin-mcp-server linkedin-mcp --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stickerdaniel/linkedin-mcp-server.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/linkedin-mcp-server/skills/linkedin-mcp .cursor/skills/linkedin-mcp && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "linkedin-mcp" agent skill from https://github.com/stickerdaniel/linkedin-mcp-server/tree/main/plugins/linkedin-mcp-server/skills/linkedin-mcp into .cursor/skills/linkedin-mcp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-mcp", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/stickerdaniel/linkedin-mcp-server.git --path plugins/linkedin-mcp-server/skills/linkedin-mcp--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add stickerdaniel/linkedin-mcp-server --skill linkedin-mcp -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install stickerdaniel/linkedin-mcp-server linkedin-mcp --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stickerdaniel/linkedin-mcp-server.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/linkedin-mcp-server/skills/linkedin-mcp .gemini/skills/linkedin-mcp && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "linkedin-mcp" agent skill from https://github.com/stickerdaniel/linkedin-mcp-server/tree/main/plugins/linkedin-mcp-server/skills/linkedin-mcp into .gemini/skills/linkedin-mcp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-mcp", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install stickerdaniel/linkedin-mcp-server linkedin-mcpInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add stickerdaniel/linkedin-mcp-server --skill linkedin-mcp -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/stickerdaniel/linkedin-mcp-server.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/linkedin-mcp-server/skills/linkedin-mcp .github/skills/linkedin-mcp && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "linkedin-mcp" agent skill from https://github.com/stickerdaniel/linkedin-mcp-server/tree/main/plugins/linkedin-mcp-server/skills/linkedin-mcp into .github/skills/linkedin-mcp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-mcp", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add stickerdaniel/linkedin-mcp-server --skill linkedin-mcp -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install stickerdaniel/linkedin-mcp-server linkedin-mcp --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stickerdaniel/linkedin-mcp-server.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/linkedin-mcp-server/skills/linkedin-mcp .opencode/skills/linkedin-mcp && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "linkedin-mcp" agent skill from https://github.com/stickerdaniel/linkedin-mcp-server/tree/main/plugins/linkedin-mcp-server/skills/linkedin-mcp into .opencode/skills/linkedin-mcp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-mcp", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
linkedin-mcp- GitHub stars
- 3.8k
- Token cost
- ~651 tokens
- SKILL.md length
- 327 words
- Files
- 1
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Rules for using the bundled LinkedIn MCP server for profile, company, job, post, feed and inbox work, with explicit authorization required for messages and connection requests.
- Looking up a person's or company's LinkedIn profile for research
- SKILL.md covers Operating rules, Browser and authentication and Tool selection
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Searching LinkedIn jobs or posts for a specific topic
What it does
The skill tells the agent to use the bundled linkedin MCP server only when you explicitly ask for LinkedIn data or an action, never for unrelated work, health checks or background maintenance. It starts with the smallest read operation, treats results as live evidence and separates retrieved facts from inference, keeps searches modest and does not collect data in bulk. The tools are listed by area: profiles, companies, jobs, feed and post search, and inbox and conversations.
send_message and connect_with_person are write actions that need your explicit approval of the exact recipient and action, with the final text confirmed, and a failed write is not retried unless it clearly was not sent. The server drives a managed Chromium browser with your own LinkedIn session. Enabling the plugin does not sign you in, and if LinkedIn shows a captcha or two-factor prompt the agent stops and asks you to complete it. It does not enable the plugin, edit configuration or start a login flow on its own, and close_session ends the browser session.
When your agent uses it
- Looking up a person's or company's LinkedIn profile for research
- Searching LinkedIn jobs or posts for a specific topic
- Reading your inbox or a conversation, and sending a message you have approved
Example prompts
- “Look up the LinkedIn profile of our new vendor's CTO and summarize their background.”
- “Search LinkedIn jobs for data engineer roles in Berlin and list the top matches.”
- “Show my latest LinkedIn conversations, then draft a reply to the recruiter for my approval.”
Requirements
- The LinkedIn MCP server plugin, enabled
- A LinkedIn account that you sign in to yourself
What it can do on your machine
Read from SKILL.md and the folder at commit b71682f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
LinkedIn MCP Usage Rules loads about 651 tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 327 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from stickerdaniel/linkedin-mcp-server at commit b71682f, republished under its Apache-2.0 licence (© stickerdaniel). 327 words, ~651 tokens.
Download SKILL.mdSave it as
.claude/skills/linkedin-mcp/SKILL.md (or your agent's skills folder).- name
- linkedin-mcp
- description
- Use LinkedIn data for profile, company, job, post, feed, inbox, recruiting, and outreach work through the bundled LinkedIn MCP server. Use only for an explicit LinkedIn request.
LinkedIn MCP
Use the bundled linkedin MCP server only when the user explicitly asks for
LinkedIn data or an action on LinkedIn. Do not call LinkedIn tools for unrelated
work, health checks, or background maintenance.
Operating rules
- Start with the smallest read operation that can answer the request.
- Treat profile, company, job, post, feed, and message results as live LinkedIn evidence. Distinguish retrieved facts from inference.
- Keep searches and result pages modest. Do not collect data in bulk or spam.
- Never enable the plugin or its MCP server, edit Codex configuration, or start a login flow merely because LinkedIn might be useful. If either component is disabled, explain that state and stop.
send_messageandconnect_with_personare write actions. Use them only when the user explicitly authorizes the exact recipient and action. Confirm the final message or connection note unless the user has already supplied it.- Do not retry a failed write action unless the result proves it was not sent.
Browser and authentication
The server uses a managed Chromium browser and the user's own LinkedIn session. Installing or enabling the plugin does not sign in. The first LinkedIn data request may prepare the browser, import an existing local session, or require a visible login window. If LinkedIn presents a captcha, two-factor prompt, or other user-owned authentication step, stop and ask the user to complete it.
If browser setup or authentication is still in progress, report that exact state and retry once after it finishes. Do not loop, launch extra browser instances, clear profiles, or replace the user's browser session.
Tool selection
- Profiles:
get_my_profile,get_person_profile,search_people, andget_sidebar_profiles. - Companies:
get_company_profile,get_company_posts,search_companies, andget_company_employees. - Jobs:
search_jobs,get_saved_jobs,get_job_details, andget_job_apply_url. - Content:
get_feedandsearch_posts. - Messages:
get_inbox,get_conversation, andsearch_conversations. - Writes:
send_messageandconnect_with_person, subject to the explicit authorization rules above. - Cleanup: use
close_sessiononly when the user asks to end the managed browser session or when the current LinkedIn task is finished and no follow-up call is expected.
© stickerdaniel, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/linkedin-mcp-server/skills/linkedin-mcp of stickerdaniel/linkedin-mcp-server.
Open the folder on GitHubat commit b71682f
Compare with similar skills
LinkedIn MCP Usage Rules next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| LinkedIn MCP Usage Rules this skillstickerdaniel/linkedin-mcp-server | 3.8k | — | ~651 | Automated safety check: Pass | Apache-2.0 | |
| Omentir Linkedin Outreachsickn33/agentic-awesome-skills | 47k | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Outreach Messagemohitagw15856/pm-claude-skills | 1.4k | — | ~827 | Automated safety check: Pass | MIT | |
| Sales OsromangojiberryAI/gojiberryai-sales-os | 138 | — | ~2k | Automated safety check: Pass | MIT | |
| Outreachandrew-shwetzer/career-ops-plugin-do-not-fork-currently-updating-v2- | 501 | — | ~939 | Automated safety check: Pass | MIT | |
| Jobgptsickn33/agentic-awesome-skills | 47k | 2 repos | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
Outreach Message
mohitagw15856/pm-claude-skills
Write cold outreach and networking messages that actually get replies.
Sales Os
romangojiberryAI/gojiberryai-sales-os
A complete outbound sales department in one skill. An agent skill from romangojiberryAI/gojiberryai-sales-os.
Outreach
andrew-shwetzer/career-ops-plugin-do-not-fork-currently-updating-v2-
Draft personalized outreach messages for LinkedIn connections, hiring managers, or recruiters.
Jobgpt
sickn33/agentic-awesome-skills
Job search automation, auto apply, resume generation, application tracking, salary intelligence, and recruiter outreach using the JobGPT MCP server.
Workorai
davila7/claude-code-templates
WorkorAI talent marketplace skill: candidate job search and employer hiring with white-box match explanations via the WorkorAI MCP server (https://workorai.com/mcp).
More from stickerdaniel/linkedin-mcp-server
Issue and PR Triage
stickerdaniel/linkedin-mcp-server
Turns the open issues and pull requests of the linkedin-mcp-server repository into a read-only priority list for maintainers.
LinkedIn MCP Issue Investigator
stickerdaniel/linkedin-mcp-server
Investigates a reported LinkedIn-MCP issue by matching the reporter's tool call to the exact source file and tests, without applying a fix.
Verify Candidate PR Fix
stickerdaniel/linkedin-mcp-server
Reviews a candidate pull request's diff and tests against its linked issue, with an optional live comparison against a previously captured baseline, without editing, merging or pushing.
BTCA Local Repo Search
stickerdaniel/linkedin-mcp-server
Searches git repositories cloned locally under a sandbox folder to answer questions with cited links and complete code snippets.
PR Review Triage
stickerdaniel/linkedin-mcp-server
Collects every review comment on a pull request, checks each against the real code, fixes the valid ones, pushes, and replies on and resolves each thread.
GitHub Issue Packet Intake
stickerdaniel/linkedin-mcp-server
Turns a bug report or feature idea into a properly sourced GitHub issue or comment, only after searching for a matching issue first.
Related
Works with
Categories
Questions about LinkedIn MCP Usage Rules
What does LinkedIn MCP Usage Rules do?
Rules for using the bundled LinkedIn MCP server for profile, company, job, post, feed and inbox work, with explicit authorization required for messages and connection requests. The skill tells the agent to use the bundled linkedin MCP server only when you explicitly ask for LinkedIn data or an action, never for unrelated work, health checks or background maintenance. It starts with the smallest read operation, treats results as live evidence and separates retrieved facts from inference, keeps searches modest and does not collect data in bulk.
When should I use LinkedIn MCP Usage Rules?
LinkedIn MCP Usage Rules fits situations like: looking up a person's or company's LinkedIn profile for research; searching LinkedIn jobs or posts for a specific topic; reading your inbox or a conversation, and sending a message you have approved.
How do I install LinkedIn MCP Usage Rules in Claude Code?
Run `npx skills add stickerdaniel/linkedin-mcp-server --skill linkedin-mcp -a claude-code`. Or copy the skill folder (plugins/linkedin-mcp-server/skills/linkedin-mcp in stickerdaniel/linkedin-mcp-server) into .claude/skills/linkedin-mcp in your project. Claude Code loads it when a task matches its description.
How do I install LinkedIn MCP Usage Rules in Codex?
Run `npx skills add stickerdaniel/linkedin-mcp-server --skill linkedin-mcp -a codex`. Or copy the skill folder (plugins/linkedin-mcp-server/skills/linkedin-mcp in stickerdaniel/linkedin-mcp-server) into .agents/skills/linkedin-mcp in your project. Codex loads it when a task matches its description.
Can I use LinkedIn MCP Usage Rules in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add stickerdaniel/linkedin-mcp-server --skill linkedin-mcp -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/linkedin-mcp, .gemini/skills/linkedin-mcp, .github/skills/linkedin-mcp and .opencode/skills/linkedin-mcp in your project.
What does LinkedIn MCP Usage Rules need to run?
SKILL.md names no scripts, command-line tools or credentials: LinkedIn MCP Usage Rules is instructions for the agent only. Our summary lists: The LinkedIn MCP server plugin, enabled; A LinkedIn account that you sign in to yourself.
Does LinkedIn MCP Usage Rules access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is LinkedIn MCP Usage Rules safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does LinkedIn MCP Usage Rules use?
LinkedIn MCP Usage Rules is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does LinkedIn MCP Usage Rules use?
About 651 tokens (SKILL.md is roughly 2.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to LinkedIn MCP Usage Rules?
Skills that share tags, products or a category with LinkedIn MCP Usage Rules: Omentir Linkedin Outreach (sickn33/agentic-awesome-skills, 47k stars), Outreach Message (mohitagw15856/pm-claude-skills, 1.4k stars), Sales Os (romangojiberryAI/gojiberryai-sales-os, 138 stars) and Outreach (andrew-shwetzer/career-ops-plugin-do-not-fork-currently-updating-v2-, 501 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains LinkedIn MCP Usage Rules?
stickerdaniel (a GitHub user) maintains it in stickerdaniel/linkedin-mcp-server, which has 3,782 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 7, 2026.
Source: stickerdaniel/linkedin-mcp-server on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.