social-content
When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms. Also use when the user mentions 'LinkedIn post,' 'Twitter thread,' 'social media,' 'content calendar,' 'social scheduling,' 'engagement,' or 'viral content.' This skill covers content creation, repurposing, and platform-specific strategies.
55
62%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./config/claude/skills/social-content/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 is a strong description with excellent trigger term coverage and clear completeness, explicitly stating both what the skill does and when to use it. The main weakness is that the specific capabilities could be more concrete—listing actions like 'write LinkedIn posts, create Twitter threads, build content calendars, suggest hashtags' would be more specific than the somewhat general 'content creation, repurposing, and platform-specific strategies.' Overall, it would perform well in a multi-skill selection scenario.
Suggestions
Replace general phrases like 'content creation, repurposing, and platform-specific strategies' with more concrete actions such as 'write LinkedIn posts, draft Twitter threads, build content calendars, suggest hashtags, adapt content across platforms.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (social media content) and some actions like 'creating, scheduling, or optimizing' and mentions 'content creation, repurposing, and platform-specific strategies,' but these are somewhat general rather than listing multiple concrete, specific actions (e.g., 'write LinkedIn posts,' 'create Twitter threads,' 'build content calendars'). | 2 / 3 |
Completeness | Clearly answers both 'what' (creating, scheduling, optimizing social media content, content creation, repurposing, platform-specific strategies) and 'when' (explicit 'Use when' clause with trigger terms and scenarios). The description opens with a 'When the user wants...' clause and includes an 'Also use when' clause. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'LinkedIn post,' 'Twitter thread,' 'social media,' 'content calendar,' 'social scheduling,' 'engagement,' 'viral content,' plus platform names like LinkedIn, Twitter/X, Instagram, TikTok, Facebook. These are terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | The description is clearly focused on social media content across specific platforms, with distinct trigger terms like 'LinkedIn post,' 'Twitter thread,' 'content calendar,' and 'viral content' that are unlikely to conflict with other skills. The niche is well-defined. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a comprehensive social media marketing guide than a focused skill for Claude. The vast majority of content covers general social media knowledge that Claude already possesses (platform characteristics, engagement best practices, analytics metrics), resulting in significant token waste. The structure is reasonable with some useful frameworks, but the content would benefit enormously from aggressive trimming to focus only on the specific patterns, templates, and decision trees that add value beyond Claude's existing knowledge.
Suggestions
Cut the content by 60-70% by removing general social media knowledge Claude already knows (platform descriptions, what metrics mean, generic engagement advice) and focus only on specific templates, decision trees, and the product-marketing-context integration.
Move hook formulas, content calendar templates, and engagement routines into the referenced bundle files (references/post-templates.md, etc.) and actually provide those bundle files to support progressive disclosure.
Add validation checkpoints to workflows — e.g., after creating content, check it against brand voice guidelines; after scheduling, verify posting times align with analytics data.
Make the skill more actionable by providing concrete output formats (e.g., 'When asked to create a LinkedIn post, output in this exact structure: [hook line] + [body with line breaks] + [CTA] + [hashtags]') rather than general strategic advice.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~300+ lines, much of which covers general social media strategy knowledge that Claude already knows (what platforms are best for, how to write hooks, engagement strategies, analytics metrics). Very little here is novel or specific enough to justify the token cost. | 1 / 3 |
Actionability | The content provides structured frameworks, templates, and specific formulas (hook examples, calendar templates, engagement routines) which are somewhat actionable. However, there's no executable code, no specific tool commands, and much of the guidance is strategic advice rather than concrete step-by-step instructions Claude can directly execute. | 2 / 3 |
Workflow Clarity | Several workflows are listed (repurposing workflow, batching strategy, daily engagement routine, reverse engineering steps) with numbered steps, but they lack validation checkpoints or feedback loops. There's no mechanism to verify content quality, check scheduling success, or iterate based on results within the workflows themselves. | 2 / 3 |
Progressive Disclosure | The skill references three external files (references/platforms.md, references/post-templates.md, references/reverse-engineering.md) which is good structure, but no bundle files are provided, so these references are broken. Additionally, a large amount of content that could be in reference files (hook formulas, engagement strategies, analytics details) is inline, making the main file bloated. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- freekmurze/dotfiles
- Commit
3974caa
- 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.