multi-channel-publishing

Purpose

Produce a channel-ready content derivative from a source document — not a summary, but a structurally adapted compression that preserves the source's thesis, maintains evidence fidelity, and conforms to the target channel's format constraints, audience expectations, and hook conventions. The output is a publishable artifact with a compression log proving nothing was lost by accident.

When to Use / When NOT to Use

Use this skill when:

• Repurposing a long-form article (Substack, blog, thesis) into a LinkedIn post, conference abstract, podcast brief, newsletter, tweet thread, spoken script, or executive briefing
• Deriving a compressed format from a full argument (compression direction: long → short)
• Adapting content for a new audience or channel while preserving the core claim
• Producing a spoken script from written beats or a conference proposal
• Creating a distribution package (multiple derivatives from one source)

Do NOT use this skill when:

• You need to write the original long-form piece (use the source-appropriate writing methodology first — P2: Substack first, derivatives second)
• You need to combine multiple sources into one synthesis (use Narrative Building or Problem Framing)
• You need to translate between languages (this is structural adaptation, not linguistic translation)
• The source document is internal/confidential and the target channel is public (Context Gate will catch this, but flag it early)
• You need a generic summary for no specific audience or channel (summaries without channel constraints produce FM-1: Summary, Not Derivative)

Anti-inputs (what this skill does NOT handle):

• Original content creation from scratch (this skill DERIVES, it does not originate)
• Content strategy or editorial calendar planning (this is a single-derivation tool)
• SEO optimization (channel format rules include discoverability principles, but this is not an SEO skill)
• Visual design or layout (this produces text; design is a separate discipline)