Content Pipeline Automation Command
Defines a multi-stage content pipeline command that generates, schedules, and publishes blog posts across platforms with configurable daily, weekly, or monthly cadences.
What this file does
Defines a multi-stage content pipeline command that generates, schedules, and publishes blog posts across platforms with configurable daily, weekly, or monthly cadences.
When to use it
- Automating a personal or team blog with regular publishing cadence
- Running a content marketing operation that needs repeatable workflows
- Coordinating cross-platform distribution from a single command
- Enforcing quality and SEO standards across batch-generated posts
Assumes this stack
Content Pipeline Automation Command
Execute the complete content generation and publishing pipeline.
Usage
/content-pipeline [timeframe] (daily, weekly, monthly)
Pipeline Stages
1. Trend Analysis & Topic Discovery
- Scan industry sources for trending topics
- Analyze competitor content gaps
- Review analytics for top-performing content
- Identify seasonal content opportunities
- Generate priority topic list
2. Content Planning & Scheduling
- Create editorial calendar
- Assign topics to publication dates
- Plan content series and clusters
- Schedule social media promotion
- Set up cross-platform distribution
3. Batch Content Creation
- Generate multiple posts simultaneously
- Ensure content variety and balance
- Optimize for different content types
- Create supporting visual content
- Prepare newsletter versions
4. Quality Assurance & Optimization
- Review all content for consistency
- Validate SEO optimization
- Check internal linking structure
- Ensure brand voice alignment
- Verify factual accuracy
5. Publishing & Promotion
- Schedule posts in CMS
- Prepare social media campaigns
- Set up email notifications
- Create cross-promotional content
- Monitor initial performance
Timeframe Options
Daily Pipeline
/content-pipeline daily
- Generate 1 main post + 2 micro-content pieces
- Create social media content for next 24 hours
- Update trending topics research
- Schedule immediate social promotion
Weekly Pipeline
/content-pipeline weekly
- Generate 3-5 comprehensive blog posts
- Create week-long social media calendar
- Develop email newsletter content
- Plan video/podcast content adaptations
- Set up cross-platform publishing schedule
Monthly Pipeline
/content-pipeline monthly
- Generate 12-15 blog posts
- Create comprehensive content calendar
- Develop content series and campaigns
- Plan seasonal and event-based content
- Set up automated publishing workflows
Quality Metrics
Content Standards
- Average word count: 1500+ words
- SEO score: 80+ (Yoast/RankMath equivalent)
- Readability: Flesch score 60-70
- Sources: 3+ authoritative citations
- Internal links: 3-5 per post
Performance Targets
- Organic traffic growth: 20% month-over-month
- Social engagement: 5% increase per week
- Email click-through: 15%+ average
- Time on page: 3+ minutes average
- Bounce rate: <60%
Automation Features
Smart Scheduling
- Optimal posting times per platform
- Audience timezone considerations
- Content type performance analysis
- Seasonal trend alignment
Cross-Platform Integration
- WordPress REST API publishing
- Ghost Admin API integration
- Hashnode cross-posting
- Newsletter automation
- Social media scheduling
Analytics Integration
- Google Analytics tracking
- Search Console monitoring
- Social media metrics
- Email performance data
- Competitor analysis updates
Output Deliverables
Each pipeline execution creates:
- Editorial calendar (markdown)
- Content files with frontmatter
- Social media content library
- SEO optimization reports
- Performance tracking setup
- Publishing schedule
Error Handling
- Backup content generation
- Quality check failures
- API integration issues
- Scheduling conflicts
- Performance monitoring alerts
What's inside
5 pipeline stages, 3 timeframe options, quality metrics, automation features, output deliverables, and error handling
Change this for your project
- Replace
WordPress REST API publishingwith your own CMS endpoints - Replace
Ghost Admin API integrationwith your own API keys - Replace
Hashnode cross-postingwith your own platform integrations - Replace
Yoast/RankMathwith your actual SEO tool name
Where it goes
Save as CLAUDE.md in your repository root. Claude Code reads it automatically at the start of every session.
Worth borrowing
- Structuring a pipeline as discrete stages with clear handoffs between trend analysis, creation, QA, and publishing
- Offering three timeframes (daily/weekly/monthly) that scale the number of outputs and planning horizon
Related Documents
Code indexing for AI agents: summarization strategies and evaluation systems
Synthesises 2024-2025 research on code indexing for AI agents, covering summarisation strategies, hybrid retrieval architectures, and evaluation benchmarks.
Claude AI Git Workflow Integration
Recommends using the git-ai-commit CLI tool for AI-generated commit messages instead of manual ones.
Missing Business Agents Research — FLUXION 2026
Identifies 12 missing business operations agents for an indie software company and ranks them by impact and effort with €0 implementation plans.
角色：金牌面试者
Prompts Claude to act as a resume consultant, collecting user info and generating a polished A4-format React resume component with STAR-format experience.