mcpField
C
content-workflow

content-workflow

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

About content-workflow

content-workflow is a marketing content skill for research, drafting, review, and distribution. It can start with a topic or an existing draft, with a human approval gate before publication.

Key features

  1. 01Research topics and assess sources
  2. 02Draft and edit in a brand voice
  3. 03Review quality and verify claims
  4. 04Adapt content for LinkedIn, Twitter/X, and email
  5. 05Track review and publication status

Use cases

  1. 01Create and distribute a blog post from a topic
  2. 02Review an existing draft and prepare social versions
  3. 03Adapt approved content for multiple platforms

Install

Copy the command and run it in a terminal.

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

After installing, type/content-workflowin 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 Workflow

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

Install

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

TypeResearch DepthDraft LengthDistribution
Blog postDeep (5+ sources)1,500-2,500 wordsLinkedIn + Twitter + Email
LinkedIn postLight (2-3 sources)150-300 wordsTwitter adaptation only
Twitter threadLight (1-2 sources)5-12 tweetsLinkedIn adaptation only
NewsletterMedium (3-5 sources)500-1,000 wordsTwitter + LinkedIn teasers
EssayDeep (8+ sources)2,000-4,000 wordsFull 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.

Comments

Markdown supported