CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

76

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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.

A well-structured orchestrator body: executable gate and router commands with exit-code semantics, a clearly sequenced gate-before-drafting workflow with feedback loops, and accurate one-level-deep references to real bundle files. The only blemish is minor duplication between the body and the frontmatter (the Distinct-from section, safety banner vs. hard rules).

Suggestions

Drop the body's "Distinct from" section — it restates the frontmatter `distinct_from` field verbatim and spends ~7 lines on context already machine-readable at routing time.

Trim the portability banner's overlap with the "Hard rules" section ("No credentials, no API, no scraping" appears in both) to one authoritative location.

Reconcile the "17 stdlib-only Python scripts" claim with the two scripts actually bundled, or clarify that the other fifteen live in the sub-skills.

DimensionReasoningScore

Conciseness

The body is a lean router document with no concept explanations, but the "Distinct from" section duplicates the frontmatter `distinct_from` field and the portability banner partially repeats the "Nothing is automated and nothing is sent" hard rule — minor trimmable duplication that keeps it at the 4 anchor rather than the every-token-earns-its-place (5) anchor.

4 / 5

Actionability

Two copy-paste commands with verified flags ("python3 scripts/linkedin_policy_gate.py --text … --output human") are backed by documented exit-code semantics for every outcome (exit 4/3/0 and exit 0/2/3), a lane table mapping asks to sub-skills, and a concrete forcing-question list — fully executable guidance covering the common cases.

5 / 5

Workflow Clarity

Steps 1–3 are clearly sequenced (gate → route → forcing questions) with an explicit validation gate before any drafting, per-exit-code handling ("A REFUSE outranks any route below"), and error recovery ("name the rule, offer the substitute the gate prints, and route there instead") — matching the explicit-validation-and-feedback-loop anchor.

5 / 5

Progressive Disclosure

The body stays an overview and every referenced path is a real one-level-deep bundle file: both scripts (with role table), both references, and the asset, each with a one-line description of what it holds and when to open it — clear navigation with no nesting.

5 / 5

Total

19

/

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 deliverables across all five lanes, an explicit use-when clause with seven natural trigger phrases, third-person voice, and a stated refusal boundary that further sharpens its niche. No fluff despite its length — every clause adds a capability or a trigger.

DimensionReasoningScore

Specificity

The description lists 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" — spanning all five lanes with no coverage gaps, matching the comprehensive-coverage anchor rather than the minor-gaps (4) anchor.

5 / 5

Completeness

Both halves are explicit: what it does ("grow an organic LinkedIn presence", "Forks context to route to one of five sub-skills, and refuses automation, scraping, pods, and bulk DMs") and when, via an explicit "Use when" clause plus concrete quoted trigger phrases — the clear both-present-with-triggers anchor.

5 / 5

Trigger Term Quality

Seven natural user phrasings are quoted verbatim ("grow my LinkedIn", "fix my headline", "write a LinkedIn post", "what should I post about", "LinkedIn strategy", "connection request", "my reach dropped"), covering each lane a user would ask about; no common variations are missing, so this fits the comprehensive anchor rather than the few-missing (4) anchor.

5 / 5

Distinctiveness Conflict Risk

"organic LinkedIn presence" and the platform name appear in nearly every clause, and the triggers ("fix my headline", "my reach dropped") are platform-specific, giving it a clear niche with minimal overlap risk against generic marketing or multi-platform skills.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

Reviewed

Table of Contents

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.