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.
65
77%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/platforms/linkedin/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description excels at trigger term coverage and completeness, with an impressive list of natural keywords and a clear 'when to use' clause including disambiguation from a related skill. Its main weakness is the lack of specific concrete actions beyond 'create copy' and 'optimize' — listing capabilities like formatting, hashtag suggestions, or content structuring would strengthen specificity.
Suggestions
Add more specific concrete actions such as 'draft LinkedIn posts, optimize hashtags, structure carousel/document posts, craft hooks for engagement' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description mentions 'create LinkedIn post copy' and 'optimize for LinkedIn' as actions, but doesn't list specific concrete capabilities like formatting, hashtag generation, audience targeting, or content structuring. The actions are somewhat generic. | 2 / 3 |
Completeness | Clearly answers both 'what' (create LinkedIn post copy, optimize for LinkedIn) and 'when' (explicit 'Use when' triggers with extensive keyword list). Also includes a helpful disambiguation note directing LinkedIn ads to a different skill. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'LinkedIn post,' 'LinkedIn article,' 'professional post,' 'LinkedIn content,' 'LinkedIn copy,' 'B2B LinkedIn,' 'LinkedIn engagement,' 'document post,' 'poll,' 'Newsletter,' 'reshare,' and more. These are terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche (LinkedIn organic content) and explicit disambiguation from 'linkedin-ads' for paid content. The extensive list of LinkedIn-specific trigger terms makes it unlikely to conflict with general social media or other platform skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive LinkedIn content skill with strong actionability—concrete specs, clear output format, and useful reference tables. Its main weakness is length: the SEO/GEO sections, profile modules, and platform positioning comparisons add significant bulk that could be split into referenced files, and some content explains things Claude already understands about LinkedIn as a platform. The workflow could benefit from explicit validation steps for character counts and hook quality.
Suggestions
Move the SEO/GEO sections and Profile Modules table into a separate referenced file (e.g., LINKEDIN-SEO.md) to reduce the main skill's token footprint while preserving the information.
Remove or significantly trim the Platform Positioning table—Claude already understands LinkedIn's professional context and doesn't need a comparison matrix against Meta/X/TikTok.
Add a validation checkpoint to the output format workflow, e.g., 'Verify first line is ≤210 chars, total post is within target range for content type, and post type matches content depth.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains useful information but is verbose in several areas. The Platform Positioning comparison table explains things Claude already knows (what LinkedIn vs Meta/X/TikTok are for). The SEO/GEO sections are extensive and could be split into referenced files rather than inline. Some sections like Profile Modules duplicate information already covered in the SEO section. | 2 / 3 |
Actionability | The skill provides concrete, actionable guidance: specific character limits, exact image dimensions, a clear output format template (first line ≤210 chars, full post with character count, hashtags, image specs, form note), and an actionable SEO/GEO checklist. The output format section gives agents a clear deliverable structure. | 3 / 3 |
Workflow Clarity | The output format section provides a clear sequence for generating copy, and the content is logically organized from post types → platform context → specs → output. However, there's no validation or feedback loop—no step to verify character count compliance, check hook effectiveness, or validate that the chosen post type matches the content. For a content generation workflow, a review/validation checkpoint would strengthen this. | 2 / 3 |
Progressive Disclosure | The skill references related skills (linkedin-ads, open-graph, entity-seo, etc.) and external links, which is good. However, the SEO/GEO sections, Profile Modules table, and Platform Positioning comparison are all inline and quite lengthy—these would be better as separate referenced files. The skill is over 200 lines with substantial content that could be offloaded, making the main file heavier than necessary. | 2 / 3 |
Total | 9 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- kostja94/marketing-skills
- Commit
c099845
- 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.