rampstackco/claude-skills / skills/content-distribution
content-distribution
VerifiedContent 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.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 361 B |
| SKILL.md | skill md | 25.4 KB |
| references/audience-channel-matching.md | markdown | 10.2 KB |
| references/channel-taxonomy.md | markdown | 12.8 KB |
| references/common-distribution-failures.md | markdown | 11.7 KB |
| references/content-channel-matching.md | markdown | 9.2 KB |
| references/distribution-cadence-patterns.md | markdown | 10.4 KB |
| references/distribution-measurement.md | markdown | 10.8 KB |
| references/earned-channel-work.md | markdown | 10.8 KB |
| references/owned-channel-discipline.md | markdown | 11.0 KB |
| references/paid-promotion-patterns.md | markdown | 11.4 KB |
references/audience-channel-matching.md
View on GitHub# Audience-channel matching
Where audiences actually engage. Common audience-channel maps. The presence-vs-engagement distinction that prevents distributing on channels where the audience is technically present but not actually paying attention.
The first and most consequential distribution decision is which channels to invest in. Most programs over-invest in channels with high audience presence but low audience engagement, and under-invest in smaller channels where the audience is genuinely paying attention. The audit shifts capacity to where engagement happens.
---
## The presence-vs-engagement distinction
A channel where the audience is present is not necessarily a channel where the audience is engaging.
**Presence.** Members of the target audience have accounts on the platform. They could see the program's content if they encountered it.
**Engagement.** Members of the target audience are actively using the platform for the kind of content the program produces. They click; they comment; they share; they convert.
**The mismatch failure mode.** A B2B technical program publishing TikTok content. The audience may have TikTok accounts (presence), but the audience is on TikTok for entertainment, not for B2B technical learning (low engagement for the program's content). The presence creates a false signal that the channel might work; the engagement reality is that distribution capacity goes to a low-return channel.
**The audit question.** Not "is the audience on this channel?" but "is the audience consuming this kind of content on this channel?"
---
## Common audience-channel maps
Mappings that show up repeatedly across program types. Programs should still validate against their own audience research; the maps below are starting points.
### B2B technical audiences
Engineers, technical decision-makers, developer-influencers, technical product managers.
**High engagement.** LinkedIn (especially long-form posts and articles); X/Twitter (specific technical communities); industry-specific newsletters; specialized podcasts; specific subreddits and Discord servers; GitHub for code-adjacent content; technical conferences and analyst-influenced channels.
**Moderate engagement.** YouTube for tutorial and conference-talk content; Hacker News for specific topics; vendor-platform community sites (AWS, Azure, GCP forums; specific tool communities).
**Low engagement.** TikTok, Instagram, Facebook for the program's primary content. Some technical professionals consume these for entertainment but rarely for technical content.
### B2B executive audiences
C-suite, VPs, senior strategy leaders.
**High engagement.** LinkedIn (long-form posts, articles, sometimes video); specific executive newsletters and podcasts; analyst-influence channels (Gartner, Forrester); event-driven media (high-quality conferences, executive roundtables).
**Moderate engagement.** Industry-specific publications; some podcasts; X/Twitter for specific topics with executive commentary.
**Low engagement.** Most consumer-focused social platforms. Executives often have low time for content consumption; the channels where they engage are concentrated.
### Consumer mass audiences
Broad consumer demographics for B2C brands.
**High engagement.** Instagram, TikTok, YouTube, Facebook (varies by demographic age and interest). Email newsletter for engaged subscribers. Pinterest for visual-product categories. Specific subreddits for interest-driven topics.
**Moderate engagement.** X/Twitter (declining for many consumer demographics). LinkedIn (low for most consumer use cases).
**Low engagement.** Most B2B-oriented channels.
### Niche specialist audiences
Concentrated audiences within specific domains (cybersecurity professionals, fertility-tracking enthusiasts, specific hobby communities).
**High engagement.** Specific subreddits, Discord servers, specialized newsletters and podcasts. Often higher engagement on smaller channels than on broad platforms.
**Moderate engagement.** Domain-specific Twitter/X communities; some LinkedIn; YouTube for educational content.
**Low engagement.** Broad social platforms where the audience is small fraction of total platform population.
### Developer audiences
Software developers across stacks and seniority levels.
**High engagement.** GitHub (code-adjacent content); Hacker News (specific topics); specific subreddits; Twitter/X for parts of the dev community; dev-focused podcasts and newsletters; YouTube for tutorial content.
**Moderate engagement.** LinkedIn for senior developers; Stack Overflow for Q&A-driven content (different distribution model than programs typically use); Discord servers for specific tools.
**Low engagement.** TikTok, Instagram, Facebook, Pinterest for primary content.
### Founder and startup audiences
Founders, startup operators, early-stage investors.
**High engagement.** Twitter/X (the founder community has historically been engaged here); LinkedIn for some segments; specific newsletters (Lenny's, Substack-based founder newsletters); specific podcasts; YC-adjacent forums.
**Moderate engagement.** YouTube for some long-form content; specific subreddits.
**Low engagement.** Most mass-consumer platforms.
---
## The audience-channel audit
A short framework for matching audience to channels.
1. **Define the target audience specifically.** Not "marketers" but "B2B SaaS marketing leaders at companies with 50-500 employees, primarily in North America and Western Europe." Specificity unlocks the matching.
2. **Map where this audience spends time professionally.** Where do they get news, learn new ideas, hear from peers, encounter products?
3. **Map where this audience spends time consuming the kind of content the program produces.** Different from professional time generally; specific to the content type.
4. **Identify channels where the audience engages.** Not just where they have accounts. Engagement signals: comments, shares, conversion behaviors.
5. **Score channels by engagement potential.** High, moderate, low. The high-engagement channels get primary distribution capacity.
---
## Audience-research methods for the audit
How to actually identify where audiences engage.
**Customer interviews.** Ask existing customers where they consume content related to the program's topic. The answers are the audience's revealed-preference distribution map.
**Audience surveys.** Quantitative confirmation of channel-engagement patterns. Surveys can over-represent platforms respondents feel they should use; the customer interviews ground-truth the survey data.
**Existing program data.** Where does the program's existing audience come from? Referral data, UTM analysis, conversion attribution. Channels that produce existing audience are channels where the audience is engaging with the program.
**Competitive analysis.** Where do competing programs distribute? Where do they appear to earn engagement (visible signals: comments, shares, mentions)? Competitive distribution patterns inform but should not dictate the program's choices.
**Industry research.** Some industry research firms publish channel-engagement data by audience segment. Useful as starting points; should be triangulated with the program's own data.
---
## The audience-channel mismatch failure mode
The pattern when audience-channel matching is skipped.
**The symptom.** The program publishes consistently on multiple channels. Engagement is flat or declining. Distribution capacity is spread thin. The team cannot identify which channels are working because none of them are working clearly.
**The diagnosis.** Channels were chosen by industry default ("everyone is on LinkedIn") or by capacity availability ("we can post on TikTok") rather than by audience-engagement match.
**The cure.** Run the audience-channel audit. Cut channels where the audience is present but not engaged. Increase investment in channels where the audience is genuinely engaged. The total distribution capacity stays the same; the allocation shifts.
**Recovery time.** Cutting underperforming channels and concentrating capacity on engaging channels typically produces visible engagement improvements within 4-8 weeks.
---
## When audience-channel maps shift
Audiences move across channels over time. Maps that fit a program 3 years ago may not fit now.
**Common shifts.**
- Twitter/X engagement has declined for many B2B audiences as the platform has changed; LinkedIn has absorbed some of the shifted attention.
- TikTok has expanded into demographics it did not initially serve.
- Newsletter consumption has grown across most audience types as inbox-based content consumption has become more accepted.
- AI-search citation has emerged as a distribution channel that did not exist meaningfully before 2024.
**The audit cadence.** Run the audience-channel audit at least annually. Maps that have not been refreshed for 18+ months are likely outdated.
---
## The audience-channel-content-type triangle
Audience-channel matching is one of three matching decisions; content-channel matching is another (see `content-channel-matching.md`); the third is content-audience matching (the source piece is for the right audience in the first place).
**The triangle.**
- Audience matches channel.
- Content matches channel.
- Content matches audience.
**The failure modes.**
- Audience-channel mismatch: distribution where the audience is not engaged.
- Content-channel mismatch: format does not fit the channel's conventions.
- Content-audience mismatch: the piece is not actually for the channel's audience even if both fit individually.
The triangle is what produces channel-fit distribution. All three matchings need to hold for distribution to produce engagement.
---
## Methodology-level choices that stay in the public skill
The presence-vs-engagement distinction, the common audience-channel maps, the audience-channel audit, audience-research methods, the mismatch failure mode, the map-shift recognition, the audience-channel-content-type triangle.
## Implementation choices that stay internal
Specific audience-research surveys and interview templates. Specific UTM tracking and attribution conventions. Specific competitive analysis tooling. Specific channel-engagement scoring rubrics. The team's own audience-segment definitions. These vary by team, audience, and tooling.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |