Skip to content

thatrebeccarae/claude-marketing / skills/content-workflow

content-workflow

Verified

End-to-end content creation pipeline from research through editorial review to social distribution. Orchestrates a 3-stage workflow: research, draft/edit, and distribute. Supports blog posts, LinkedIn, Twitter threads, newsletters, and essays.

FileKindSize
EXAMPLES.mdmarkdown2.2 KB
LICENSEother1.0 KB
REFERENCE.mdmarkdown4.2 KB
SKILL.mdskill md4.0 KB
---
name: content-workflow
description: "End-to-end content creation pipeline from research through editorial review to social distribution. Orchestrates a 3-stage workflow: research, draft/edit, and distribute. Supports blog posts, LinkedIn, Twitter threads, newsletters, and essays."
license: MIT
origin: custom
author: Rebecca Rae Barton
author_url: https://github.com/thatrebeccarae
metadata:
  version: 1.0.0
  category: content
  domain: workflow
  updated: 2026-03-13
  tested: 2026-03-17
  tested_with: "Claude Code v2.1"
---

# Content Workflow

End-to-end content creation pipeline: research, draft, review, distribute.

## Install

```bash
git clone https://github.com/thatrebeccarae/claude-marketing.git && cp -r claude-marketing/skills/content-workflow ~/.claude/skills/
```

## Pipeline Stages

### Stage 1: Research

Gather raw material for the content piece.

1. **Topic research** — web search, RSS feeds, industry sources
2. **Source assessment** — credibility, recency, relevance
3. **Data extraction** — key statistics, quotes, data points
4. **Counter-arguments** — opposing views, nuance, caveats
5. **Angle development** — what makes this piece unique

**Output:** Research brief with sources, data points, and recommended angle.

### Stage 2: Draft & Edit

Create and refine the content.

1. **Draft** — write following the content type framework and brand voice
2. **Editorial review** against quality criteria:
   - Voice consistency
   - Structural quality (hook → body → CTA)
   - SEO optimization (if applicable)
   - Factual accuracy (all claims sourced)
   - Readability (appropriate level for audience)
3. **Revision** — apply specific feedback
4. **Final review** — verify all issues addressed

**Output:** Polished draft ready for approval.

### Stage 3: Distribute

Adapt the finished piece for cross-platform distribution.

1. **LinkedIn post** — hook, body, CTA, hashtags
2. **Twitter/X thread** — numbered tweets, hooks per tweet
3. **Email subject lines** — 3 options with preview text
4. **Pull quotes** — 3-5 shareable excerpts for social

**Output:** Distribution pack with platform-specific adaptations.

## Usage Modes

### Full Pipeline

```
/content-workflow [topic]
```

Runs all 3 stages: research → draft → review → distribute.

### Start from Draft

```
/content-workflow --from-draft [file path]
```

Skips research. Takes an existing draft through editorial review and distribution.

### Distribution Only

```
/content-workflow --distribute [file path]
```

Takes a finished, approved piece and creates the social distribution pack.

## Content Types

| Type | Research Depth | Draft Length | Distribution |
|------|---------------|-------------|--------------|
| Blog post | Deep (5+ sources) | 1,500-2,500 words | LinkedIn + Twitter + Email |
| LinkedIn post | Light (2-3 sources) | 150-300 words | Twitter adaptation only |
| Twitter thread | Light (1-2 sources) | 5-12 tweets | LinkedIn adaptation only |
| Newsletter | Medium (3-5 sources) | 500-1,000 words | Twitter + LinkedIn teasers |
| Essay | Deep (8+ sources) | 2,000-4,000 words | Full distribution pack |

## Status Tracking

Content moves through these statuses:

```
stub → draft → reviewed → approved → published → measured
                                   ↘ rejected (terminal)
```

- **stub:** Topic identified, no content yet
- **draft:** First draft complete
- **reviewed:** Editorial review complete
- **approved:** Human approval gate passed
- **published:** Live on platform
- **measured:** Performance data collected
- **rejected:** Did not pass review, will not publish

## Key Principles

1. **Research before writing.** Even short posts benefit from 10 minutes of source gathering.
2. **One piece, many platforms.** Write once, adapt to each platform's format.
3. **Human approval gate.** Never publish without explicit approval.
4. **Measure everything.** Track performance to inform future content decisions.

For editorial review criteria and platform templates, see [REFERENCE.md](REFERENCE.md).
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 119kUpdated Claude CodeCodexVerifiedInstall
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: 118kUpdated Claude CodeCodexVerifiedInstall