Draft and gate-check social posts
Turn a product update or a week of usage signal into ranked story directions, draft the posts, and hold them for approval before anything publishes.
Copy this prompt to start your first task:
What is this workflow?
"Draft and gate-check social posts" turns a product update or a week of channel activity into ranked story directions, then drafts the actual LinkedIn and X posts for the one you pick. The teammate writes in your real voice — pulled from prior posts, notes, and team chat — instead of generic brand boilerplate, and if a draft is built around a screenshot, it reads the image first and writes down exactly what's visible rather than inventing details. Every draft is held for approval: nothing publishes until a person reviews the exact final text.
How to use this workflow
Hire a content teammate
Open AI Teammates in the sidebar, click Hire AI Teammate, and pick the Content Writer template. The default bio is generic long-form writing. Replace it on the Profile step so it knows this job is ranking story directions and drafting posts, held for approval:
Confirm the name and click Create teammate. They land in their own channel, which is where you'll send everything below. More on hiring →
Point it at what happened
Add the teammate to #general first, because it can only read channels it's a member of.
Ask for the drafts
Hold everything for approval
By default, review happens in the channel before you post anything yourself. If you want a stricter approval step, say so in its instructions:
Turn the weekly cycle into an automation
Open Automations in the sidebar and click Create via Chat. On Home, choose this teammate and send the prefilled scheduled-task starter. When the interview asks what to schedule, answer with the recurring job below. Add the teammate to #content too, so the drafts have somewhere to land:
Publishing waits for you either way: posting to LinkedIn or X is an external, irreversible action, so Helio holds it for your sign-off regardless of what a teammate's instructions say — this workflow's own "hold for approval" step just makes that explicit. See Control for what runs on its own versus what always pauses for you.
Tips for Better Results
| Tip | Description |
|---|---|
| Give it real signal, not just a request | Point it at actual product updates and channel activity so it ranks directions off your own signal, not a generic brainstorm. |
| Add it to the channels it needs to read | It can only read channels it's a member of — add it to #general (or wherever updates land) and #content before asking it to rank or post anything. |
| Let it read screenshots before it drafts | When a draft is built around a screenshot, it's instructed to read the image first and write down exactly what's visible — worth checking that description before you approve. |
| Ask to see the exact final text | Approval only works if you see the literal post. Tell it never to say a post is ready without showing the exact text and any image brief. |
Common Questions
Content
Back to the content use case overview.
Create brand guidelines
Turn a positioning line into a guideline every asset gets checked against.