thatrebeccarae/claude-marketing / skills/content-pipeline
content-pipeline
VerifiedEnd-to-end content creation workflow that orchestrates research, editorial review, and social distribution agents in sequence. Use when the user wants to create, review, and distribute content through a multi-stage pipeline, or says "/content-pipeline".
| File | Kind | Size |
|---|---|---|
| EXAMPLES.md | markdown | 2.7 KB |
| LICENSE | other | 1.0 KB |
| REFERENCE.md | markdown | 3.1 KB |
| SKILL.md | skill md | 4.4 KB |
SKILL.md
View on GitHub---
name: content-pipeline
description: End-to-end content creation workflow that orchestrates research, editorial review, and social distribution agents in sequence. Use when the user wants to create, review, and distribute content through a multi-stage pipeline, or says "/content-pipeline".
license: MIT
origin: custom
author: Rebecca Rae Barton
author_url: https://github.com/thatrebeccarae
metadata:
version: 1.0.0
category: content
domain: content-orchestration
updated: 2026-03-18
tested: 2026-03-18
tested_with: "Claude Code v2.1"
---
# Content Pipeline
Orchestrate the full content creation workflow from research brief to published-ready content with social distribution pack.
## Install
```bash
git clone https://github.com/thatrebeccarae/claude-marketing.git && cp -r claude-marketing/skills/content-pipeline ~/.claude/skills/
```
## What This Skill Does
Chains up to 3 agents in sequence:
1. **research-analyst** — Generates a research brief on the topic
2. **editor-in-chief** — Reviews the draft against voice, structure, SEO, and argument quality
3. **social-amplifier** — Creates platform-specific distribution pack (LinkedIn, Twitter/X, email)
Users can enter at any stage or run the full pipeline.
> **How this differs from content-workflow:** The content-workflow skill is a manual workflow guide with frameworks and checklists. This skill is the *orchestration layer* — it actually spawns subagents and manages the pipeline programmatically.
## How to Use
```
/content-pipeline [topic or file path]
```
### Full Pipeline (from scratch)
```
/content-pipeline "Why MCP is the new API"
```
### Start from Existing Draft
```
/content-pipeline review ./drafts/article-draft.md
```
### Social Pack Only
```
/content-pipeline distribute ./content/published-article.md
```
## Workflow Stages
### Stage 1: Research (optional — skip if draft exists)
- Spawn research-analyst agent with the topic
- Output: `./research-briefs/YYYY-MM-DD-topic-slug.md`
- User reviews brief, decides whether to proceed
### Stage 2: Editorial Review
- Spawn editor-in-chief agent pointing at the draft/brief
- Output: `[draft-path]-review.md` saved alongside the source
- Agent provides: voice assessment, structure feedback, SEO evaluation, line-level notes, title variants
- User decides: publish as-is, revise, or iterate
### Stage 3: Social Distribution
- Spawn social-amplifier agent pointing at the final content
- Output: `[content-path]-social-pack.md` saved alongside the source
- Generates: LinkedIn posts (2 variants), Twitter/X thread, email subject lines, pull quotes, hashtags
## Configuration
### Customizing Agents
The default agent chain uses Claude Code subagents with the Agent tool. To customize:
```
Pipeline Stage | Default Agent Type | Override With
Research | research-analyst | Any research/analysis agent
Editorial | editor-in-chief | Any editorial review agent
Distribution | social-amplifier | Any social content agent
```
### Output Paths
Configure where each stage saves its output:
| Stage | Default Output Path |
|-------|-------------------|
| Research | `./research-briefs/YYYY-MM-DD-topic-slug.md` |
| Draft | `./content/YYYY/YYYY-MM-DD-slug.md` |
| Review | `[draft-path]-review.md` (alongside draft) |
| Social Pack | `[content-path]-social-pack.md` (alongside content) |
### Publishing Cadence
Adapt the pipeline to your publishing schedule. Example cadence:
- **Research**: Monday/Tuesday
- **Draft**: Tuesday/Wednesday
- **Review**: Wednesday/Thursday
- **Publish**: Thursday/Friday
## Pipeline State Management
The pipeline tracks which stages are complete via file existence:
- Research brief exists → Stage 1 complete
- Review file exists → Stage 2 complete
- Social pack exists → Stage 3 complete
Resume from any stage by pointing to existing files.
## Integration with Other Skills
This skill composes well with:
- **seo-content-writer** — Run during Stage 2 for deep SEO optimization
- **content-creator** — Use for brand voice analysis before editorial review
- **research-digest** — Alternative to the built-in research stage for RSS-based research
## Quick Commands
- `/content-pipeline` — Start full pipeline with topic prompt
- `/content-pipeline review [path]` — Jump to editorial review
- `/content-pipeline distribute [path]` — Jump to social distribution
- `/content-pipeline status` — Show drafts in progress
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |