Agent Teams
Assign drafting, review, and publishing to separate coordinated agents — each with a clear role in the pipeline.
Paperclip
Blogizi for Paperclip
Define a content pipeline with drafting, review, and publishing stages, and let Paperclip's open-source agent teams run it against Blogizi.
Blogizi's draft-first behavior fits naturally into Paperclip's approval-gated pipelines.
Context
What is Paperclip?
Paperclip is an open-source orchestration framework for building agent teams — a content agent, a review agent, a publishing agent — that collaborate on a pipeline with defined roles and approval gates.
Fit
Why pipelines map to Blogizi
Approval Gates
Pipelines can require explicit approval before a stage runs — which maps directly onto Blogizi’s draft-then-publish model.
Single Dashboard
Monitor pipeline status across drafting, review, and publishing stages from one place.
Pipeline
A Blogizi content pipeline
Writer → reviewer (approval) → publisher. The automated publisher only stages a draft.
pipeline.yaml
pipeline: blog_content
schedule: "weekdays 9am"
tools:
- blogizi-agent
roles:
writer:
task: "Research and draft an SEO blog post with frontmatter"
output: drafts/
reviewer:
task: "Review the draft for accuracy and tone"
requires: writer
approval: true
publisher:
task: "Push the approved draft to Blogizi"
requires: reviewer
action: blogizi draft # publishing live stays a separate, explicit stepEven the “publisher” role only runs blogizi draft, not blogizi publish. Going live is always a separate, human-confirmed action outside the automated pipeline — regardless of how many approval gates the pipeline itself has.
Runtime
How a run looks
Agents hand off through the gate; Blogizi only receives a draft.
Agent log
Writer Agent
Drafting post about our new release…
→ Generated draft with SEO frontmatter
Reviewer Agent
Reviewing draft…
→ Approved, minor edits applied
Publisher Agent
Pushing to Blogizi
- Uploading cover image
- Saving as draft
Done! Draft ready: “What's New in v2.3” — review it in your dashboard, then publish when you're ready.
Summary
Why Paperclip + Blogizi
- Multi-agent teams — separate drafting, review, and publishing roles
- Approval gates — pipelines can require explicit review before a stage proceeds
- Declarative pipelines — define the whole workflow in one config file
- Draft-first by design — even automated pipelines stop at draft; publishing live stays manual
- Open-source — Paperclip and blogizi-agent are both inspectable
CLI commands and other agent runtimes: /agent
Orchestrate the draft. You own the publish.
Paperclip coordinates the team and the gates. Blogizi holds the draft until you say go live.