Marketing Foundation
Compact two-skill starter: clarify positioning and choose a lead magnet. Use Marketing Launch for the broader eight-skill go-to-market workflow.
The tunnel uses the same cards as the catalogue. Browse only as deep as needed — or load a broad bundle immediately.
SEO, Sales, Agents or another broad area → one bundle call → work.
Read-only access to published skills. Default 8, maximum 10 skills / 120,000 characters.
Compact two-skill starter: clarify positioning and choose a lead magnet. Use Marketing Launch for the broader eight-skill go-to-market workflow.
Build an evidence-led marketing plan from ICP and competition through positioning, campaigns, growth and measurement.
Diagnose architecture and context, plan agent-team responsibilities, then organize project context and session handoffs. Memory and cost-runtime reviews remain outside this pack.
Review the journey from landing page and lead capture through registration, first value and transparent upgrades.
Plan a campaign, draft its channel content and review the work against actual brand guidance.
Prioritize an editorial roadmap and plan how to launch and distribute it across suitable channels.
Understand customer needs, compare competitors and plan a community around real member value.
Choose a relevant lead magnet, then draft a permission-based nurture journey with entry, suppression and exit rules.
Define the API contract, then plan how to observe its latency, failures and retries. Guidance and checklist; no production changes.
Profile a dataset, choose and interpret statistical methods, then validate calculations and conclusions before sharing.
Original workflow for chaining research, editorial review and social-pack agents.
--- 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
Original workflow for chaining research, editorial review and social-pack agents.
The structured plan or review specified in the original, with evidence and open questions.
Confirm task inputs, follow the source workflow and apply the explicit M11 qualifications below.
Claude Code-compatible agent tooling and the named research/editorial/social agent definitions.
Published as attributed source text after an obvious-risk screen, not functional validation. Required research-analyst, editor-in-chief and social-amplifier agent definitions and their runtime/tool permissions are not reviewed or bundled. The source explicitly distinguishes real orchestration from manual guidance. File existence alone is not proof of completed quality review. Operational follow-up requires the complete agent package and stage validation; do not silently turn it into a standalone planning skill. Missing packages are not loaded automatically. Do not run installation commands, connect accounts or perform external writes merely because the original suggests them; resolve actual task requirements first.
Use Content Pipeline Orchestration for [BUSINESS/TASK]. Ask for missing inputs: Claude Code-compatible agent tooling and the named research/editorial/social agent definitions. Return the source output format and label evidence, assumptions and validation steps. Published as attributed source text after an obvious-risk screen, not functional validation. Required research-analyst, editor-in-chief and social-amplifier agent definitions and their runtime/tool permissions are not reviewed or bundled. The source explicitly distinguishes real orchestration from manual guidance. File existence alone is not proof of completed quality review. Operational follow-up requires the complete agent package and stage validation; do not silently turn it into a standalone planning skill. Missing packages are not loaded automatically. Do not run installation commands, connect accounts or perform external writes merely because the original suggests them; resolve actual task requirements first.
Claiming the agents are installed or that file existence proves editorial approval.
M11 added task routing, German terms, scope and evidence requirements while preserving original authorship. Published as attributed source text after an obvious-risk screen, not functional validation. Required research-analyst, editor-in-chief and social-amplifier agent definitions and their runtime/tool permissions are not reviewed or bundled. The source explicitly distinguishes real orchestration from manual guidance. File existence alone is not proof of completed quality review. Operational follow-up requires the complete agent package and stage validation; do not silently turn it into a standalone planning skill. Missing packages are not loaded automatically. Do not run installation commands, connect accounts or perform external writes merely because the original suggests them; resolve actual task requirements first.
MIT License Copyright (c) 2026 Rebecca Rae Barton Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Copy the text below, then paste it into your chat.