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.
78
73%
Does it follow best practices?
Impact
Pending
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 capability descriptions could be more concrete—listing specific deliverables rather than general categories like 'platform-specific strategies.' Overall, it would perform well in a multi-skill selection scenario.
Suggestions
Replace general phrases like 'platform-specific strategies' and 'content creation' with more concrete actions such as 'write LinkedIn posts, draft Twitter threads, build content calendars, suggest hashtags, adapt long-form content into short-form posts.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (social media content) and some actions like 'creating, scheduling, or optimizing' and '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 trigger guidance with 'Use when the user wants help...' and 'Also use when the user mentions...' clauses with specific trigger terms). | 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 carves out a clear niche around social media content specifically, with platform-specific mentions and social-media-specific trigger terms like 'content calendar,' 'social scheduling,' and 'viral content' that are unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
57%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 social media content skill that is well-organized with good progressive disclosure and clear section structure. However, it suffers from verbosity—much of the content (engagement tips, hook formulas, analytics basics) is general social media knowledge Claude already possesses. The skill would benefit from being more concise and providing more concrete, executable examples like actual sample posts rather than abstract frameworks.
Suggestions
Cut sections covering general social media knowledge Claude already knows (engagement etiquette, basic analytics definitions, generic advice like 'respond to comments') to reduce token usage by ~40%.
Add concrete example outputs: include 2-3 actual sample posts per platform showing the hook formulas and content pillars in action, so Claude can pattern-match rather than interpret abstract frameworks.
Add validation checkpoints to workflows, such as 'Review post against platform character limits' or 'Check hook against engagement criteria before finalizing' to improve workflow clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite long (~300 lines) and includes substantial content that Claude already knows (engagement strategies, basic social media advice like 'respond to comments,' generic hook formulas). While organized, much of this is general social media knowledge that doesn't need to be spelled out in this detail. | 2 / 3 |
Actionability | The skill provides structured frameworks (content pillars, calendars, hook formulas) which are useful templates, but lacks concrete executable examples. There are no actual sample posts, no specific tool commands for scheduling, and the guidance remains at the strategic/advisory level rather than providing copy-paste ready outputs. | 2 / 3 |
Workflow Clarity | Several workflows are listed (repurposing workflow, batching strategy, daily engagement routine) with clear sequences, but they lack validation checkpoints. For instance, the content creation workflow doesn't include review/quality checks, and the repurposing workflow has no step to verify platform-specific formatting is correct before scheduling. | 2 / 3 |
Progressive Disclosure | The skill effectively uses progressive disclosure with clear references to separate files (references/platforms.md, references/post-templates.md, references/reverse-engineering.md) that are well-signaled and one level deep. The main file serves as an overview with appropriate depth, pointing to detailed resources for specific topics. | 3 / 3 |
Total | 9 / 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
05d40bb
- 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.