community-automations/content-pipeline

DevOps & Code

PublicClaude subagentDemo

Content Pipeline Crew

Getting one article from brief to published in several languages normally passes through a writer, an editor, and a translator, with handoffs that drag for days. This crew runs the whole chain.

sonnet1 weekCrewAIOpenAIDeepLGrammarly API
ClaudeClaude
ROI for
README.md

Why this subagent

Getting one article from brief to published in several languages normally passes through a writer, an editor, and a translator, with handoffs that drag for days. This crew runs the whole chain.

A lead agent moves the piece through drafting, editing, and parallel translation, holding one voice across every language. You start with a brief and end with publish-ready content in every language, staged in your CMS.

How it runs

    • Read

      Used at step 01 to kick off the pipeline.

    • Write

      Used at step 01 to kick off the pipeline.

    • WebFetch

      Used at step 01 to kick off the pipeline.

    • WebSearch

      Used at step 01 to kick off the pipeline.

Sample output

json
// Sample output
// (generated when the pipeline finishes)

As the lead agent, move a brief through draft, edit, and parallel translation sub-agents, enforcing one consistent voice across languages, then publish each localized version to the CMS.

Unlock the rest

The full agent definition, install snippet, and starter task are gated for community members.

Members get the full `.md` agent file, the npm / pnpm install one-liners, a starter prompt that we've tuned against real runs, and the open-source repo when this automation ships there. One email, magic link, done.