Install
$ agentstack add skill-indranilbanerjee-contentforge-contentforge ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
ContentForge — Enterprise Content Production
Transform a content requirement into a publication-ready, fact-checked, brand-compliant, SEO-optimized piece in 20-30 minutes through a 10-phase autonomous agent pipeline with three-layer fact verification and zero hallucinations.
Context efficiency
Pipeline phase. Grep before Read for references/, humanization-patterns.json, brand voice profiles. Pass earlier-phase outputs by path + line range, not by reloading. On /contentforge:resume, load only the failed phase's state.
Execution Protocol (CRITICAL — read first)
This skill orchestrates 11 distinct phases. Each phase MUST be executed by invoking its dedicated subagent via the Task tool — DO NOT generate the deliverable yourself in a single inference pass. A single-pass generation skips the quality gates, fact-checking layers, humanizer 29-pattern catalog, and reviewer scoring that define ContentForge.
Required Per-Phase Workflow
For every one of the 11 phases below:
- Call
Bashto mark phase start:
``bash python3 ${CLAUDE_PLUGIN_ROOT}/scripts/pipeline-tracker.py --action phase-start --brand --phase ``
- Call
Taskwith the phase'ssubagent_typeand pass the previous phase's output as context. - Call
Bashto mark phase end with the output word count:
``bash python3 ${CLAUDE_PLUGIN_ROOT}/scripts/pipeline-tracker.py --action phase-end --brand --phase --content-words ``
- Emit the audit line (so users can see real-time progress):
`` [PHASE-AUDIT] phase= name= status= output_summary="" gate= ``
- Check the quality gate. If
gate=FAIL, loop back to the phase the reviewer flagged (max 5 total loops; on 5th loop, escalate to human review and halt).
Phase → Subagent Mapping
| Phase | subagent_type | Purpose | |-------|---------------|---------| | 0.5 | researcher (mini call) OR inline title curation | SERP-informed title generation; user picks 1 of 4-5 | | 1 | researcher | Web research, source mining, structured outline | | 2 | fact-checker | URL verification, claim validation | | 3 | content-drafter | First draft with brand voice | | 3.5 | visual-asset-annotator | Chart generation + visual markers | | 4 | scientific-validator | Industry-specific accuracy + hallucination detection | | 5 | structurer-proofreader | Grammar, flow, readability | | 6 | seo-geo-optimizer | Keywords, meta, schema, internal-link markers | | 6.5 | humanizer | 29-pattern catalog + self-critique meta-pass + voice calibration | | 7 | reviewer | 5-dimension quality scoring + final gate | | 8 | output-manager | .docx generation (local or Google Drive) + reports |
Final Output Requirements
After Phase 8 completes, the output-manager subagent must produce a Microsoft Word .docx file by calling:
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/generate-docx.py \
--content \
--output .docx \
--reports \
--brand "" \
--content-type
The .docx must contain: title page, full article body, sources/citations, Appendix A (SEO Scorecard), Appendix B (Quality Scorecard), Appendix C (Production Details).
If the brand has Google Drive configured (tracking.backend == "google"), upload the .docx via drive-uploader.py. Otherwise save locally to ~/.claude-marketing//output///.docx and tell the user the local path.
Why This Matters
Skipping the Task-tool orchestration means: no real fact-checking, no real humanizer (29-pattern AI removal won't fire), no real reviewer scoring — the pipeline becomes single-pass content generation labeled with fake phase names. The audit trail (pipeline-run.json, [PHASE-AUDIT] lines, real reviewer score) is the proof of execution. If those artifacts don't exist after a run, the pipeline didn't actually run.
When to Use
Use /contentforge when you need:
- Single high-quality content piece (article, blog, whitepaper, FAQ, research paper)
- Research-backed content with verified citations
- Brand-compliant content for regulated industries (Pharma, BFSI, Healthcare, Legal)
- SEO-optimized content with keyword targeting and meta tags
- Natural-sounding content with AI patterns removed (Phase 6.5 Humanizer)
For multiple pieces in parallel, use [/batch-process](../batch-process/SKILL.md) instead (4-5x faster).
What This Command Does
Runs your content through 10 specialized agents with quality gates at each phase:
- Research Agent — SERP analysis, source mining, competitive analysis, structured outline
- Fact Checker — URL verification, claim validation, confidence scoring
- Content Drafter — First draft with brand voice, SME calibration via industry knowledge packs
- Visual Asset Annotator — Chart generation from verified stats, visual markers, asset manifest
- Scientific Validator — Hallucination detection, domain-specific validation, logic validation
- Structurer & Proofreader — Grammar/spelling correction, readability optimization, brand compliance
- SEO/GEO Optimizer — Keyword optimization, meta tag generation, internal linking markers
- Humanizer — AI pattern removal, sentence variety (burstiness), brand personality
- Reviewer — 5-dimension quality scoring (Content Quality 30%, Citation Integrity 25%, Brand Compliance 20%, SEO Performance 15%, Readability 10%)
- Output Manager — .docx with embedded charts, internal links, Google Drive upload
Quality Gates: If any phase fails, the pipeline loops back with feedback (max 5 total loops before human escalation).
Required Inputs
Minimum Required:
- Topic — What the content is about (e.g., "AI in Healthcare", "remote work productivity")
- Content Type — article, blog, whitepaper, faq, research_paper
- Brand — Which brand profile to use (create with
/contentforge:style-guideif new brand)
Pre-Flight Validation: After gathering inputs, the system validates your brand profile for completeness (voice, guardrails, audience, industry pack). For regulated industries (pharma, BFSI, healthcare, legal), guardrails are required — the system will warn if they're empty and ask whether to proceed or update the profile first.
Optional:
- Target Audience — Who this content is for (e.g., "Healthcare CIOs")
- Word Count — Target length (defaults to content type standard)
- Primary Keyword — Main SEO keyword to optimize for
- Tone — Overrides brand default (authoritative, conversational, technical, witty)
How to Use
Interactive Mode (Recommended for First-Time Users)
/contentforge
Prompts you for:
- Topic (the subject — NOT the final title)
- Content Type (select from 5 options)
- Brand (select from existing profiles)
- Target Audience
- Word Count (or use default)
- Primary Keyword
Then generates 4-5 title options (different angles: benefit-driven, how-to, data-driven, question-based, contrarian). You select, modify, or provide your own title. Pipeline starts only after title confirmation.
Quick Mode (Topic Provided)
/contentforge "AI in Healthcare" --type=article --brand=AcmeMed --audience="Healthcare CIOs" --keyword="AI healthcare 2026"
Even in quick mode, the system generates title options and asks you to select before starting Phase 1. The topic you provide is the subject — the final title is always a user decision.
Use Existing Google Sheet Requirement
/contentforge --sheet-url=https://docs.google.com/spreadsheets/d/ABC123 --row=5
Reads requirement from Row 5 of the sheet.
What Happens
Title Curation (1-2 minutes) — MANDATORY
Before the pipeline starts, the system generates 4-5 SEO-optimized title options using the topic, content type, brand voice, audience, and primary keyword. Each title takes a different angle:
- Benefit-driven — leads with reader value
- How-to / Tactical — actionable, instructional
- Data-driven / Stat-led — opens with a number or trend
- Question-based / Curiosity — provokes the reader
- Contrarian / Unexpected — challenges convention
You select, modify, or provide your own title. The confirmed title becomes the anchor for the entire pipeline — research, outline, SEO, and final output all flow from it.
Do NOT skip this step or auto-select a title. The title shapes the entire content piece.
Phase 1: Research (3-5 minutes)
- Uses the confirmed title as the anchor for all research
- Performs SERP analysis for the topic and title angle
- Mines 10-15 authoritative sources
- Analyzes competitor content
- Generates structured outline aligned with the confirmed title
- Quality Gate: Must have 5+ live sources, differentiated angle
Phase 2: Fact Checking (2-3 minutes)
- Verifies all URLs are accessible (no 404s)
- Validates claims against sources
- Assigns confidence scores (strongly verified, partially verified, weakly verified)
- Flags any unverifiable claims
- Quality Gate: 80%+ verified claims, zero flagged items, all URLs live
Phase 3: Content Drafting (5-7 minutes)
- Generates first draft with brand voice
- Includes inline citations (APA format)
- Targets word count ±10%
- Maintains min 1 citation per 300 words
- Quality Gate: Word count ±10%, all outline sections covered, citation density met
Phase 4: Scientific Validation (2-3 minutes)
- Scans for hallucinations (fabricated statistics, made-up studies)
- Ensures all claims are traceable to sources
- Validates logical consistency
- Quality Gate: Zero hallucinations, all claims traceable
- If fails: Loops back to Phase 3 with specific claims to fix (max 2 loops)
Phase 5: Structuring & Proofreading (2-3 minutes)
- Corrects grammar and spelling (100% accuracy)
- Optimizes readability for content type (Grade 8-16 depending on type)
- Enforces brand terminology and style guide
- Quality Gate: Zero grammar errors, readability on target, 100% brand compliant
Phase 6: SEO/GEO Optimization (2-3 minutes)
- Optimizes keyword density (target: 1.5-2.5%)
- Places keywords in critical positions (title, H2s, first paragraph, conclusion)
- Generates meta title, meta description, URL slug
- Prepares content for AI answer engines (ChatGPT, Perplexity, Gemini)
- Quality Gate: Keyword density 1.5-2.5%, all critical placements hit, meta tags optimized
Phase 6.5: Humanizer ⭐ (1-2 minutes)
- Removes AI telltale phrases (20+ patterns: "delve", "leverage", "it's important to note")
- Increases sentence variety (burstiness ≥0.7 for natural human rhythm)
- Injects brand personality (authoritative, witty, warm, data-driven)
- Validates SEO preservation (keyword density unchanged ±2 occurrences)
- Quality Gate: AI patterns removed, burstiness ≥0.7, SEO preserved
Phase 7: Reviewer (2-3 minutes)
- Scores content across 5 dimensions:
- Content Quality (30%): Depth, originality, value, clarity
- Citation Integrity (25%): Accuracy, relevance, authority, freshness
- Brand Compliance (20%): Voice, terminology, guardrails, style
- SEO Performance (15%): Keyword optimization, meta tags, structure
- Readability (10%): Grade level, sentence variety, flow
- Calculates composite score (1-10, needs ≥7.0 to pass)
- Quality Gate: Score ≥7.0, all dimensions pass, zero critical violations
- **If ` for setup guides.
Environment
- Claude Code or Cowork (latest version)
- Internet connection (for Phase 1 web research)
Troubleshooting
"Brand profile not found"
When: You run /contentforge with a brand that doesn't have a profile yet.
Fix:
- Create a brand profile (recommended, 5 min):
`` /contentforge:style-guide `` Answer 3 questions (name, tone, industry) and you're ready.
- Or specify a different brand:
`` /contentforge "your topic" --brand=ExistingBrand ``
"Quality score 45 min for article"
When: The pipeline is taking longer than expected.
This is usually normal — API rate limits or network latency cause delays. ContentForge auto-retries with backoff.
If it persists beyond 60 min:
- Check internet connection
- Run
/contentforge:integrationsto verify MCP servers are responding - Try a simpler topic to isolate the issue
- Large whitepapers (5000+ words) can legitimately take 45-75 min
"Guardrails empty — compliance skipped"
When: Your brand profile doesn't have prohibited claims or required disclaimers defined.
Impact: Phase 5 (Brand Compliance) will report "SKIPPED" instead of actually checking content. Phase 7 applies a -1.0 penalty to Brand Compliance score.
Fix:
/contentforge:style-guide --update [brand]
Add at minimum: 3-5 prohibited claims, any required legal disclaimers, and industry-specific restrictions.
For regulated industries (pharma, BFSI, healthcare, legal): This is critical. Empty guardrails mean no compliance verification.
Pipeline phase explanations
During content production, you'll see updates as each phase completes:
| Phase | What's Happening | Duration | What You'll See | |-------|-----------------|----------|----------------| | Title Curation | Generating 4-5 title options from SERP data | 1-2 min | Title options with character counts | | Phase 1: Research | SERP analysis, source mining, outline | 3-5 min | Source count, outline sections | | Phase 2: Fact Check | URL verification, claim validation | 2-3 min | Verified %, flagged claims | | Phase 3: Draft | First draft with brand voice | 5-7 min | Word count, citation density | | Phase 3.5: Visuals | Charts, image generation (if opted in) | 2-3 min | Visual count, chart specs | | Phase 4: Validation | Hallucination detection | 2-3 min | Zero hallucinations confirmed | | Phase 5: Structure | Grammar, readability, brand compliance | 2-3 min | Compliance status | | Phase 6: SEO | Keyword optimization, meta tags | 2-3 min | Keyword density, GEO score | | Phase 6.5: Humanize | AI pattern removal, personality | 1-2 min | Burstiness score | | Phase 7: Review | 5-dimension quality scoring | 2-3 min | Score breakdown, pass/fail | | Phase 8: Output | .docx generation, tracking, delivery | 1-2 min | Output location, final metrics |
If a phase loops back: The system shows which phase failed, why, and what it's fixing. Loops are automatic — you don't need to do anything unless it escalates to human review.
Example Workflow
Scenario: Create 1 thought leadership article for AcmeMed brand
Step 1: Create Brand Profile (One-Time Setup)
/contentforge:style-guide
Provide: Brand name (AcmeMed), Industry (Healthcare), Voice (Authoritative), Tone (Professional), Terminology, Guardrails
Step 2: Start Content Production
/contentforge "AI-Powered Diagnostics in Precision Medicine" --type=article --brand=AcmeMed --audience="Healthcare Executives" --keyword="AI diagnostics precision medicine"
Step 3: Select Title (1-2 minutes)
ContentForge generates 4-5 title options:
- "AI-Powered Diagnostics: The Future of Precision Medicine in 2026"
- "How AI Diagnostics Are Transforming Precision Medicine for Healthcare Leaders"
- "5 AI Diagnostic Breakthroughs Reshaping Precision Medicine Right Now"
- "The Executive's Guide to AI-Powered Precision Medicine Diagnostics"
- "Why AI Diagnostics in Precision Medicine Are Finally Delivering on the Promise"
You select Option 1 → Pipeline starts with that title as the anchor.
Step 4: Review Output (24 minutes later)
- Quality Score: 9.1/10 ✅
- Word Count: 1,922 ✅
- Citations: 12 sources ✅
- SEO: Keyword density 2.3% ✅
Step 5: Publish
/contentforge:publish --platform=webflow
Total Time: 25 minutes (setup once, then 20-30 min per piece)
Limitations
- Sequential processing (for parallel, use
/batch-process) - 20-30 min per piece (cannot be rushed without compromising quality)
- Best with brand profile — works without one but us
…
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: indranilbanerjee
- Source: indranilbanerjee/contentforge
- License: MIT
- Homepage: https://indranil.in
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.