content-distribution
Promote creative and technical work through strategic content distribution. Covers platform selection, audience building, content repurposing, and engagement strategies without becoming a full-time marketer. Triggers on promotion, audience building, social media strategy, or content marketing requests.
Best use case
content-distribution is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Promote creative and technical work through strategic content distribution. Covers platform selection, audience building, content repurposing, and engagement strategies without becoming a full-time marketer. Triggers on promotion, audience building, social media strategy, or content marketing requests.
Teams using content-distribution should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/content-distribution/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How content-distribution Compares
| Feature / Agent | content-distribution | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Promote creative and technical work through strategic content distribution. Covers platform selection, audience building, content repurposing, and engagement strategies without becoming a full-time marketer. Triggers on promotion, audience building, social media strategy, or content marketing requests.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Content Distribution
Get your work seen without becoming a full-time marketer.
## Distribution Philosophy
### The Reality
- Great work doesn't promote itself
- You don't need millions of followers
- Consistency beats virality
- Value attracts audience
### The Sustainable Approach
| Unsustainable | Sustainable |
|---------------|-------------|
| Post daily everywhere | Focus on 1-2 platforms |
| Chase trends | Build on your expertise |
| Optimize for algorithm | Optimize for humans |
| Content for content's sake | Share genuine value |
---
## Platform Selection
### Choose Based On
1. **Where is your audience?**
2. **What format fits your work?**
3. **What can you sustain?**
### Platform Strengths
| Platform | Best For | Content Type | Effort |
|----------|----------|--------------|--------|
| Twitter/X | Tech, ideas, discussion | Short-form, threads | Medium |
| LinkedIn | Professional, B2B | Articles, updates | Medium |
| Instagram | Visual work, creative | Images, reels | High |
| YouTube | Tutorials, long-form | Video | Very High |
| TikTok | Entertainment, quick tips | Short video | High |
| Substack/Newsletter | Deep content, owned audience | Long-form writing | Medium |
| Personal Blog | SEO, portfolio | Any | Low |
| GitHub | Code, open source | Repositories | Low |
### The 70/20/10 Rule
Pick ONE primary platform:
- 70% of effort on primary platform
- 20% on secondary platform
- 10% experimenting
---
## Content Strategy
### Content Pillars
Define 3-5 themes you consistently create around:
```
Example for a creative technologist:
1. Technical tutorials (how I built X)
2. Creative process (behind the scenes)
3. Industry commentary (trends, tools)
4. Personal projects (show the work)
5. Career/professional development
```
### Content Types by Effort
| Low Effort | Medium Effort | High Effort |
|------------|---------------|-------------|
| Retweet + comment | Thread/carousel | Blog post |
| Quick tip | Short-form video | YouTube video |
| Question | Newsletter | Course/workshop |
| Work-in-progress | Case study | Open source project |
| Curated links | Tutorial | Research paper |
### The 4-1-1 Rule
For every 6 posts:
- 4 share value from others (curate)
- 1 soft self-promotion
- 1 direct self-promotion
Or: **Give value 5x for every 1x you ask**
---
## Content Creation
### The Show Your Work Framework
From Austin Kleon:
1. **Daily dispatch**: Share process, not just product
2. **Flow, not stock**: Ongoing sharing, not just launches
3. **Become a documentarian**: Capture as you go
### Content Prompts
**Process**:
- What are you working on today?
- What problem did you just solve?
- What mistake did you make?
- What did you learn this week?
**Teaching**:
- What do beginners get wrong?
- What's a shortcut you discovered?
- What tool changed your workflow?
- What concept took you too long to understand?
**Opinion**:
- What's a hot take in your field?
- What's underrated/overrated?
- What would you tell yourself 5 years ago?
- What do you disagree with experts on?
### Writing Formats That Work
**Thread/Carousel**:
```
Hook: Surprising claim or question
Point 1: [Evidence/example]
Point 2: [Evidence/example]
Point 3: [Evidence/example]
Summary: Key takeaway
CTA: Follow for more / Link to resource
```
**Short-form post**:
```
[Hook - first line matters most]
[Value - the actual content]
[CTA - what to do next]
```
---
## Repurposing
### The Content Pyramid
```
┌───────────┐
│ Pillar │ Long-form (blog, video)
│ Content │
└─────┬─────┘
│
┌───────────┼───────────┐
▼ ▼ ▼
┌────────┐ ┌────────┐ ┌────────┐
│Thread 1│ │Thread 2│ │Thread 3│ Medium-form
└────┬───┘ └────┬───┘ └────┬───┘
│ │ │
┌────┴────┬─────┴────┬─────┴────┐
▼ ▼ ▼ ▼
Tweets Quotes Images Clips Micro-content
```
### Repurposing Workflow
One blog post becomes:
- Twitter thread
- LinkedIn article
- 5-10 individual tweets/posts
- Newsletter section
- Carousel graphics
- Video script
- Podcast talking points
### Repurposing Rules
- Wait between platforms (not same day)
- Adapt format to platform norms
- Don't just copy/paste
- Update with new insights
---
## Engagement Strategy
### Meaningful Engagement
**Do**:
- Add value to conversations
- Ask genuine questions
- Share relevant experiences
- Credit and amplify others
**Don't**:
- Generic comments ("Great post!")
- Hijack threads for self-promo
- Engage only with big accounts
- Automate engagement
### Building Relationships
1. **Identify peers**: 20-50 people in your space
2. **Engage consistently**: Comment on their work
3. **Add value first**: Help before asking
4. **Collaborate**: Guest posts, interviews, projects
### Responding to Engagement
- Reply to comments within 24 hours
- Ask follow-up questions
- Thank people who share
- DM people who engage consistently
---
## Analytics That Matter
### Vanity vs Valuable Metrics
| Vanity | Valuable |
|--------|----------|
| Follower count | Follower growth rate |
| Total likes | Engagement rate |
| Impressions | Click-through rate |
| Views | Subscribers/email signups |
### What to Track
- Which content types perform best?
- When does your audience engage?
- What topics resonate?
- Where do website visitors come from?
### Review Cadence
- **Weekly**: Quick check on recent posts
- **Monthly**: Content performance review
- **Quarterly**: Strategy adjustment
---
## Sustainable Schedule
### Minimum Viable Presence
| Platform | Minimum | Ideal |
|----------|---------|-------|
| Twitter | 3x/week | 1x/day |
| LinkedIn | 2x/week | 3-4x/week |
| Newsletter | 2x/month | Weekly |
| Blog | 2x/month | Weekly |
| YouTube | 2x/month | Weekly |
### Batching
- **Write day**: Create content in batches
- **Schedule ahead**: Use scheduling tools
- **Repurpose day**: Transform existing content
- **Engagement time**: Daily 15-30 min blocks
---
## Launch Strategy
### For a New Project
**Pre-launch** (2-4 weeks before):
- Tease what's coming
- Share behind-the-scenes
- Build email list interest
**Launch week**:
- Announce on all platforms
- Ask friends to share
- Engage with every comment
- Share social proof
**Post-launch**:
- Thank supporters
- Share results/learnings
- Continue creating content
---
## References
- `references/platform-guides.md` - Platform-specific tactics
- `references/content-calendar-template.md` - Planning templates
- `references/tools-stack.md` - Scheduling and analytics toolsRelated Skills
posse-distribution-architecture
Implement POSSE (Publish on Own Site, Syndicate Elsewhere) content distribution with canonical URLs, cross-platform syndication, backfeed collection, and resilient delivery. Covers multi-platform publishing automation and IndieWeb patterns. Triggers on POSSE implementation, content syndication architecture, or IndieWeb publishing requests.
conversation-content-pipeline
Transform AI conversations and chat transcripts into publishable content including blog posts, documentation, tutorials, and knowledge base entries. Covers extraction, restructuring, and editorial refinement. Triggers on conversation-to-content, transcript processing, or chat-to-doc requests.
taxonomy-modeling-design
Phase 2 of the pentaphase structural-overhaul protocol. Classifies entities, standardizes attributes, establishes relationships, and designs the access framework. Use when the user invokes phase 2 of an overhaul, asks to "design the taxonomy" or "model the structure", or has completed a landscape audit and is ready to redesign. Consumes phase-1-landscape-report.md; produces phase-2-taxonomy-model.md.
systemic-ingestion-normalization
Phase 4 of the pentaphase structural-overhaul protocol. Purges redundancies, enriches and aligns legacy entities to the new schema, executes phased ingestion into the new environment, and audits integrity. Use when the user invokes phase 4 of an overhaul, asks to "migrate the data" or "ingest into the new system", or has a configured environment ready to accept legacy entities. Consumes phase-3-environment-spec.md; produces phase-4-ingestion-report.md.
system-environment-configuration
Phase 3 of the pentaphase structural-overhaul protocol. Translates the taxonomy model into objective technical criteria, evaluates candidate mechanisms or frameworks, instantiates the chosen architecture, and programs validation rules. Use when the user invokes phase 3 of an overhaul, asks to "select a system" or "configure the environment", or has a taxonomy model and is ready to choose technology. Consumes phase-2-taxonomy-model.md; produces phase-3-environment-spec.md.
pentaphase-orchestrator
Threads the full five-phase structural-overhaul protocol — landscape discovery, taxonomy design, environment configuration, systemic ingestion, governance evolution — for any substrate the user names. Use when the user requests a structural overhaul, system redesign, or end-to-end restructuring of a documentation system, asset registry, code monorepo, knowledge base, or operational workflow; or when they explicitly invoke the pentaphase methodology. Coordinates handoffs between phase-skills and seats validation gates between phases.
landscape-discovery-audit
Phase 1 of the pentaphase structural-overhaul protocol. Inventories assets, maps current flow, identifies friction, and defines value metrics for any substrate. Use when the user invokes phase 1 of an overhaul, requests a baseline audit, asks to "discover the landscape" of a system, or wants to understand current state before redesigning. Produces phase-1-landscape-report.md.
governance-evolution-protocol
Phase 5 of the pentaphase structural-overhaul protocol. Codifies operational protocols, onboards the ecosystem of participants, programs behavior monitoring, and establishes an iteration cadence so the substrate evolves rather than calcifies. Use when the user invokes phase 5 of an overhaul, asks to "establish governance" or "lock in the protocols", or has completed ingestion and is ready to declare the substrate operational. Consumes phase-4-ingestion-report.md; produces phase-5-governance-charter.md, which closes the protocol.
dimension-surfacing
Surfaces the parallel domain dimensions implicit in a dense or minimal prompt. Use when a user prompt is small on the surface but plainly implies multiple independent domains needing different expertise; when explicitly invoked by the coliseum-orchestrator skill as Phase 1; or when the user asks "what dimensions does this prompt encode" or "what axes does this break into." Produces a named dimension set where each dimension is independently executable and not a paraphrase of another.
coliseum-dispatch
Dispatches a composed set of assignment envelopes to domain-expert subagents in parallel, in a single message with multiple Agent tool calls. Enforces the no-pingpong gate via the pingpong-detector agent before any dispatch fires. Use when invoked by the coliseum-orchestrator as Phase 3; when envelopes are already composed and the next step is parallel execution; or when the user asks to "fan out" or "dispatch in parallel." Produces a dispatch log capturing what was sent, when, and where returns land.
assignment-composition
Wraps each surfaced dimension as a self-contained 9-section autonomous-work-assignment envelope — scope, context, success criteria, allowed tools, return format, handoff — all the recipient subagent needs to execute without coming back. Use when invoked by coliseum-orchestrator as Phase 2; when dimensions are named and the next step is to make each independently dispatchable; or when the user asks "compose this as an assignment." The no-pingpong gate validates each envelope before dispatch.
workspace-autopsy-governance
Conducts a full automated autopsy of the current workspace directory to map files, identifies structural issues, proposes a restructuring plan (the signal), and establishes unified governance using templates. Use this skill when a user asks to map, restructure, reorganize, or apply new governance to an existing messy repository.