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

82%

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

The canonical home for this skill is content-repurposing in rampstackco/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

65%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 skill with concrete per-format guidance, worked examples, runnable audits, and exemplary progressive disclosure into nine real reference files. The main gaps are a missing ordered workflow tying the considerations into a sequence with validation checkpoints, and noticeable repetition of the mass-blast examples across the intro, framing, and failure-modes sections.

Suggestions

Add an explicit ordered workflow (e.g., select source piece, choose derivative formats, adapt per format, run per-derivative audits, plan sequencing and cadence, set up cross-promotion) with the existing audits placed as validation checkpoints, rather than presenting the material only as parallel considerations and delegating sequences to references/repurposing-pipeline-templates.md.

Tighten the redundancy between the intro paragraphs, the 'One-and-done vs mass-blast vs adapt-by-format' section, and the failure-modes list, which repeat the same mass-blast examples (newsletter as blog's first three paragraphs, article read aloud) three times — consolidate each example into one location and cross-reference it.

State the litmus test and the 12-consideration framework as an ordered end-of-work review checklist (with the closing section's questions merged in) so a completed repurposing plan has a single verification pass instead of three scattered ones.

DimensionReasoningScore

Conciseness

Mostly efficient, domain-specific editorial content, but the same mass-blast examples are repeated three times ("email newsletter is the blog's first three paragraphs" in the intro, the keystone-framing section, and the failure-modes list; likewise the article-read-aloud-as-video/podcast example), and the closing section restates the framework's litmus questions. This is more than the anchor-4 "minor instances" of trimming but short of anchor 2's pervasive padding.

3 / 5

Actionability

Concrete, specific guidance throughout: eight adaptation patterns with worked examples ("A 1,500-word blog post... becomes a 5-email sequence, one email per step"), per-format constraints with numbers ("200-800 words", "hook in the first 1-2 seconds", "60-90 second window"), and runnable audits. As an instruction-only skill this is actionable without code, but guidance is editorial direction rather than fully copy-paste-ready artifacts, so anchor 5's "fully executable" is not quite met.

4 / 5

Workflow Clarity

Audits exist (selection audit, litmus test, voice audit, pacing audit) and the 12 considerations act as a checklist, but there is no ordered end-to-end sequence (e.g., select source, choose formats, adapt, audit, sequence, cross-promote) — the pipeline workflows are delegated to a reference file rather than sequenced in the body, leaving checkpoints implicit. Not anchor 4, which requires a clear sequence with most checkpoints present; the destructive/batch cap does not apply since repurposing is not a destructive operation.

3 / 5

Progressive Disclosure

The body is an overview with nine one-level-deep references, each clearly signaled inline ("Detail in [references/...]") and indexed in a Reference files section with descriptions; all nine referenced files exist in the bundle. This matches the anchor-5 pattern of a clear overview with well-signaled single-level references and easy navigation.

5 / 5

Total

15

/

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 capabilities, a comprehensive natural-language trigger list with synonyms and task phrasings, and explicit what-and-when structure. The only notable weakness is that the "content distribution across formats" trigger phrase risks firing for the related content-distribution skill.

DimensionReasoningScore

Specificity

"Turning one substantial piece into many derivative formats (blog series, email sequences, social posts, webinars, podcasts, video shorts)" names the domain and enumerates several concrete derivative formats. It falls short of the anchor-5 example's multiple distinct executable actions (extract, fill, merge, convert) because this is one transformation action with format variations, and derivative types like FAQ extraction are omitted.

4 / 5

Completeness

The what is explicit ("Cross-format content adaptation. Turning one substantial piece into many derivative formats") and the when is explicit with concrete trigger phrases ("Triggers on content repurposing..." plus "Also triggers when a flagship piece is shipping but the team has not planned how to extend it across formats"). This clearly matches the anchor-5 example structure of both what and when with concrete trigger phrases.

5 / 5

Trigger Term Quality

"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" is comprehensive natural-term coverage with many synonyms and concrete task phrasings users would actually say, matching the anchor-5 example's breadth (file extensions are not applicable to this domain).

5 / 5

Distinctiveness Conflict Risk

Core triggers ("content repurposing", "source-piece-to-derivative", "email from whitepaper") are distinct, but including "content distribution across formats" as a trigger creates minor overlap risk with the sibling `content-distribution` skill — a distinction the body itself calls load-bearing. Not anchor 5 ("minimal conflict risk") because of that overlap; clearly not anchor 3, whose examples are vague single-format phrases with no niche.

4 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

rampstackco/claude-skills

Path

dist/codex/.agents/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.