CtrlK
BlogDocsLog inGet started
Tessl Logo

linkedin-posts

When the user wants to create LinkedIn post copy or optimize for LinkedIn. Also use when the user mentions "LinkedIn post," "LinkedIn article," "professional post," "post to LinkedIn," "LinkedIn content," "LinkedIn copy," "B2B LinkedIn," "LinkedIn engagement," "LinkedIn feed," "share box," "document post," "poll," "Newsletter," "reshare," or "LinkedIn marketing." For LinkedIn ads, use linkedin-ads.

64

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/platforms/linkedin/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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-organized, reference-rich body with genuinely actionable numbers and a concrete output format, weakened by redundancy (overlapping length tables, repeated mobile stat), a knowledge-restating platform-comparison table, and ~40 lines of profile-SEO/GEO material inlined in SKILL.md that should be a separate reference file. As an instruction-only skill it needs no code, and its guidance is executable as written.

Suggestions

Delete or compress the "Platform Positioning" comparison table — that LinkedIn is professional and TikTok is entertainment is knowledge Claude already has; keep only the "Prioritize LinkedIn when" line.

Merge "Character Limits" and "Optimal Length by Content Type" into one table (they repeat the same ranges), and state the 88% mobile-browsing stat once instead of in both Image Specs and Best Practices.

Move the "Off-Site Search Visibility (SEO & GEO)" and "Profile Modules" sections into a separate reference file (e.g. references/seo-geo.md) linked from the body, keeping SKILL.md focused on post copy creation and output format.

DimensionReasoningScore

Conciseness

Tables keep most sections dense, but the "LinkedIn vs Meta / X / TikTok" positioning table restates common knowledge (LinkedIn is professional and real-name; TikTok is entertainment), the "Character Limits" and "Optimal Length" tables repeat the same 100–200 and 1,300–1,600 ranges, the 88%-mobile stat appears twice, and the ~40-line Off-Site SEO/GEO section drifts beyond post-copy creation. Mostly efficient with clear trimmable padding, matching anchor 3; not 2 because the bulk is genuinely useful reference data, not filler.

3 / 5

Actionability

Concrete, usable numbers throughout — 3,000-char limit, 210–235 first-line window, per-type length ranges, 1200×627 / 1200×1200 image dims, ≤10MB files, up to 20 carousel images — plus a numbered 5-item Output Format and a form-note convention. Per the instruction-skill note, absence of code is not penalized; it falls short of 5 only because there is no worked example post and some guidance stays soft ("a few, relevant" hashtags, "Often strong for reach").

4 / 5

Workflow Clarity

The Output Format section gives a clear numbered sequence of what to produce (first line ≤210 chars → full post with count → hashtags → image specs → form note), and post-type selection is tabulated. Checkpoints as such aren't needed since nothing is destructive or batch, so no cap applies; it is not 5 because the path from "user request" to "finished post" (pick type → match length → write hook → assemble per format) must be assembled by the reader rather than stated.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ all absent), and the ~180-line body inlines a ~40-line SEO/GEO-plus-profile-modules block that is tangential to post copy creation and belongs in a separate reference file. Section headers are clear and cross-skill references are well signaled, which lifts it above anchor 2's "minimal structure," but the single-file scope creep matches anchor 3's "content that should be separate is inline."

3 / 5

Total

14

/

20

Passed

Description

86%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 description with an explicit what/when structure, third-person voice, a comprehensive list of natural trigger terms, and an explicit boundary redirect to linkedin-ads. Its only real gap is thin capability coverage — it names just two actions (create/optimize) when the skill body covers post types, character limits, hooks, image specs, and SEO/GEO.

DimensionReasoningScore

Specificity

The description names the domain and two concrete actions — "create LinkedIn post copy or optimize for LinkedIn" — but goes no further (no mention of articles, polls, documents, image specs, or character-count handling that the skill actually covers). This matches anchor 3 (domain plus 1-2 concrete actions, not comprehensive); it is not 4 because several specific actions are missing, and not 2 because the actions named are genuinely concrete.

3 / 5

Completeness

It explicitly answers both questions: what ("create LinkedIn post copy or optimize for LinkedIn") and when ("When the user wants to... Also use when the user mentions [list]") with concrete trigger phrases. This matches anchor 5 exactly; voice is third-person about the user, so no voice penalty applies.

5 / 5

Trigger Term Quality

Fifteen quoted trigger phrases spanning natural synonyms users would actually say ("LinkedIn post," "post to LinkedIn," "LinkedIn copy," "B2B LinkedIn," "share box," "document post," "reshare," "LinkedIn marketing"). Coverage is comprehensive with variants; not 4 because very few natural phrasings (e.g. "write a LinkedIn post," "LinkedIn ghostwriting") are missing.

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche (organic LinkedIn content) and even handles the closest conflict explicitly — "For LinkedIn ads, use linkedin-ads" — but bare triggers like "poll," "Newsletter," and "professional post" could plausibly fire for other platforms' skills. Mostly distinct with minor overlap risk, matching anchor 4 rather than 5.

4 / 5

Total

17

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
kostja94/marketing-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.