Name: linkedin-skills
Rating: 71.2 (1 reviews)
Author: alirezarezvani

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

88%

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

The canonical home for this skill is linkedin-skills in alirezarezvani/claude-skills

Quality

Content

77%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 well-sequenced with a strong validation gate and concrete commands, but its progressive disclosure is undermined by a missing bundle: every referenced script, reference, and asset file is absent, and the '17 scripts' claim is unsupported.

Suggestions

Ship the bundle: create scripts/, references/, and assets/ with the files the body links to (linkedin_policy_gate.py, linkedin_goal_router.py, linkedin_platform_canon.md, policy_and_account_safety.md, linkedin_operating_agreement.md), or remove the links.

Reconcile the script count: the body and footer say '17 stdlib-only Python scripts' but the Scripts table lists only 2 — either add the missing 15 or correct the number.

De-duplicate the safety message so the 'no credentials / no API / no scraping' rule appears once (e.g. in Hard rules) rather than in the top quote, the REFUSE bullets, and Hard rules.

Dimension	Reasoning	Score
Conciseness	Lean and mostly efficient with no over-explanation of concepts Claude already knows, but the safety message ('No credentials, no API, no scraping, nothing auto-sent') is repeated across the top quote, the Step 1 REFUSE bullets, and the Hard rules section, which could be consolidated.	4 / 5
Actionability	Provides concrete copy-paste commands with flags ('python3 scripts/linkedin_policy_gate.py --text "…" --output human') and explicit exit-code decision logic (exit 4/3/0, route 0/2/3), though the actual lane sub-skill invocations are delegated rather than shown as executable steps.	4 / 5
Workflow Clarity	A clear Gate → Route → Forcing-questions sequence with an explicit pre-drafting validation checkpoint and feedback loops: REFUSE names the rule and offers the printed substitute then reroutes, CONSTRAIN states the constraint, ALLOW proceeds.	5 / 5
Progressive Disclosure	The structure and signaling are good (clear one-level-deep markdown links to scripts, references, and assets), but the actual bundle contains none of the referenced files — scripts/, references/, and assets/ do not exist — so every link is a dead end, and the body claims '17 stdlib-only Python scripts' while only 2 are listed and 0 are present.	3 / 5
	Total	16 / 20 Passed

Description

100%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 exemplary: concrete capabilities, explicit natural-language triggers, both a clear 'what' and 'when', and a distinct niche with minimal conflict risk. It is the strongest part of the skill.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — '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' — giving comprehensive coverage in third person.	5 / 5
Completeness	Explicitly answers both 'what' (grow an organic LinkedIn presence across five lanes, routing to sub-skills, refusing automation) and 'when' ('Use when someone wants to grow an organic LinkedIn presence…' plus 'Triggers on…') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Explicit natural trigger phrases users would say — 'grow my LinkedIn', 'fix my headline', 'write a LinkedIn post', 'what should I post about', 'LinkedIn strategy', 'connection request', 'my reach dropped' — covering synonyms and variations comprehensively.	5 / 5
Distinctiveness Conflict Risk	Clear LinkedIn-only niche with platform-specific triggers and explicit distinct_from boundaries, so it is unlikely to fire for the wrong skill.	5 / 5
	Total	20 / 20 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 5 missing	Warning
referenced_paths_exist	Referenced path issues: 12 missing	Warning

	Total	13 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: .gemini/skills/linkedin-skills/SKILL.md
Commit: 19392f7

Reviewed: ~8 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.