rampstackco/claude-skills / skills/content-repurposing
content-repurposing
VerifiedCross-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.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 360 B |
| SKILL.md | skill md | 23.7 KB |
| references/aeo-extraction-patterns.md | markdown | 10.4 KB |
| references/common-repurposing-failures.md | markdown | 10.5 KB |
| references/cross-promotion-patterns.md | markdown | 9.5 KB |
| references/format-adaptation-patterns.md | markdown | 13.4 KB |
| references/per-format-constraints.md | markdown | 10.5 KB |
| references/repurposing-pipeline-templates.md | markdown | 11.4 KB |
| references/sequencing-and-cadence-patterns.md | markdown | 11.2 KB |
| references/source-piece-selection-criteria.md | markdown | 10.9 KB |
| references/voice-consistency-across-formats.md | markdown | 10.7 KB |
references/aeo-extraction-patterns.md
View on GitHub# AEO extraction patterns
FAQ extraction, snippet design, statistic extractions, entity extractions for AI search citation. The repurposing pattern that turns long-form content into AI-search-ready derivatives.
AI search engines (the citation-driven generative answer engines) cite content in specific shapes. Pieces that are designed for citation get cited at higher rates and with better framing control; pieces that are not designed for citation still get cited but at lower rates and with less control over how the citation appears.
The AEO (answer engine optimization) extraction is its own derivative format with its own conventions. Treating it as a derivative is the discipline.
---
## The AEO extraction frame
AI engines retrieve and cite content paragraph-by-paragraph or snippet-by-snippet. They favor content that:
- Has standalone meaning (the snippet works without surrounding context).
- Cites named sources within the snippet (specific authority).
- Uses specific phrasings (queryable framings).
- Has structural signals (FAQ schema, headings, lists where appropriate).
Source pieces written without these properties may have the same content but in shapes the engines do not cite cleanly. AEO extraction restructures the content into citation-ready shape.
---
## Pattern 1: FAQ extraction
The most common AEO extraction pattern.
**The shape.** Specific question-answer pairs derived from the source piece. Each Q&A is 40-80 words. Format as standalone FAQ entries.
**Question framing.**
- Use phrasings users actually search. "What is X?" "How does X work?" "Why does X matter?" "When should I use X?"
- Avoid phrasings users do not search. "What are the considerations around X?" rarely matches search intent.
- Specific is better than generic. "How long should a B2B sales email be?" performs better than "What length should sales emails be?"
**Answer framing.**
- Standalone meaning. The answer works as a paragraph; no pronoun references that depend on outside context.
- Named source within the answer where applicable. "According to a 2025 Forrester study, B2B sales emails between 75 and 150 words have the highest reply rates" performs better than "Studies show shorter emails work better."
- Specific framings, not hedged. "The strongest length is 75-150 words" performs better than "Generally, shorter tends to be better."
- Length: 40-80 words typical. Longer answers get truncated or cited partially; shorter answers may not have enough substance to cite.
**Where the FAQ lives.**
- A dedicated FAQ section at the bottom of the source piece, schema-marked with FAQPage.
- A standalone FAQ page that aggregates multiple FAQs across topics, deeply linked to source pieces.
- Inline within the source piece as a callout box, surfacing the Q&A while the surrounding prose develops the topic.
---
## Pattern 2: Snippet design
Standalone paragraphs in the source piece designed to be citation-ready.
**The shape.** A paragraph (100-200 words typical) that answers a specific query cleanly and can be cited as a unit.
**Snippet framing.**
- Opens with a specific claim or definition. Snippets that open with throat-clearing rarely get cited cleanly.
- Includes named source citations where the claims need authority.
- Uses specific framings. "B2B sales emails between 75 and 150 words have a 32% reply rate, compared to 18% for emails over 250 words" is citation-ready; "shorter emails tend to do better" is not.
- Stands alone. The paragraph's meaning does not depend on the prior or following paragraphs.
**Where snippets live.**
- Throughout the source piece as load-bearing paragraphs that incidentally meet snippet criteria.
- As deliberately-designed snippets in specific positions (often after each H2 question for AEO-optimized pieces; see `editorial-qa`'s SEO/AEO compliance for the answer-paragraph discipline).
- As standalone snippets in derivative pieces (FAQ pages, glossaries, knowledge-base entries).
---
## Pattern 3: Statistic extractions
AI engines weight statistics with named sources at high citation rates.
**The shape.** Specific statistic with named source, framed for citation.
**Statistic framing.**
- The number is specific. "32% of B2B buyers" performs better than "around a third of buyers."
- The source is named. "According to the 2025 Salesforce State of Marketing report" performs better than "according to a recent study."
- The context is clear. "Among B2B SaaS buyers in the $50M-500M revenue band" rather than just "among buyers."
- The currency is specified. The stat's date matters for AI engines deciding which sources to cite as current.
**Where statistic extractions live.**
- Throughout the source piece where data supports claims.
- In dedicated "key statistics" callouts that schema-mark the stats.
- As standalone tweet-graphic-style social derivatives (the stat on its own with the source citation).
- In FAQ-style answers that frame "what does the data say about X?"
**The citation-laundering avoidance.** Statistic extractions that cite secondary sources (other content marketing pieces) rather than primary sources reduce citation rates. AI engines increasingly detect citation laundering and discount it.
---
## Pattern 4: Definition and entity extractions
Source pieces often define specific terms or describe specific entities authoritatively.
**The shape.** Standalone definitions or entity descriptions that can serve as canonical references.
**Definition framing.**
- "X is [definition], typically [characterization], distinguished from [related concept] by [distinction]."
- 50-150 words for substantive definitions.
- Specific authority signals: who developed the concept, when, in what context.
**Entity framing.**
- For products, companies, frameworks: who, what, when, why, where used.
- Specific dates, named people, named organizations.
- Source attribution where the entity claim depends on authority.
**Where definition and entity extractions live.**
- Glossary pages. Many programs underuse glossaries; they are AI-search valuable real estate.
- Knowledge-base entries.
- Schema-marked definitions within source pieces (Article schema with appropriate sub-types).
- Wikipedia and similar entity authorities where the entity is significant enough to warrant external listings (different from on-property AEO but related; AI engines weight cross-source consistency).
---
## Pattern 5: Comparison extractions
Source pieces that compare options, frameworks, or approaches produce comparison-extraction derivatives.
**The shape.** Side-by-side or table comparisons with specific axes, citation-ready.
**Comparison framing.**
- Defined axes (price, feature set, fit, scale).
- Specific values per axis per option.
- Tradeoff summary that AI can quote.
- Recommendation framing where the source piece commits a position.
**Where comparison extractions live.**
- Tables within the source piece, schema-marked where appropriate.
- Standalone comparison pages.
- FAQ-style answers framing "How does X compare to Y?"
- Decision-guide derivatives that walk readers through the comparison.
---
## Pattern 6: How-to extractions
Source pieces with sequential instructions produce how-to extractions.
**The shape.** Step-by-step instructions that AI can cite as a procedure.
**How-to framing.**
- Numbered steps in a clear sequence.
- Each step is a complete instruction (not "do this, then that" run together).
- Schema-marked with HowTo where the source is an instructional piece.
**Where how-to extractions live.**
- Within source pieces as schema-marked procedures.
- Standalone how-to pages on specific tasks.
- Tutorial derivatives in video format.
---
## AEO extraction failures
**Generic FAQs.** Questions that do not match user search phrasings get little citation. Cure: query research; phrase questions in user voice.
**Context-dependent answers.** Answers that reference "this approach" or "the method described above" do not cite cleanly. Cure: each answer is rewritten to stand alone with full context.
**Hedged answers.** "Generally, in some cases, depending on context, X might work" rarely gets cited. AI engines prefer specific framings. Cure: where the source piece is genuinely uncertain, scope the answer to the specific case where the answer is specific.
**Missing schema.** FAQs and snippets without schema markup do not signal cleanly to engines. Cure: add appropriate schema (FAQPage, HowTo, Article) where formats fit.
**No source citations within answers.** Statistics and specific claims without named sources within the answer paragraph get cited at lower rates. Cure: include source citations within the answer body, not just in surrounding context.
**Citation laundering.** FAQs citing other content marketing pieces rather than primary sources. Cure: trace claims to primary sources; cite the primary.
**Over-extraction.** Producing 50 FAQs from a 5,000-word source piece dilutes; not every question deserves a standalone FAQ. Cure: extract the 10-15 highest-value questions; let the rest live within the source's prose.
---
## AEO extraction integration with the cross-format set
AEO extractions integrate with other derivatives.
**FAQ pages link to the source.** The FAQ page is a derivative; the source piece is the canonical version. Cross-promotion follows the standard pattern.
**Statistic extractions appear in social posts.** Each stat with its source citation can become a social post (often with quote-graphic visual treatment).
**Definition extractions appear in glossaries that the source piece links to.** The glossary entry serves as the canonical definition for the term across the program.
**Comparison extractions appear in decision-guide derivatives.** The comparison from the source becomes the spine of a separate decision-guide piece.
**The integration discipline.** AEO extraction is one derivative type among several; the cross-format set's coordination includes the AEO extractions, not as a separate workflow but as part of the rollout plan.
---
## Methodology-level choices that stay in the public skill
The six AEO extraction patterns, the question/answer/snippet framing principles, the schema markup integration, the AEO extraction failures, the integration with the broader cross-format set.
## Implementation choices that stay internal
Specific schema markup automation. Specific FAQ-page templates in the team's CMS. Specific glossary-page architecture. Specific statistic-extraction tooling. Specific monitoring of AI citation rates per piece. The team's own conventions for FAQ length within the bands. These vary by team, CMS, and AI-citation tracking infrastructure.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |