Execute distribution-first content creation

When to Activate

• You're planning content creation and need to maximize distribution effectiveness
• Content has failed to gain traction using traditional "create then promote" approaches
• You need predictable, channel-specific content performance
• You're working in competitive/saturated content spaces where generic promotion fails

Core Knowledge

The fundamental shift: Distribution is not the final step—it's the first. You reverse-engineer a single distribution channel's success patterns and embed those characteristics into the content from ideation forward.

Why this matters: Modern content ecosystems are crowded. Search results are saturated, social platforms restrict organic reach, and audiences are discerning. Shotgun promotion (sharing one article across many channels) no longer works. Content must be shaped for a specific channel to break through.

Channel-specific success patterns to reverse-engineer:

Organic Search (Google):

• Place lucrative keywords in <h2> headers to rank for multiple high-volume terms simultaneously
• Use HTML tables to trigger featured snippets (search-engine and user-friendly formatting)
• Strategic use of length to capture long-tail variants (not padding—each section targets specific keyword clusters)
• Example: AdEspresso's "Instagram Hashtags for Every Day of the Week" ranked for 4,100 keywords by structuring headers as [monday hashtags], [tuesday hashtags], etc.

Twitter:

• Round-up formats create natural tagging opportunities
• Feature contributors prominently to incentivize re-sharing
• Engage hyper-active niche communities (position as community service, not marketing)
• Example: SFOX's Bitcoin Cash guide tagged industry figureheads, generating 42 retweets and thousands of impressions in crypto community

Hacker News:

• Novel angles on well-known concepts (audience is marketing-savvy; avoid tired formulas)
• Strong opinions that spark discussion (opinion over fact drives comments)
• Piggyback platform darlings (Bezos, Musk, Buffett)
• Example: Slab's Bezos narrative article generated 14,477 pageviews in one day

Trade-offs to understand:

• One piece cannot serve two masters—Twitter-optimized content may underperform in search
• Traffic patterns differ: Hacker News spikes then dies; organic search starts slow and builds
• Set appropriate expectations in reporting based on channel

Constraints / Hard Rules

• Select exactly ONE primary distribution channel per piece of content
• Do not create content first and then decide where to promote it
• Do not add channel-specific elements as afterthoughts—they must be foundational to the concept
• Do not use round-ups unless they create genuine tagging/sharing incentives
• Do not create length for its own sake—only when it serves channel-specific goals (like long-tail keyword capture)

Workflow

1. Select single distribution channel

   • Choose based on audience overlap and strategic priority
   • Commit fully—this determines everything that follows

2. Reverse-engineer channel success patterns

   • Study 5-10 high-performing pieces in that channel
   • Document common structural elements (headers, formatting, length, opinion vs. fact)
   • Identify audience preferences (topics, angles, contributors, timing)
   • Note technical requirements (HTML tables for snippets, tagging mechanisms, etc.)

3. Develop channel-tailored concept

   • Start with a concept that naturally fits identified success patterns
   • For search: Map keyword clusters to header structure before writing
   • For Twitter: Identify taggable contributors and active communities first
   • For Hacker News: Find novel angle on known topic or timely hook to platform darling

4. Embed channel characteristics into structure

   • Build technical elements into foundation (tables, headers, etc.)
   • Shape voice and opinion level to channel norms
   • Plan length strategically for channel goals
   • Create natural promotion mechanisms (tags, shareability, discussion prompts)

5. Execute content creation

   • Write with distribution mechanisms already in place
   • Every element (thesis, sub-headers, voice, examples) serves channel fit

6. Promote within chosen channel

   • Use built-in mechanisms (tags for Twitter, timely submission for HN)
   • Activate contributors if using round-up format
   • Set reporting expectations based on channel traffic patterns

Output Contract

When executing this skill, you produce:

Channel Selection Document:

• Primary distribution channel with justification
• Expected traffic pattern (spike vs. build)
• Success metrics appropriate to channel

Reverse-Engineering Analysis:

• 5-10 high-performing examples from chosen channel
• Common structural characteristics documented
• Audience preferences mapped
• Technical requirements listed

Content Blueprint:

• Concept tailored to channel success patterns
• Structural elements embedded (header keywords, HTML tables, tagging opportunities, etc.)
• Built-in promotion mechanisms identified
• Length and voice specifications matched to channel

Execution-Ready Brief:

• All channel-specific elements defined before writing begins
• Clear success criteria based on channel norms
• Promotion approach that leverages built-in mechanisms

---

Source: Content Promotion: The Secret to Distributing Content Is Hidden in Plain Sight