Name: linkedin
Rating: 58.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

LinkedIn integration. Manage Users, Organizations. Use when the user wants to interact with LinkedIn data.

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/linkedin/SKILL.md

Quality

Content

68%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 highly actionable with copy-paste Membrane CLI commands and a well-structured connection workflow, but it loses conciseness to an unnecessary intro about what LinkedIn is and lacks validation guidance for its destructive actions, which caps workflow clarity.

Suggestions

Remove or compress the opening paragraph explaining what LinkedIn is; Claude already knows this.

Add an explicit validation/confirmation checkpoint before running destructive actions (delete-post, delete-comment, delete-reaction), e.g. confirm the target URN with the user and verify existence via get-post before deletion.

Fix the inconsistent step numbering ("1b" with no "1a"/"Step 2" label) so the connection sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	The opening paragraph "LinkedIn is a professional networking platform where users create profiles to showcase their work experience..." explains a concept Claude already knows, and lines like "so you can focus on the integration logic rather than auth plumbing" add padding; the rest is mostly efficient, fitting the 'mostly efficient but includes some unnecessary explanation' anchor rather than level 4.	3 / 5
Actionability	The body provides copy-paste-ready commands throughout (`npm install -g @membranehq/cli@latest`, `membrane login`, `membrane connection ensure`, `membrane action list`, `membrane action run`, `membrane request`) plus a concrete actions table and flag reference, matching the 'fully executable; copy-paste ready code or commands; specific examples cover the common cases' anchor.	5 / 5
Workflow Clarity	The connect-to-LinkedIn flow is sequenced with state polling and error handling (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but the skill exposes destructive actions (delete-post, delete-comment, delete-reaction) with no validation or verification checkpoint before running them, so per the destructive-operations cap workflow clarity cannot exceed 3.	3 / 5
Progressive Disclosure	Content is organized into clear, well-labeled sections (Overview, Install, Authentication, Connecting, Searching, Popular actions, Proxy requests, Best practices) with no nested references and a single inline file; the large inline actions table is a minor organization gap that keeps it just below the ideal level-5 split.	4 / 5
	Total	15 / 20 Passed

Description

66%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 is a solid third-person statement that covers both what the skill does and when to use it, with a distinct LinkedIn niche. Its main weakness is generic verbs ("Manage") and limited trigger-term variety, which keep specificity and trigger quality at mid-range.

Suggestions

Replace the generic verb "Manage" with concrete actions, e.g. "Create, update, and delete posts, comments, reactions; retrieve profiles and organizations."

Add natural trigger variations and file/term synonyms, e.g. "Use when the user wants to post, comment, react, or pull LinkedIn profile, organization, or network data."

Dimension	Reasoning	Score
Specificity	"Manage Users, Organizations" names the LinkedIn domain and two entity types, but the verb "Manage" is generic and coverage is not comprehensive, matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor rather than the more specific level 4.	3 / 5
Completeness	It states both what ("LinkedIn integration. Manage Users, Organizations.") and when ("Use when the user wants to interact with LinkedIn data"), matching the level-4 anchor where both are present though the 'when' could be more specific; it does not reach level 5 because the trigger phrases are not as concrete as the top anchor.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with LinkedIn data" surfaces the natural keyword "LinkedIn" but lacks synonyms or varied phrasings users might say, fitting the 'some relevant keywords but missing common variations or synonyms' anchor.	3 / 5
Distinctiveness Conflict Risk	"LinkedIn integration" targets a clear, single-platform niche with distinct triggers and minimal overlap risk with other skills, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.	5 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/linkedin/SKILL.md
Commit: f484c82

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.