CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

linkedin-mcp

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.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a lean, well-organized rule set for dispatching LinkedIn MCP tools safely: exact tool names per task category, explicit authorization and confirmation checkpoints for every write action, and bounded retry behavior for auth and send failures. Its only shortfalls are the absence of example tool invocations and mild repetition in the write-authorization rules.

DimensionReasoningScore

Conciseness

Quotes: 'Start with the smallest read operation that can answer the request', 'Distinguish retrieved facts from inference', and the tool lists — terse, operational rules with zero explanation of concepts Claude already knows. The write-authorization pattern is restated across three bullets ('Use it only when the user explicitly asks...') and could be consolidated, which matches anchor 4 ('minor instances ... could be trimmed') rather than anchor 5's every-token-earns-its-place.

4 / 5

Actionability

Quotes: 'Profiles: `get_my_profile`, `get_person_profile`, `search_people`, and `get_sidebar_profiles`' — exact tool names mapped to every task category, plus executable conditions like 'Confirm the final message or connection note unless the user has already supplied it' and 'retry once after it finishes'. No example invocations or arguments are given and 'Keep searches and result pages modest' states no concrete limit, so it falls short of anchor 5's fully executable, example-covered guidance while clearly exceeding anchor 3's pseudocode-level incompleteness.

4 / 5

Workflow Clarity

Checkpoints are explicit for the risky operations: confirm the exact message or connection note before writes, 'dismiss_job ... cannot be undone' is gated on explicit user request, auth has a bounded feedback loop ('report that exact state and retry once after it finishes. Do not loop'), and 'Do not retry a failed write action unless the result proves it was not sent' governs failure recovery. This satisfies the destructive-operation validation requirement, but the overall order of operations (verify request → check session → read → authorized write) is implied across sections rather than sequenced, matching anchor 4 with minor gaps rather than anchor 5's explicit stepwise workflow.

4 / 5

Progressive Disclosure

A self-contained, single-purpose skill (~45 content lines) with three clear sections ('Operating rules', 'Browser and authentication', 'Tool selection'), no nested or buried references — the body references no files and no references/scripts/assets bundle exists — and no content that belongs in a separate file. Per the simple-skill scoring note, well-organized sections alone warrant 5 here; anchor 4 would require organization gaps that are not present.

5 / 5

Total

17

/

20

Passed

Description

73%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly names its niche, answers both what it does and when to use it, and carries minimal conflict risk thanks to the 'explicit LinkedIn request' gate. Its main weakness is generic action language — it enumerates work areas rather than concrete operations, and omits common trigger words for messaging and connecting.

Suggestions

Replace the generic 'Use LinkedIn data for ... work' with concrete operations, e.g. 'Search profiles, companies, and jobs; read feeds, posts, and the inbox; send messages and connection requests through the bundled LinkedIn MCP server.'

Add the natural phrases users say for messaging tasks ('send a message', 'connect', 'InMail') alongside the existing domain keywords.

Expand the when-clause with concrete triggers, e.g. 'Use only when the user explicitly asks for LinkedIn data or a LinkedIn action, such as viewing a profile, searching jobs, or messaging a connection.'

DimensionReasoningScore

Specificity

Quotes: 'Use LinkedIn data for profile, company, job, post, feed, inbox, recruiting, and outreach work through the bundled LinkedIn MCP server.' It names the domain and eight work areas, but the only action verb is the generic 'Use ... data for ... work' — no concrete operations (search, view, send) are stated. This fits anchor 3 (domain plus limited concrete actions) rather than anchor 4, which expects several specific actions listed; it is above anchor 2 because the enumerated coverage goes well beyond naming the domain alone.

3 / 5

Completeness

Both parts are present: what ('Use LinkedIn data for profile, company, job, post, feed, inbox, recruiting, and outreach work through the bundled LinkedIn MCP server') and when ('Use only for an explicit LinkedIn request'). The when-clause is explicit, so it clears the anchor-3 cap, but it is a single terse condition rather than the enumerated concrete trigger phrases that distinguish anchor 5 ('when the user mentions PDFs, forms, or document extraction').

4 / 5

Trigger Term Quality

Quotes: 'profile, company, job, post, feed, inbox, recruiting, and outreach' plus 'LinkedIn' itself — all natural terms a user would say. Common phrasings such as 'message', 'connect', 'InMail', or 'network' are absent, so it matches anchor 4 ('good keyword coverage; a few natural terms missing') rather than anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Quotes: 'through the bundled LinkedIn MCP server' and 'Use only for an explicit LinkedIn request.' LinkedIn is a clear niche with a hard trigger condition; no other skill would plausibly claim these requests, a direct match for anchor 5 ('clear niche with distinct triggers; minimal conflict risk').

5 / 5

Total

16

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

stickerdaniel/linkedin-mcp-server

Path

plugins/linkedin-mcp-server/skills/linkedin-mcp/SKILL.md

Reviewed

Table of Contents

Is this your skill?

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.