CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

71

Quality

86%

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

86%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.

A tight, well-organized instruction skill with concrete tool selection and solid validation rules for risky write and authentication operations. Minor gaps are the absence of tool argument shapes and a fully numbered workflow sequence.

Suggestions

Add a brief example invocation or argument shape for one read and one write tool to make guidance copy-paste ready.

Consider presenting the browser/authentication flow as a short numbered sequence to make the retry-once checkpoint explicit.

DimensionReasoningScore

Conciseness

Lean and operational throughout; assumes Claude's knowledge of LinkedIn, MCP, and browsers, with every line earning its place and no concept over-explanation.

5 / 5

Actionability

Maps each task category to concrete tool names (e.g., get_person_profile, send_message) with explicit authorization rules, but provides no argument shapes or example invocations.

4 / 5

Workflow Clarity

Clear auth progression with checkpoints (captcha/2FA -> stop and ask) and write-action feedback loops ('do not retry unless the result proves it was not sent'), though guidance is rule-based rather than a numbered sequence.

4 / 5

Progressive Disclosure

Under 50 lines with no need for external references, organized into clear sections (Operating rules, Browser and authentication, Tool selection); the simple-skill exception applies.

5 / 5

Total

18

/

20

Passed

Description

87%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.

A concise, well-scoped description that clearly states capabilities and an explicit trigger condition with minimal conflict risk. The only weakness is generic action phrasing and a few missing natural synonyms.

Suggestions

Replace the generic verb 'Use LinkedIn data for ... work' with concrete actions (e.g., 'Fetch profiles, search people and jobs, read feeds and inbox, send messages and connection requests').

Add common trigger synonyms such as 'messages', 'connections', or 'networking' alongside 'inbox' and 'outreach'.

DimensionReasoningScore

Specificity

Names the LinkedIn domain plus many concrete capability areas (profile, company, job, post, feed, inbox, recruiting, outreach), though the action verb is generic ('Use ... for ... work') rather than enumerating distinct actions.

4 / 5

Completeness

Explicitly answers 'what' (LinkedIn data across listed domains via the bundled MCP server) and 'when' ('Use only for an explicit LinkedIn request') with a concrete trigger phrase.

5 / 5

Trigger Term Quality

Covers natural terms a user would say (LinkedIn, profile, company, job, post, feed, inbox, recruiting, outreach), but omits common synonyms such as 'message', 'connection', or 'network'.

4 / 5

Distinctiveness Conflict Risk

LinkedIn is a clear niche and the explicit-only trigger ('Use only for an explicit LinkedIn request') minimizes overlap with other skills.

5 / 5

Total

18

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
stickerdaniel/linkedin-mcp-server
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.