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 skill 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 and specific—listing particular actions rather than broad 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 'optimizing' with more concrete actions such as 'write LinkedIn posts, compose Twitter threads, design content calendars, adapt long-form content into platform-specific formats.'
| 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 'Use when' clause with specific trigger terms and scenarios). | 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 scoped to social media content across specific platforms with distinct trigger terms like 'LinkedIn post,' 'Twitter thread,' 'content calendar,' making it unlikely to conflict with other skills like general writing or marketing 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 well-structured social media content skill with good progressive disclosure and useful frameworks (hook formulas, content pillars, platform reference table). However, it's somewhat verbose for what Claude already knows about social media strategy, and the actionability could be improved with concrete output examples (e.g., a complete sample LinkedIn post from hook to CTA). The workflows would benefit from explicit validation or review checkpoints.
Suggestions
Add 1-2 complete example outputs showing a finished LinkedIn post and Twitter thread generated from a sample input, so Claude has concrete reference points for quality and format.
Trim sections that cover general social media knowledge Claude already has (e.g., 'Quality Comments' advice like 'Add new insight, not just Great post!' and basic analytics definitions) to reduce token usage.
Add a validation step to the repurposing and batching workflows, such as 'Review each adapted post against brand voice guidelines before scheduling' to ensure quality control.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly lengthy with some sections that could be tightened (e.g., the engagement strategy daily routine, analytics metrics lists, and content ideas sections contain advice Claude would already know). However, the tables and hook formulas add genuine value and aren't overly padded. | 2 / 3 |
Actionability | The skill provides structured frameworks (content pillars, hook formulas, calendar templates) which are useful, but lacks truly executable artifacts—there are no concrete code examples, no actual post drafts with before/after, and much of the guidance remains at the strategic/advisory level rather than copy-paste ready output templates. | 2 / 3 |
Workflow Clarity | Several workflows are listed (repurposing workflow, batching strategy, weekly review) with numbered steps, but they lack validation checkpoints or feedback loops. For example, the repurposing workflow doesn't include any quality check or review step before publishing, and the batching strategy has no verification that content aligns with brand voice or goals. | 2 / 3 |
Progressive Disclosure | The skill effectively uses one-level-deep references to separate files (references/platforms.md, references/post-templates.md, references/reverse-engineering.md) and keeps the main file as an overview with clear navigation signals. Related skills are also well-linked at the bottom. | 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
2c6f6e8
- 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.