The Content Studio kit gives your AI four workflows for a content team: Blog Post, Social Post, Newsletter Issue and Content Repurpose. Each starts from a brief, saves every draft as a task note, and stops for your approval before anything is published or sent. A post becomes the source for the other three.
4 templates · 20 steps · 6 approvals · 4 loops back
one chip per stored step · square chips wait for a person
Four workflow templates, installed together. Each one is a stored workflow your AI client receives one step at a time over MCP.
01 · 6 steps · 2 approvals
Take a blog post from brief to published draft. The AI drives through Outline, Draft, Edit, and a final read-through.
02 · 4 steps · 1 approval
Take a social post from brief to ready-to-publish. The AI drives through Draft Variants and a Polish checkpoint.
03 · 5 steps · 1 approval
Build one newsletter issue from theme to send. The AI drives through Curate, Draft, and a send-review checkpoint.
04 · 5 steps · 2 approvals
Turn one piece of content into several formats. The AI drives through Angles, Produce, and a review checkpoint.
Blog Post produces the long-form source. Content Repurpose turns it into a version per channel, Social Post writes a single post with three hooks, and Newsletter Issue curates it into the next issue. Each runs on its own task with its own approvals, and each one's saved output is the next one's input.
| From | To | How the work moves |
|---|---|---|
| Blog Post | Content Repurpose | The approved draft is the source Content Repurpose captures at Source Intake. |
| Blog Post | Newsletter Issue | The post becomes the lead story at Theme or one of the curated items. |
| Content Repurpose | Social Post | Both write social copy: Repurpose one version per channel, Social Post three hooks for one platform. |
Each template runs on its own task. They connect through what a finished run leaves on record, not through a shared run.
Every approval step in the kit, read from the stored workflows. The run holds at each one until you answer.
| Template | Approval step | If you reject |
|---|---|---|
| Blog Post | Outline step 2 | no rejection path; approve to continue |
| Final Review step 5 | back to Edit | |
| Social Post | Polish step 3 | back to Draft Variants |
| Newsletter Issue | Send Review step 4 | back to Draft |
| Content Repurpose | Angles step 2 | no rejection path; approve to continue |
| Review step 4 | back to Produce Versions |
An illustrative run, labelled as an example. The step names are the templates' real steps.
Blog Post takes a brief, you approve the outline, the AI drafts and edits, and you approve the final read-through.
Content Repurpose proposes a LinkedIn angle and a thread angle. You approve the angles, it produces both, you approve the set.
Social Post drafts three hooks for the launch. You pick the story variant; it polishes and you approve.
Newsletter Issue leads with the post, curates four items, and waits for your pre-send approval.
Connect your AI client first, then install the kit from the catalog in the ConvOps app. See how to connect a client
Installed templates are workflows in your workspace. Ask your AI to change one in plain words; the edit lands on the step that needs it.
new chat
more example prompts
Blog Post has two (outline and final), Content Repurpose two (angles and set), Social Post one and Newsletter Issue one. You can remove any as trust grows.
No. Each workflow ends with approved, ready-to-publish copy saved as a task note. You or your AI client publish it with the tools you already use.
The Free plan includes 3 workflow templates and this kit has 4, so the full kit needs Pro or above.
Any MCP client connected to ConvOps. Verified clients: Claude Code, Claude (desktop, web, Cowork), OpenAI Codex, ChatGPT, Cursor, OpenCode. None of its workflows needs a repository.