Name: linkedin-strategy
Rating: 76 (1 reviews)
Author: alirezarezvani

linkedin-strategy

Use when someone needs a LinkedIn plan rather than a post — content pillars, positioning for a career change or consulting or thought leadership, a sustainable posting cadence, or a newsletter decision. Triggers on "what should I post about", "how often should I post", "LinkedIn content strategy", "should I start a LinkedIn newsletter", "grow my following", "90-day plan". Validates the positioning brief, sizes the week against real hours and refuses a plan that will not survive week five, and gates a newsletter against eligibility and a six-month cadence commitment.

Quality

96%

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-strategy in alirezarezvani/claude-skills

Quality

Content

92%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 concise, highly actionable, and sequenced with explicit validation gates, but it depends entirely on a referenced bundle (scripts, references, assets) that is absent, so its progressive-disclosure pointers are broken.

Suggestions

Ship the referenced bundle — create scripts/positioning_brief.py, scripts/cadence_planner.py, and scripts/newsletter_planner.py so the documented commands actually execute.

Add the three references/*.md and two assets/* files (positioning_brief_template.md, example_brief.json) the body links to, or remove the broken links and inline the minimal necessary content.

Until the bundle exists, note in the body that the scripts are illustrative/expected so a reader is not sent to nonexistent paths.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it never explains what LinkedIn, a newsletter, or a pillar is — and dense operational lines like "a positioning that excludes nothing is availability" encode decision rules rather than padding, matching the lean-and-efficient anchor.	5 / 5
Actionability	Three copy-paste-ready commands with full flags and documented exit codes (0 fits / 2 below floor / 3 over budget) cover the common cases for each decision, matching the fully-executable anchor.	5 / 5
Workflow Clarity	A clearly ordered three-decision sequence ("Three decisions, in this order") where each step carries an explicit refusal gate with feedback — step 1 refuses invalid objectives/audiences, step 2 refuses sub-90-minute weeks, step 3 refuses ineligible newsletters — matching the explicit-validation-and-feedback-loops anchor.	5 / 5
Progressive Disclosure	Structure and signaling are good (overview body plus a Scripts table, References, and Assets sections with one-level-deep links), but every referenced bundle path — scripts/.py, references/.md, assets/* — points to files and directories that do not exist, so navigation is signaled but leads nowhere, a material rather than minor organization gap.	3 / 5
	Total	18 / 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.

A strong, specific description with explicit trigger phrases and concrete capabilities covering all three decisions, written in third person. It clearly answers both what and when with minimal conflict risk.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions across all three sub-decisions — "Validates the positioning brief", "sizes the week against real hours", "refuses a plan that will not survive week five", "gates a newsletter against eligibility and a six-month cadence commitment" — matching the comprehensive-coverage anchor.	5 / 5
Completeness	Opens with an explicit "Use when someone needs a LinkedIn plan rather than a post" clause (the when) plus concrete "Triggers on..." phrases, and states the what (pillars, positioning, cadence, newsletter; validates/sizes/refuses/gates), satisfying the anchor for clearly answering both what and when with concrete triggers.	5 / 5
Trigger Term Quality	Explicit quoted natural triggers ("what should I post about", "how often should I post", "LinkedIn content strategy", "should I start a LinkedIn newsletter", "grow my following", "90-day plan") give comprehensive coverage with synonyms, matching the anchor for comprehensive natural-term coverage.	5 / 5
Distinctiveness Conflict Risk	The niche is LinkedIn strategy (a plan vs. a post) with triggers specific to strategy-level questions, clearly distinct from post-drafting or analytics skills; conflict risk is minimal, matching the clear-niche anchor.	5 / 5
	Total	20 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 8 missing	Warning
referenced_paths_exist	Referenced path issues: 19 missing	Warning

	Total	14 / 16 Passed

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

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