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.
What this skill does
# 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 tools
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.