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.
81%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
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.
send_message, reply_to_conversation and connect_with_person are 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.archive_conversation is a write action too: it moves a thread out of the
user's inbox. Use it only when the user explicitly asks to archive that
thread.dismiss_job hides a job from every later search and cannot be undone. Use
it only for jobs the user asked to dismiss.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.
get_my_profile, get_person_profile, search_people, and
get_sidebar_profiles.get_company_profile, get_company_posts, search_companies,
and get_company_employees.search_jobs, get_saved_jobs, get_job_details,
get_job_apply_url and get_easy_apply_form. get_easy_apply_form opens
the Easy Apply form, so use it only when the user is preparing an
application.get_feed and search_posts.get_inbox, get_conversation, and search_conversations.send_message, reply_to_conversation (answer an existing thread,
InMail included), connect_with_person, archive_conversation and
dismiss_job, subject to the explicit authorization rules above.get_session_status says whether a login is saved without opening
a browser or a login window; it does not prove LinkedIn still accepts it.close_session only 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/linkedin-mcp-server
e9b47a4
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.