菜单
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".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Klaviyo marketing operations and analyst expertise. Audit flows, segments, campaigns, deliverability, and revenue attribution. Use when the user asks about Klaviyo marketing strategy, email/SMS automation, customer segmentation, flow optimization, or lifecycle marketing. For API integration, SDK, webhook, or developer questions, see the klaviyo-developer skill.
Klaviyo API and developer integration expertise. Event tracking, SDKs, webhooks, rate limits, OAuth, catalog sync, and code patterns. Use when the user asks about Klaviyo API, integrating with Klaviyo, tracking events, building custom integrations, webhook handling, or developer implementation. For marketing strategy, flow optimization, and campaign auditing, see the klaviyo-analyst skill.
Pre-push hygiene check for GitHub repositories. Scans for PII, secrets, and sensitive data before pushing. Audits commit messages, enforces repo-specific blocklists, and rate-limits pushes to avoid GitHub abuse detection. Use before any git push, especially to public repos.
Generate, audit, or update GitHub READMEs with project-type-aware structure, voice calibration, and SEO/AEO discoverability guidance. Three modes: generate (new), audit (check existing), update (patch). Detects repo type and adapts sections, tone, and badges accordingly.
Google Tag Manager expertise. Audit GTM containers, design tag and trigger architecture, debug firing issues, implement consent mode v2, and advise on server-side tagging. Use when the user asks about GTM, tag management, container audits, consent mode, server-side tagging, or tracking implementation.
Comprehensive content marketing toolkit with brand voice analysis, SEO optimization scripts, content frameworks, social media strategy, and content calendar planning. Use when writing blog posts, creating social media content, analyzing brand voice, optimizing SEO, planning content calendars, or developing content strategy. For deep SEO writing optimization, see the seo-content-writer skill.
| 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-18T00:00:00.000Z","tested":"2026-03-18T00:00:00.000Z","tested_with":"Claude Code v2.1"} |
Orchestrate the full content creation workflow from research brief to published-ready content with social distribution pack.
git clone https://github.com/thatrebeccarae/claude-marketing.git && cp -r claude-marketing/skills/content-pipeline ~/.claude/skills/
Chains up to 3 agents in sequence:
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.
/content-pipeline [topic or file path]
/content-pipeline "Why MCP is the new API"
/content-pipeline review ./drafts/article-draft.md
/content-pipeline distribute ./content/published-article.md
./research-briefs/YYYY-MM-DD-topic-slug.md[draft-path]-review.md saved alongside the source[content-path]-social-pack.md saved alongside the sourceThe 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
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) |
Adapt the pipeline to your publishing schedule. Example cadence:
The pipeline tracks which stages are complete via file existence:
Resume from any stage by pointing to existing files.
This skill composes well with:
/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