Name: linkedin-ads
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

linkedin-ads

LinkedIn Ads integration. Manage Accounts. Use when the user wants to interact with LinkedIn Ads data.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/linkedin-ads/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 concrete CLI commands and good connection-state handling, but loses points for an unnecessary intro explanation of LinkedIn Ads and a lack of validation guidance around its destructive delete actions.

Suggestions

Trim the opening paragraph that defines LinkedIn Ads and the 'rather than auth plumbing' marketing phrasing — Claude already knows the platform.

Add a validation/confirmation step before destructive actions, e.g. 'Before running delete-* actions, confirm the entity is in DRAFT state with a get-* call and verify the ID with the user'.

Consider moving the 20-row Popular actions table into a separate reference file and linking it, keeping only the most common entries inline.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command reference, but the opening paragraph explaining what LinkedIn Ads is ('LinkedIn Ads is a platform for businesses to advertise to professionals...') and soft marketing lines ('focus on the integration logic rather than auth plumbing') restate concepts Claude already knows.	3 / 5
Actionability	It provides copy-paste-ready, executable commands for every common case — 'npm install -g @membranehq/cli@latest', 'membrane connection ensure "..."', 'membrane action run <actionId> ...', 'membrane request CONNECTION_ID /path' — plus a full action-key table.	5 / 5
Workflow Clarity	The connection flow is well sequenced with state-based polling checkpoints (READY / BUILDING / CLIENT_ACTION_REQUIRED), but the skill exposes destructive operations (Delete Campaign Group/Campaign/Creative) with no validation or verification step before running them, capping this dimension at 3.	3 / 5
Progressive Disclosure	Structure is clear with well-organized sections (Overview, Working with LinkedIn Ads, Popular actions, Best practices) and no nested references; the only minor gap is the 20-row action table and proxy-flag table being inlined rather than split into a reference file.	4 / 5
	Total	15 / 20 Passed

Description

62%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 cleanly states what the skill does and when to use it, with a clear LinkedIn Ads niche. It is let down by thin action specificity ('Manage Accounts' only) and limited trigger-term coverage that misses common LinkedIn Ads vocabulary.

Suggestions

Replace the generic 'Manage Accounts' with several concrete actions, e.g. 'Manage ad accounts, campaigns, creatives, and analytics'.

Expand the 'Use when' clause to list natural trigger phrases users say: 'campaigns', 'ad creatives', 'ad analytics', 'lead gen forms'.

Keep third-person voice but add 1-2 more specific capability verbs to lift specificity beyond a single action.

Dimension	Reasoning	Score
Specificity	Quotes 'LinkedIn Ads integration' and 'Manage Accounts' — it names the domain and one concrete object (Accounts), but the single verb 'Manage' is generic and coverage of the platform's capabilities is far from comprehensive.	3 / 5
Completeness	It answers both 'what' ('LinkedIn Ads integration. Manage Accounts.') and 'when' ('Use when the user wants to interact with LinkedIn Ads data'), with the 'when' clause explicit though it could name more concrete trigger phrases.	4 / 5
Trigger Term Quality	It includes the natural trigger 'LinkedIn Ads' and 'interact with LinkedIn Ads data', but omits common variations users would say such as campaigns, ad creatives, analytics, and lead gen forms.	3 / 5
Distinctiveness Conflict Risk	'LinkedIn Ads' is a clear, distinct niche with minimal conflict risk, though broad 'Manage Accounts' wording leaves minor overlap with a generic LinkedIn or general-ads skill.	4 / 5
	Total	14 / 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-ads/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.