content-pipeline

Coordinate a five-stage content workflow from topic ideation to published blog posts.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/infolog-io/Monet --skill content-pipeline-infolog-io
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: content-pipeline
Source: https://github.com/infolog-io/Monet/tree/main/jtbd/pipelines/content-pipeline/.claude/skills/content-pipeline
Command: npx skills add https://github.com/infolog-io/Monet --skill content-pipeline-infolog-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Content Pipeline Orchestrator receives a user topic and drives it through five sequential agents, validating data at every handoff boundary.

Core Features & Use Cases

  • Orchestrates five stages: Trend Scout, Content Writer, SEO Optimizer, QA Fact-Checker, and Git Publisher with strict handoff contracts.
  • Validates each stage's JSON output before passing to the next stage to ensure data integrity.
  • Applies to end-to-end content projects from topic ideation to published blog posts.

Quick Start

Provide a topic and let the pipeline orchestrate the five stages to deliver a published post.

Frequently Asked Questions about content-pipeline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate a blog content pipeline from ideation to publishing?

Automate a blog content pipeline by orchestrating five sequential stages: topic ideation, drafting, SEO optimization, quality assurance, and publishing. The workflow enforces strict input validation and deterministic stage sequencing using JSON handoff schemas to ensure data integrity across each phase.

How does validated stage sequencing work in an automated content workflow?

Validated stage sequencing works by enforcing deterministic progression through five agents using JSON handoff schemas. Each stage outputs a validated contract—like ResearchBrief, DraftPost, or OptimizedPost—ensuring data integrity before passing data to the next boundary.

Can I use this content pipeline to handle SEO optimization and QA fact-checking?

Yes, the content pipeline includes dedicated SEO optimization and QA fact-checking stages. The SEO Optimizer and QA Fact-Checker agents process the drafted content, outputting an OptimizedPost and ValidationReport respectively before final publishing.

What is the best way to ensure data integrity during content workflow handoffs?

Ensure data integrity during content workflow handoffs by validating each stage's JSON output before passing it to the next. The pipeline uses strict input validation and structured JSON schemas like ValidationReport and PublishReceipt to prevent data loss between agents.

Do I need to provide structured input to start the automated blog publishing process?

No, you only need to provide a topic to start the automated blog publishing process. The pipeline orchestrator takes the topic and drives it through trend scouting, drafting, SEO, QA, and publishing stages automatically using validated handoff contracts.

Why does a content pipeline use JSON handoff schemas between workflow stages?

A content pipeline uses JSON handoff schemas to maintain strict input validation and data integrity across stage boundaries. These deterministic contracts, such as DraftPost and PublishReceipt, ensure each agent receives properly structured data before processing.