Cross-format content adaptation. Turning one substantial piece into many derivative formats (blog series, email sequences, social posts, webinars, podcasts, video shorts) without losing the original's value or producing AI-slop variants. The discipline of adaptation per medium rather than mass-blast distribution. Triggers on content repurposing, content adaptation, cross-format content, content atomization, content multiplication, content distribution across formats, source-piece-to-derivative, video shorts from blog, email from whitepaper, podcast from article, blog series from research. Also triggers when a flagship piece is shipping but the team has not planned how to extend it across formats, when repurposing is happening but the derivatives feel mass-produced, or when AI-assisted repurposing is producing slop variants of strong source pieces.
53
60%
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/content-repurposing/SKILL.mdQuality
Discovery
100%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 defines its niche in cross-format content adaptation. It excels at listing concrete actions, providing extensive natural trigger terms including format-to-format examples, and explicitly defining both what the skill does and when it should be used. The situational triggers (e.g., 'when repurposing is happening but the derivatives feel mass-produced') add valuable context for skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and derivative formats: 'blog series, email sequences, social posts, webinars, podcasts, video shorts' and describes specific transformations like 'video shorts from blog, email from whitepaper, podcast from article, blog series from research'. | 3 / 3 |
Completeness | Clearly answers both 'what' (turning one piece into many derivative formats without losing value) and 'when' (explicit trigger terms plus situational triggers like 'when a flagship piece is shipping but the team has not planned how to extend it across formats'). The 'Triggers on' clause serves as an explicit 'Use when' equivalent. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'content repurposing', 'content adaptation', 'content atomization', 'content multiplication', and concrete format-to-format phrases like 'video shorts from blog', 'email from whitepaper'. These are terms users would naturally use when requesting this kind of work. | 3 / 3 |
Distinctiveness Conflict Risk | Occupies a clear niche around cross-format content adaptation specifically. The focus on repurposing/adaptation across formats with anti-slop quality emphasis distinguishes it from general content creation, social media, or copywriting skills. The specific format-to-format triggers further reduce conflict risk. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
20%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads as a strategic essay or editorial philosophy document rather than an actionable skill for Claude. It excels at framing the problem space and identifying failure modes but provides almost no concrete, executable guidance—no templates, no worked examples of actual transformations, no step-by-step workflows. The extreme verbosity (~3000+ words of conceptual explanation) wastes token budget on ideas Claude already understands while omitting the specific, actionable content that would make the skill useful.
Suggestions
Replace conceptual explanations with concrete worked examples: show an actual 200-word source paragraph being adapted into a LinkedIn post, an email, and a video short script, with annotations on what changed and why.
Cut the opening philosophy (first 3 paragraphs), the 'What this skill is for' section's extensive skill-suite mapping, and the closing section—these consume ~800 tokens of context Claude doesn't need.
Add a concrete step-by-step workflow: 'Step 1: Run source-piece selection audit (criteria X, Y, Z). Step 2: Choose derivative formats using [decision matrix]. Step 3: Draft derivatives using [per-format template]. Step 4: Run voice audit. Step 5: Run litmus test per derivative.'
Move the per-format constraints, voice consistency details, and sequencing patterns entirely into the referenced files rather than covering them substantially inline—the main skill should be a concise overview pointing to these references.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~3000+ words. Extensive explanations of concepts Claude already understands (what mass-blast is, why repurposing matters, what each format is). The opening 3 paragraphs are pure context-setting that Claude doesn't need. Per-format constraints section explains basic facts about email, video, and podcasts. The closing section restates points already made. Most sections could be cut by 60-70% without losing actionable value. | 1 / 3 |
Actionability | The skill is almost entirely conceptual framing and strategic philosophy with no concrete, executable guidance. There are no code examples, no templates, no specific prompts, no fill-in-the-blank structures, no worked examples showing actual source text transformed into a derivative. The 'format adaptation patterns' section describes what adaptations are but never shows one being done. A reader finishes knowing the theory but not how to execute any specific repurposing task. | 1 / 3 |
Workflow Clarity | The 12-consideration framework provides a reasonable checklist, and the sequencing section outlines clear patterns. However, there is no step-by-step workflow for actually executing a repurposing project—no 'Step 1: do X, Step 2: validate Y' sequence. The failure modes section provides diagnostic value but no validation checkpoints within the actual repurposing process. The 'litmus test' is a useful checkpoint but is buried in prose rather than positioned as a workflow gate. | 2 / 3 |
Progressive Disclosure | The skill references 9 separate reference files with clear descriptions, which is good structure. However, the main SKILL.md itself is far too long—much of the per-format constraints, voice consistency, and sequencing content should live entirely in the referenced files rather than being substantially covered inline. The references are well-signaled but the body duplicates much of what should be deferred to them. No bundle files were provided to verify the references exist. | 2 / 3 |
Total | 6 / 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 | |
8e70d03
Table of Contents
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.