CtrlK
BlogDocsLog inGet started
Tessl Logo

linkedin-content

Use when someone wants to write, edit, or lint a LinkedIn post — a story, how-to, opinion piece, carousel script, video script, or poll — or wants an article, talk, or transcript repurposed into posts. Triggers on "write a LinkedIn post", "is this hook any good", "review my post", "turn this into LinkedIn posts", "carousel", "what format should this be". Lints posts 0-100 on mechanics, hook, integrity, and accessibility; picks the format the material actually supports; and splits long sources into standalone units with a reuse ledger.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 tight, well-structured skill body: concrete executable commands with exit-code semantics, a clear multi-step workflow with validation and feedback loops, and clean one-level-deep references that all resolve to real bundle files. No padding, no over-explanation.

DimensionReasoningScore

Conciseness

Lean and efficient throughout — opens with a pointed thesis, never explains concepts Claude already knows, and every editorial line ('Posts without pillars are noise', 'the one they repeat beats the one that scores higher once') encodes a real decision rather than padding.

5 / 5

Actionability

Copy-paste-ready commands with real flags and exit-code semantics — 'python3 scripts/format_picker.py --goal authority ...', 'python3 scripts/post_linter.py --input draft.md --has-image', exit 0/2/3 — covering the common cases fully rather than the minor-gap level of a 4.

5 / 5

Workflow Clarity

Five-step sequence with explicit validation checkpoints (linter exit 0 SHIP / 2 REVISE / 3 REWRITE) and a stated stop condition ('exit 0 or a stated decision to accept a warning'); the batch repurpose operation carries ledger validation, so the destructive/batch cap does not apply.

5 / 5

Progressive Disclosure

Overview body points to one-level-deep references — four references/, two assets/, three scripts/ — each clearly signaled with a description, and every linked path resolves to a real file in the bundle.

5 / 5

Total

20

/

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 that names concrete capabilities, supplies natural trigger phrases, and explicitly covers both what the skill does and when to use it. Voice and distinctiveness are clean, with no vague fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'write, edit, or lint', 'Lints posts 0-100 on mechanics, hook, integrity, and accessibility', 'picks the format', 'splits long sources into standalone units with a reuse ledger' — with comprehensive coverage rather than the minor gaps of a 4.

5 / 5

Completeness

Explicitly answers both 'what' (lint / pick format / split sources) and 'when' ('Use when someone wants...' plus 'Triggers on...') with concrete trigger phrases, the top anchor.

5 / 5

Trigger Term Quality

Includes natural phrases users actually say — 'write a LinkedIn post', 'is this hook any good', 'review my post', 'turn this into LinkedIn posts', 'carousel', 'what format should this be' — covering synonyms and variations, matching the comprehensive anchor rather than the few-missing of a 4.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear LinkedIn-specific niche with distinct triggers and minimal overlap risk; voice is third person ('Lints', 'picks', 'splits') with no first/second-person trigger phrasing to penalize.

5 / 5

Total

20

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
alirezarezvani/claude-skills
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.