All skills
coreyhaines31 avatar

/content-strategy

@c4800ba

When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "what content should I create," "blog topics," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce, not just writing it. For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media content specifically, see social.

Use this Skill: https://skilld.dev/gh/coreyhaines31/marketingskills/content-strategy

This session only. Nothing lands on disk.

referencescontent-distribution.md

≈1.4k tokens on demand. Your agent reads this file only when SKILL.md points to it.

Content Distribution Spine

The "distribute" half of content strategy. Creating a great piece is table stakes; the leverage is in getting it seen. This reference expands the Create Once, Distribute Twice section of the skill.

Cross-links: ORB channel-type playbook lives in launch; atomization/repurposing workflows (podcast → clips, blog → thread) live in social. This file consolidates the strategy that ties them together—don't re-derive ORB from scratch here.

Create Once, Distribute Twice

One exceptional piece, reformatted across channels—not a fresh piece per platform. The math is simple: a flagship piece plus ten repurposed cuts reaches far more people than eleven mediocre native posts, at a fraction of the effort.

The discipline is designing the piece to be distributed:

  • Write subheads that read as standalone social posts.
  • Structure sections modularly so they can be lifted out and stand alone.
  • Pre-identify the pull quotes, stats, and frames you'll turn into graphics or short clips.
  • Know the atomized outputs before you write, so the source piece contains them.

Treat the flagship as the master; every channel gets a cut derived from it.

The ORB Framework as a Funnel

Own, Rent, Borrow—read as a discovery → engagement → conversion funnel:

Layer Channels Funnel role You control
Borrowed Podcasts, guest posts, partnerships, PR, other people's audiences Discovery / breakthrough Nothing—it's a loan
Rented Social platforms, ad networks, marketplaces Engagement / reach The content, not the audience or algorithm
Owned Email list, blog, community, app Conversion / retention Everything—the durable asset

The strategic move: use borrowed and rented reach to funnel strangers into owned channels where you can convert and retain them. Borrowed and rented are rented land; owned is the only asset you keep.

The Ownership Paradox

Most teams invert the priority: they spend ~90% of effort on borrowed and rented channels they don't control, and neglect the owned assets that actually convert. The paradox is that the channels getting the least attention (email, blog, community) are the ones that compound and can't be revoked. Rebalance toward owned as the destination for all upstream effort.

Failure Modes

  • Spray-and-pray — publishing across every platform with no flagship and no repurposing system. Effort scatters; nothing compounds; each post starts from zero.
  • Platform dependency — building your audience on rented land. Facebook organic reach collapsed from ~20% to under 2% as the platform monetized. Any rented channel can throttle, deprioritize, or de-platform you with no recourse. The lesson isn't "avoid rented"—it's "never let rented be the endpoint."

Platform Half-Lives

Content decays at wildly different rates by channel. Match the piece to the channel's shelf life:

Channel Rough half-life Implication
Twitter/X post Minutes–hours Post often; repost; thread for reach
Instagram / Facebook ~a day Frequent cadence; stories are ephemeral by design
LinkedIn post ~a day, longer for strong performers Fewer, higher-effort posts
TikTok / Reels / Shorts Days–weeks (algorithmic resurfacing) Evergreen hooks can re-surface long after posting
YouTube video Months–years Search-driven; compounds like a blog post
Blog post / SEO Years The long tail; the compounding asset
Email Sent once, but archived / repurposable One-shot attention; harvest into other formats

Short half-life channels reward frequency and repetition; long half-life channels reward depth and evergreen framing. Owned, long-half-life formats (blog, YouTube, email archive) are where distribution effort compounds.

The Content Distribution Flywheel

Distribution isn't a linear checklist—it's a loop that feeds itself:

  1. Create one exceptional flagship piece (guide, video, podcast, original research), with distribution hooks built in.
  2. Atomize it into channel-native cuts—clips, threads, carousels, quote graphics, email, subhead-posts.
  3. Distribute across owned → rented → borrowed, routing everything back to owned.
  4. Engage with the responses; capture the questions, objections, and reactions.
  5. Feed back — the engagement surfaces the next flagship topic (what resonated, what got asked), and top-performing atoms signal what to make more of.

Each turn of the loop lowers the cost of the next piece (you learn what lands) and grows the owned audience that amplifies it. The flywheel is why consistent distributors pull away from one-off publishers over time.

Atomization Checklist (per flagship)

For each major piece, produce (see social for the platform-native execution):

  • 3–5 standalone social posts from the subheads/key points
  • 1 thread (Twitter/X) or carousel (LinkedIn/Instagram) of the core argument
  • 2–4 short-form video clips (if source is video/podcast)
  • 1–2 quote or stat graphics
  • 1 email to the owned list linking the flagship
  • Repost/reshare schedule across the piece's half-life (don't post once and move on)

Related

  • launch — ORB channel-type playbook and launch-day distribution
  • social — atomization/repurposing workflows and platform-native execution
  • emails — the owned channel that converts distributed attention
  • ai-seo — making owned content citable by LLMs (another distribution surface)

Source: SKILL.md on GitHub

1 warning17d5 checks · Risk SAFE
  • Gen Agent Trust Hub17d

    The content-strategy skill is a purely instructional framework for planning marketing and SEO content. It contains no executable code, scripts, or remote dependencies. The skill follows standard agent patterns for context gathering and provides structured methodologies for content prioritization and distribution.

  • Socket17d

    No alerts

  • Snyk17d

    Risk: MEDIUM · 1 issue

  • Runlayer6mo

    2 files scanned · No issues

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at c4800ba. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 hours ago.

Activeupdated last month
metadata
{
  "version": "2.1.1"
}
  • SEO
  • content-strategy
  • marketing
  • keyword-research
  • blog
  • editorial-calendar
  • content-planning
  • buyer-journey
  • topic-clusters

README badge

README badge for coreyhaines31/marketingskills/content-strategy

Helps plan what content to create by identifying topic pillars, prioritizing ideas based on search volume and customer research, and mapping content clusters across awareness, consideration, decision, and implementation stages. Use this skill when deciding content strategy, not for writing individual pieces or technical SEO audits.

Generated from the current SKILL.md.

Does this skill help with writing individual blog posts?
No. This skill focuses on planning what content to create and developing strategy. For writing individual pieces, use the copywriting skill.
Does this skill cover SEO technical audits?
No. For technical SEO and on-page optimization, use the seo-audit skill. This skill helps decide what topics to target, not audit existing pages.
What if I don't have keyword research data or customer call transcripts?
The skill guides you through gathering business context, customer research, and competitive analysis using web search and forum research (Reddit, Quora) to identify content ideas even without formal data.
Should I create dedicated pillar pages with custom URLs, or keep everything under /blog?
Most content works fine under /blog with good internal linking. Dedicated pillar pages with custom URL structures are only needed for comprehensive resources with multiple layers of depth.
How do I decide between creating searchable versus shareable content?
Prioritize searchable content first — it captures existing demand. Shareable content creates demand but works best as a secondary strategy. Content can target both.

Generated from the current SKILL.md. These answers refresh after source changes.