mcpField
C
content-pipeline

content-pipeline

github.com/thatrebeccaraeMarketing & growth188115 installsUpdated 24w ago
Repository

About content-pipeline

content-pipeline is a Claude Code skill for content marketers that coordinates research, editorial review, and social distribution. It runs these stages through subagents and can resume from an existing draft or a chosen stage.

Key features

  1. 01Chains research, editing, and distribution
  2. 02Skips or enters stages as needed
  3. 03Creates research briefs and review files
  4. 04Builds platform-specific social content packs
  5. 05Resumes based on existing files

Use cases

  1. 01Run the full content process from a topic
  2. 02Review an existing article draft
  3. 03Create social materials for a published article

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/thatrebeccarae/claude-marketing --skill content-pipeline

After installing, type/content-pipelinein Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

EXAMPLES.md
LICENSE
REFERENCE.md

Details

From the project README

Content Pipeline

Orchestrate the full content creation workflow from research brief to published-ready content with social distribution pack.

Install

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:

StageDefault 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

Comments

Markdown supported