linkedin-skills

Use when someone wants to grow an organic LinkedIn presence — a content strategy for a career change or consulting or thought leadership, a rewritten profile or headline, post drafts and hooks, a posting cadence or newsletter plan, connection notes and outreach, a commenting strategy, repurposing an article or talk into posts, or a read on why their reach dropped. Triggers on "grow my LinkedIn", "fix my headline", "write a LinkedIn post", "what should I post about", "LinkedIn strategy", "connection request", "my reach dropped". Forks context to route to one of five sub-skills, and refuses automation, scraping, pods, and bulk DMs before any drafting starts.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

88%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 well-orchestrated router skill: concrete commands with exit-code-driven branching, validation gating before any drafting, and verified one-level-deep references. Its two minor weaknesses are near-verbatim duplication of the safety statement between the blockquote and hard rules, and incomplete navigation to the five forked sub-skills that hold the remaining scripts.

Suggestions

Drop the duplicated automation/safety sentence from either the opening blockquote or the first hard rule (they say the same thing about credentials, API, scraping, and auto-sending).

Give the five lane sub-skills explicit paths or skill identifiers in the lane table so the fork target is navigable, and clarify that the other 15 of the 17 scripts live in those sub-skills.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — no explanation of known concepts, dense tables, commands only. However, the opening blockquote ('No LinkedIn credentials, no API calls, no scraping, nothing auto-sent') nearly verbatim duplicates the first hard rule, and the footer repeats '17 stdlib scripts · nothing auto-sent', so minor trims remain.	4 / 5
Actionability	Fully executable guidance: copy-paste commands for both scripts ('python3 scripts/linkedin_policy_gate.py --text "<the user's own words>" --output human') with complete exit-code semantics (REFUSE=4/CONSTRAIN=3/ALLOW=0, route=0/ambiguous=2/no-signal=3), a lane table with typical asks, and five concrete forcing questions with recommendations.	5 / 5
Workflow Clarity	Clear gate-before-draft sequence with the policy gate as an explicit validation checkpoint, precedence rules ('A REFUSE outranks any route below'), a refuse→substitute→reroute feedback loop, and a stop condition ('Stop as soon as the lane can run honestly'). No destructive or batch operations exist, so the validation cap does not apply.	5 / 5
Progressive Disclosure	The overview is lean, references are one level deep, clearly signaled with roles, and all linked files (2 scripts, 2 references, 1 asset) verify as real bundle files. But the five lane sub-skills are named ('linkedin-profile', etc.) without paths, and the '17 stdlib-only Python scripts' claim versus 2 scripts present in this bundle leaves a navigation ambiguity for the other 15.	4 / 5
	Total	18 / 20 Passed

Description

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

An exemplary description: dense with concrete deliverables, explicit use-when guidance with seven natural trigger phrases, and honest boundary-setting (refusing automation/scraping/pods). The only weakness is that a few trigger terms are not platform-qualified, creating minor overlap risk with adjacent social-growth skills.

Dimension	Reasoning	Score
Specificity	The description enumerates multiple concrete deliverables — 'a rewritten profile or headline, post drafts and hooks, a posting cadence or newsletter plan, connection notes and outreach, a commenting strategy, repurposing an article or talk into posts, or a read on why their reach dropped' — giving comprehensive, non-generic coverage across all five capability lanes.	5 / 5
Completeness	It explicitly answers 'when' with a 'Use when someone wants to grow an organic LinkedIn presence…' clause plus concrete trigger phrases, and 'what' with 'Forks context to route to one of five sub-skills, and refuses automation, scraping, pods, and bulk DMs before any drafting starts.'	5 / 5
Trigger Term Quality	It lists seven natural user phrasings with synonym variation ('grow my LinkedIn', 'fix my headline', 'write a LinkedIn post', 'what should I post about', 'LinkedIn strategy', 'connection request', 'my reach dropped'); these are exactly what a user would say when needing this skill, with no common variant missing.	5 / 5
Distinctiveness Conflict Risk	The platform is named throughout and the niche (organic LinkedIn presence, one platform in depth) is distinct, but several trigger phrases ('fix my headline', 'what should I post about', 'my reach dropped') are platform-agnostic and could also match closely related multi-platform or X/Twitter growth skills.	4 / 5
	Total	19 / 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: alirezarezvani/claude-skills
Path: marketing/linkedin/skills/linkedin-skills/SKILL.md
Commit: 19392f7

Reviewed: 16 hours 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.