ClaudeSuperPower
SubmitLog in

content-distribution

Skill

Content distribution as a discipline. Owned channels (newsletter, blog, social), earned channels (PR, syndication, mentions), paid channels (boosted posts, syndication networks), and the channel-fit decisions that distinguish strategic distribution from spam-everywhere. Audience-channel matching, co

151Content

Install

git clone https://github.com/rampstackco/claude-skills.git ~/.claude/skills/content-distribution

What is content-distribution?

Content distribution as a discipline. Owned channels (newsletter, blog, social), earned channels (PR, syndication, mentions), paid channels (boosted posts, syndication networks), and the channel-fit decisions that distinguish strategic distribution from spam-everywhere. Audience-channel matching, content-channel matching, distribution cadence. Triggers on content distribution, channel strategy for content, owned earned paid channels, content amplification, content promotion, audience-channel matching, content-channel matching, distribution cadence, syndication strategy, organic distribution. Also triggers when content is publishing but reach is low, when the team is distributing on every channel without strategy, or when the content program needs a distribution discipline rather than just publication.

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Inherit all session tools

Declares no tool restrictions — inherits every session tool

~203 tokens of context used while enabled, before you invoke anything

Trust

87/100 · Excellent

2 factors scored below maximum

Documentation

README · ~14 min read

Content Distribution

A senior editorial leader's playbook for content distribution as a discipline. Owned, earned, and paid channels matched to audience and content type, with the channel-fit decisions that distinguish strategic distribution from spam-everywhere or hope-and-pray.

Content distribution is half the work and gets a fraction of the attention. Most programs spend 90% of capacity on production and 10% on distribution; the resulting ratio of effort-to-reach is consistently poor. The teams producing content that reaches audiences are the ones who treat distribution as a real discipline: channels chosen for fit, cadence calibrated to audience attention, owned-earned-paid balance set by program strategy, and effectiveness measured per channel.

This skill is the channel discipline. Different from content-repurposing (which turns one piece into many formats), this skill is about getting content TO audiences via the right channels. The two skills compose: repurpose first, then distribute the right format on the right channel.

The voice is the senior editorial leader who has watched programs underperform because distribution was treated as posting-after-publishing rather than as the equal half of the work.

When to use this skill: building a distribution discipline for a content program, auditing why content publishes consistently but reach is low, calibrating owned-earned-paid balance, designing channel-fit decisions for a multi-format program.

What this skill is for

This skill spans channel selection, audience-channel matching, content-channel matching, and distribution cadence. The content suite distinction:

  • content-strategy decides what to produce.

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.

Subagents

All subagents →

agent-sdk-verifier-ts

Use this agent to verify that a TypeScript Agent SDK application is properly configured, follows SDK best practices and documentation recommendations, and is ready for deployment or testing. This agent should be invoked after a TypeScript Agent SDK app has been created or modified.

32.8K stars

comment-analyzer

Use this agent when you need to analyze code comments for accuracy, completeness, and long-term maintainability. This includes (1) after generating large documentation comments or docstrings, (2) before finalizing a pull request that adds or modifies comments, (3) when reviewing existing comments fo

32.8K stars

agent-sdk-verifier-py

Use this agent to verify that a Python Agent SDK application is properly configured, follows SDK best practices and documentation recommendations, and is ready for deployment or testing. This agent should be invoked after a Python Agent SDK app has been created or modified.

32.8K stars