🌐 Read this in: English · हिन्दी · 中文 · 日本語 · 한국어 · Español · Português · العربية · اردو · தமிழ் · বাংলা · Русский You need to ship 30 articles this quarter that sound human, cite real sources, link into your funnel, and survive an editor who checks.
$ npx -y skills add indranilbanerjee/contentforge --agent claude-code
What's inside
🌐 Read this in: English · हिन्दी · 中文 · 日本語 · 한국어 · Español · Português · العربية · اردو · தமிழ் · বাংলা · Русский
You need to ship 30 articles this quarter that sound human, cite real sources, link into your funnel, and survive an editor who checks. Your team is three people. You have nine weeks. Your last "AI-written" batch got flagged for hallucinated stats — and the batch before that quietly went stale and nobody noticed.
Run /contentforge:create-content against each topic. The 10-phase pipeline produces a publication-ready .docx with a 43-pattern humanizer, a fact-checker subagent, three-category internal linking, and C2PA provenance for EU AI Act compliance — in 30–60 minutes per piece. Then the part no single-shot tool has: the lifecycle loop. Every published piece is measured (cf-aeo-check), audited for decay (cf-audit), and fed back into the next calendar and the next brief — through durable file contracts, so what the system learns about your brand survives the session that learned it.
Open-source enterprise content production system — 22 skills · 13 specialist agents · 10 quality gates · 43-pattern AI-detection humanizer · a run auditor that re-derives every gate before a run may call itself finished · 28 Python scripts, stdlib-only. Built for marketing teams producing high volumes of long-form content that needs brand voice consistency, citation integrity, and an internal-link strategy that turns content into a funnel. Installs on Claude Code (CLI + IDE), Anthropic Cowork, OpenAI Codex, Cursor 2.5+, GitHub Copilot CLI, Google Antigravity 2.0, Hermes Agent, OpenClaw, and Grok (xAI Build CLI) + 35+ Agent Skills platforms — with hero skills uploadable to claude.ai (web) as .skill release assets. Created by Indranil Banerjee · LinkedIn · X.
🆕 Just shipped — v4.1.2 (August 17, 2026): schema-clean hooks manifest. Cowork's plugin validation rejects unknown top-level fields in
hooks.json, and ours carried a_readmerationale field (digital-marketing-pro#9 — the same defect shipped in all three suite plugins). The rationale now lives in hooks/README.md,hooks.jsonis exactly{"hooks": {}}, and a new guard keeps it that way. Translations re-stamped. Previously —v4.1.1 (August 17, 2026): the README goes global, and shows its receipts. This README now reads in 12 languages (हिन्दी, 中文, 日本語, 한국어, Español, Português, العربية, اردو, தமிழ், বাংলা, Русский — switcher at the top, every translation version-stamped and guard-checked), carries the real artifacts from a real validated run — the actual chart the pipeline rendered, the actual humanizer before/after edits, the actual 9.0/A scorecard and CLEAN audit verdict (see them) — and documents running ContentForge on OpenAI surfaces (Codex CLI/IDE/App and ChatGPT via Agent Plugins 1.0) with the same depth as the Claude surfaces, including updating on all nine platforms. Previously —
v4.1.0 (August 17, 2026): two new surfaces. ContentForge now installs natively on Grok (xAI Build CLI) —
grok plugin install indranilbanerjee/contentforge— via a first-class.grok-plugin/manifest pair, version-locked to every other manifest by the release-consistency suite. And five hero skills now ship as claude.ai-uploadable.skillrelease assets (cf-brief,cf-social-adapt,cf-translate,cf-video-script,cf-aeo-check), built by a deterministic packager (scripts/build-skill-assets.py) that bundles each skill's config/template dependencies and refuses to package any skill whose prose references a file that wouldn't exist after upload — so a claude.ai user never downloads a skill with broken references. Install for your platform →v4.0.0 (August 17, 2026): the lifecycle release. ContentForge 3.x was a production pipeline; 4.0 makes it a content system. Three architectural changes, each grounded in a defect a real run exposed: (1) The lifecycle loop closed.
cf-auditfindings now land in a validated, canonical per-brand store (scripts/audit-ledger.py) thatcf-calendarandcontent-refreshread across sessions; AI-visibility history (aeo/checks.json) feeds the freshness model; and each run's verified link inventory merges back intobrand_pagesautomatically — conversion pages only ever staged for your confirmation, because a CTA is a commercial decision the system must not make for you. Before 4.0 every one of those handoffs was conversational, and worked only while one session held both ends. (2) The pipeline contract is data.config/pipeline-graph.jsondeclares every phase's reads, writes, gates, and budgeted loop edges — drift-guarded both directions against the agent contracts, the checkpoint manager, and the run auditor. Encoding it immediately found six under-declared inputs the prose table had lost. (3) The pipeline learns, with floors. Newscripts/telemetry.pyaggregates loop history, phase timings, and the humanizer's per-pattern hit counts across runs — recurring patterns reach the next drafter brief as advisories behind a recurrence floor, and never touch a gate, a threshold, or a verdict. 22 skills · 27 scripts · 498 tests. Release notes → · Full changelog →
# Install in Claude Code (CLI or VS Code/JetBrains extension):
/plugin marketplace add indranilbanerjee/neels-plugins
/plugin install contentforge@neels-plugins
# Install in Cowork: use the Plugins panel in the UI -- /plugin slash
# commands DON'T work in Cowork (or Claude.ai / Claude Desktop).
# Open Plugins panel -> Add marketplace -> paste indranilbanerjee/neels-plugins
# -> Install ContentForge from the listed plugins.
# Install on Hermes Agent (Nous Research):
hermes plugins install indranilbanerjee/contentforge
# Install on OpenClaw:
openclaw plugins install git:github.com/indranilbanerjee/contentforge
# Install on Grok (xAI Build CLI):
grok plugin install indranilbanerjee/contentforge
If ContentForge saves your team time, give it a star ⭐ — it's the single thing that helps other marketing teams find it.
Most AI writing tools produce one draft, in one tone, with no quality gates, and forget the piece the moment it ships. The output reads like AI, factual claims are unverified, internal links don't exist, brand voice drifts, the file format is markdown when the editor wants Word — and six months later nobody knows which pieces went stale. ContentForge fixes this end to end:
| Capability | Why it matters |
|---|---|
| 10-phase pipeline with a quality gate after every phase | Bad output is caught and re-run before it propagates downstream |
| 43-pattern AI-detection humanizer + self-critique meta-pass | Output reads human, not AI — measured advisory tell-scan + burstiness metrics (text-metrics.py --ai-tell-scan) |
| Fact-checker subagent verifies URLs and cross-references claims | Citations work and aren't hallucinated — every statistic traces to a verified ledger entry |
| Three-category internal linking (topical / commercial / authority) | Content becomes a funnel, not a stranded page |
Real .docx output with embedded SEO + Quality + Production + Internal-Link appendices | Editor / design team gets a working Word file, not markdown |
| A run auditor that re-derives every gate from the artifacts | "The pipeline says it finished" and "the artifacts prove it finished" can never drift apart silently — finalize --status completed refuses without a fresh CLEAN verdict |
| The lifecycle loop (v4.0) — audit → refresh → measure → plan, joined by file contracts | Published content stops being fire-and-forget: decay is detected, refreshes are prioritized from data, and what the pipeline learns about your brand compounds |
| C2PA content provenance signing for EU AI Act Article 50 compliance | Long-form AI-assisted content distributed in EU markets needs provenance from 2 Aug 2026 |
| Platform | Install command | Manifest path | Status |
|---|---|---|---|
| Claude Code CLI + IDE extension | /plugin install contentforge@neels-plugins | .claude-plugin/plugin.json | Full support (canonical for solo devs) |
| Anthropic Cowork | Plugins panel in UI → Add marketplace → indranilbanerjee/neels-plugins → Install ContentForge | same .claude-plugin/ files | Recommended for teams — /contentforge:cf-cowork-setup wires Google Drive for team-shareable output (and, in 4.0, for the lifecycle stores that make the loop compound across sessions) |
| OpenAI Codex CLI + IDE + App | codex plugin marketplace add indranilbanerjee/neels-plugins then codex plugin install contentforge@neels-plugins | .codex-plugin/plugin.json (published OpenAI schema) | Full skills + MCP support |
| Cursor 2.5+ | In any Cursor Agent chat: /add-plugin contentforge@https://github.com/indranilbanerjee/contentforge | .cursor-plugin/plugin.json (verified Cursor 2.5+ JSON Schema) | Full skills + agents + commands support |
| GitHub Copilot CLI | copilot plugin marketplace add indranilbanerjee/neels-plugins then copilot plugin install contentforge@neels-plugins | .github/plugin/plugin.json (Copilot also recognizes .claude-plugin/plugin.json as fallback) | Full skills + MCP support |
| Google Antigravity 2.0 CLI + IDE | agy plugin install https://github.com/indranilbanerjee/contentforge | gemini-extension.json (at repo root, per Google's reference pattern) | Full skills + hooks support |
View @indranilbanerjee’s profileYour agency just signed a 50-brand client. The previous agency left no playbook. Three brands are bleeding budget, two have stale positioning, one is launching in a regulated jurisdiction next month. Where do you start?
@indranilbanerjeeFAQ
contentforge is a Claude Code plugin with 22 hand-picked skills for content work, indexed on Flowy. Install it with the command on its page. It includes batch-process, cf-add-integration, cf-aeo-check. Its skills do not fire on their own yet. Request auto-invocation to have Flowy route them as you prompt. Free and open source.
Is this plugin yours?
Claim it with GitHubSubmit a pluginPromote it