community-automations/content-pipeline

DevOps 與程式碼

PublicClaude 子代理示範

內容產線團隊

把一篇文章從簡報做到多語言上線，通常得經過寫手、編輯和譯者，層層交接一拖就是好幾天。這個團隊跑完整條流程。

sonnet1 週CrewAIOpenAIDeepLGrammarly API
ClaudeClaude
ROI for
README.md

為什麼選擇此子代理

把一篇文章從簡報做到多語言上線，通常得經過寫手、編輯和譯者，層層交接一拖就是好幾天。這個團隊跑完整條流程。

主導代理人讓文章依序經過草稿、編輯與平行翻譯，並在每種語言中維持一致的口吻。你從一份簡報開始，最後得到每種語言都已準備上線的內容，並暫存在你的 CMS 裡。

運作方式

    • 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.

輸出範例

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.