Create platform-native content systems for X, LinkedIn, TikTok, YouTube, newsletters, and repurposed multi-platform campaigns. Use when the user wants social posts, threads, scripts, content calendars, or one source asset adapted cleanly across platforms.
84
84%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
92%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 that clearly articulates specific capabilities across named platforms and includes an explicit 'Use when' clause with natural trigger terms. The description uses proper third-person voice and lists concrete deliverables. The only minor weakness is potential overlap with general writing or marketing skills, though the platform-specific focus helps mitigate this.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'platform-native content systems', 'social posts, threads, scripts, content calendars', and 'one source asset adapted cleanly across platforms'. Names specific platforms (X, LinkedIn, TikTok, YouTube, newsletters) and concrete deliverables. | 3 / 3 |
Completeness | Clearly answers both 'what' (create platform-native content systems for specific platforms and repurposed campaigns) and 'when' (explicit 'Use when' clause specifying social posts, threads, scripts, content calendars, or cross-platform adaptation). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'social posts', 'threads', 'scripts', 'content calendars', 'repurposed', 'multi-platform', and specific platform names (X, LinkedIn, TikTok, YouTube, newsletters). These are terms users naturally use when requesting content creation help. | 3 / 3 |
Distinctiveness Conflict Risk | While it specifies social media content creation with named platforms, it could overlap with general writing/copywriting skills or marketing skills. The multi-platform and content calendar aspects help distinguish it, but 'content systems' is broad enough to potentially conflict with other content-related skills. | 2 / 3 |
Total | 11 / 12 Passed |
Implementation
70%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 content creation skill with clear workflows, good progressive disclosure, and a useful quality gate. Its main weakness is the lack of concrete examples—no sample posts, threads, or before/after transformations that would make the platform adaptation rules truly actionable rather than descriptive. The conciseness is decent but has room for tightening where guidance overlaps.
Suggestions
Add 1-2 concrete before/after examples showing a source claim adapted into an X post and a LinkedIn post to make platform rules actionable rather than descriptive.
Include a sample repurposing output showing how one anchor asset becomes 3 platform-native drafts, demonstrating the 7-step flow in practice.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient and avoids explaining things Claude already knows, but some sections could be tightened. For example, the 'Non-Negotiables' and 'Hard Bans' sections contain guidance that overlaps conceptually, and the voice handling section repeats the brand-voice reference multiple times. | 2 / 3 |
Actionability | The skill provides clear directional guidance (platform rules, hard bans, repurposing flow) but lacks concrete examples of actual outputs. There are no example posts, no sample thread, no before/after transformations showing what good vs bad looks like for each platform. The instructions describe rather than demonstrate. | 2 / 3 |
Workflow Clarity | The repurposing flow is clearly sequenced (7 steps), the source-first workflow establishes a clear starting point, and the quality gate serves as an explicit validation checkpoint before delivery. The voice handling section clearly specifies when to run brand-voice first, creating a proper decision tree. | 3 / 3 |
Progressive Disclosure | The skill is well-organized with clear sections, appropriate length for a SKILL.md overview, and clean one-level-deep references to related skills (brand-voice, crosspost, x-api). Content is logically structured from activation triggers through workflow to quality gates. | 3 / 3 |
Total | 10 / 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 | |
Reviewed
Table of Contents