CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

content-repurposing

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.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured editorial playbook: concrete quantified adaptation patterns, explicit audits as checkpoints, and exemplary progressive disclosure with all nine one-level-deep references verified to exist. The main cost is token weight — the opening framing duplicates the keystone section nearly verbatim, and some format constraints restate general knowledge.

Suggestions

Cut the duplicated mass-blast explanation: the intro (lines ~13-17) and the 'One-and-done vs mass-blast vs adapt-by-format' section describe the same failure mode in nearly identical words — keep one, compress the other to a one-line pointer.

Trim per-format constraints that restate general knowledge (e.g., 'bad audio kills retention', 'captions essential; many viewers watch without sound') and keep only the medium-specific guidance a competent writer would not already infer.

Merge the distributed audit steps (litmus test, voice audit, pacing audit) into a single ordered per-derivative review checklist with an explicit failure-recovery step, so the body's checkpoints form one workflow rather than scattered section-level tests.

DimensionReasoningScore

Conciseness

Mostly efficient but could be tightened: the mass-blast failure mode is explained twice in nearly identical words (intro paragraph "the email newsletter is the blog's first three paragraphs with 'read more' tacked on" vs. the keystone section's "Email newsletter is the blog's first three paragraphs"), and some per-format constraints restate knowledge Claude already has ("bad audio kills retention", "many viewers watch without sound"). Not a 2 because every section still carries program-specific framing and the detail is correctly pushed to reference files rather than inlined.

3 / 5

Actionability

Concrete, specific guidance throughout: quantified adaptation patterns ("A 6,000-word whitepaper becomes 4-6 standalone blog posts", "a 5-email sequence, one email per step", "30-45 minute webinar", "60-90 second video clips", "Each Q&A is 40-80 words"), a runnable selection audit, and failure modes paired with named cures ("Cure: rewrite for platform-native structure"). Not a 5 because the framing sections (one-and-done vs mass-blast) and the 12-consideration list describe discipline conceptually rather than demonstrating a full worked derivative transformation; not a 3 because the specific numbers and audit procedures go well beyond vague direction.

4 / 5

Workflow Clarity

The body presents a coherent progression (selection audit → format patterns → per-format constraints → voice audit → sequencing/cadence → cross-promotion → failure diagnosis) with explicit checkpoints: the litmus test ("Read each derivative as if you had not seen the source piece"), the per-derivative voice audit, and the pacing audit, plus a 12-consideration checklist for designing/auditing a program. Not a 5 because these audits are distributed per-section rather than integrated into one ordered procedure with feedback loops, and there is no explicit error-recovery step after an audit fails.

4 / 5

Progressive Disclosure

Each major section ends with a clearly signaled one-level-deep pointer ("Detail in [references/format-adaptation-patterns.md](…)"); all nine referenced files exist, contain no further nested references, and are indexed with descriptions in a closing Reference files section. The SKILL.md body stays at overview altitude while the detail lives in the bundle, making navigation easy.

5 / 5

Total

16

/

20

Passed

Description

91%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete format enumeration, comprehensive natural trigger terms including synonyms and situational triggers, and explicit what/when coverage. The only weaknesses are a minor conflict risk from borrowing a distribution-related trigger phrase and a single-action framing rather than multiple distinct capability verbs.

DimensionReasoningScore

Specificity

The description names the domain and enumerates six concrete derivative formats ("blog series, email sequences, social posts, webinars, podcasts, video shorts") plus the core action ("Turning one substantial piece into many derivative formats"), but centers on a single transformation action rather than multiple distinct concrete actions, leaving minor coverage gaps (e.g., FAQ/ebook extraction from the body is absent). Not a 5 because the action list is one verb with format examples; not a 3 because the enumerated formats make the capability concrete and broad.

4 / 5

Completeness

Explicitly answers both what ("Cross-format content adaptation. Turning one substantial piece into many derivative formats (…) without losing the original's value or producing AI-slop variants") and when ("Triggers on … Also triggers when a flagship piece is shipping but the team has not planned how to extend it across formats"), with concrete trigger phrases covering both keyword and situational invocations.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage with synonyms: "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" — these are phrases a user would actually say, spanning both noun-form and task-form triggers.

5 / 5

Distinctiveness Conflict Risk

The repurposing-vs-distribution niche is distinct ("The discipline of adaptation per medium rather than mass-blast distribution"), but listing "content distribution across formats" as a trigger term for this skill creates minor overlap risk with a sibling content-distribution skill. Not a 5 due to that overlap; clearly above 3 because the core triggers (repurposing, atomization, source-piece-to-derivative) are unambiguous.

4 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

rampstackco/claude-skills

Path

skills/content-repurposing/SKILL.md

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.