# Draft and gate-check social posts (/use-cases/content/social-drafts)



Copy this prompt to start your first task:

<Prompt>
  Look at this week's product updates and channel activity, rank the top story directions with reasoning for each, and draft a LinkedIn and X post for the best one. Hold everything for my approval before anything publishes.
</Prompt>

<LivePreview component="NewThread" scenario="{ draft: &#x22;Look at this week's product updates and channel activity, rank the top story directions with reasoning for each, and draft a LinkedIn and X post for the best one. Hold everything for my approval before anything publishes.&#x22; }" />

## What is this workflow? [#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 [#how-to-use-this-workflow]

<Steps>
  <Step>
    ### Hire a content teammate [#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:

    <Prompt>
      You turn a product update or a week of channel activity into ranked story directions with your reasoning for each, matched to our actual voice from past posts, notes, and team chat rather than generic brand boilerplate. When a draft is built around a screenshot, read the image first and write down exactly what's visible; never invent details to make it sound more impressive. Nothing publishes until a person reviews the exact final text in the channel.
    </Prompt>

    Confirm the name and click **Create teammate**. They land in their own channel, which is where you'll send everything below. [More on hiring →](/ai-teammates/hire-an-ai-teammate)

    <LivePreview component="CreateAssistantPage" scenario="{ focus: &#x22;profile&#x22;, initialState: { start: &#x22;template&#x22;, templateRef: &#x22;@helio/content-writer&#x22;, name: &#x22;Content Writer&#x22;, bio: &#x22;You turn a product update or a week of channel activity into ranked story directions with your reasoning for each, matched to our actual voice from past posts, notes, and team chat rather than generic brand boilerplate. When a draft is built around a screenshot, read the image first and write down exactly what's visible; never invent details to make it sound more impressive. Nothing publishes until a person reviews the exact final text in the channel.&#x22; } }" />
  </Step>

  <Step>
    ### Point it at what happened [#point-it-at-what-happened]

    Add the teammate to #general first, because it can only read channels it's a member of.

    <Prompt>
      Look at this week's product updates and #general activity. Rank the top 2-3 story directions worth posting about, and tell me why each one's worth it before you draft anything.
    </Prompt>

    <LivePreview
      component="AssistantChat"
      scenario="{ assistantName: &#x22;Content Writer&#x22;, messages: [
    { author: &#x22;user&#x22;, text: &#x22;Look at this week's product updates and #general activity. Rank the top 2-3 story directions worth posting about, and tell me why each one's worth it before you draft anything.&#x22; },
    { author: &#x22;assistant&#x22;, text: &#x22;Looking at this week's shipped updates and #general now. I'll rank the top 2-3 directions with my reasoning for each, then wait for your call before drafting anything.&#x22; },
  ] }"
    />
  </Step>

  <Step>
    ### Ask for the drafts [#ask-for-the-drafts]

    <Prompt>
      Draft a LinkedIn and an X post for the direction we picked. If it's built around a screenshot, read the image first and write down exactly what's visible. Don't invent details to make it sound more impressive.
    </Prompt>
  </Step>

  <Step>
    ### Hold everything for approval [#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:

    <Prompt>
      Never tell me a post is ready to publish without also showing me the exact final text and any image brief.
    </Prompt>
  </Step>

  <Step>
    ### Turn the weekly cycle into an automation [#turn-the-weekly-cycle-into-an-automation]

    Open **Automations** in the sidebar, click **Create via Chat**, and pick this teammate in the New Thread composer that opens. Add the teammate to #content too, so the drafts have somewhere to land:

    <Prompt>
      Every Monday, look at last week's product updates and channel activity. Rank the top 2-3 story directions, draft a LinkedIn and X post for the top one, and post the drafts to #content for approval. Don't publish anything yourself.
    </Prompt>

    <LivePreview component="NewThread" scenario="{ populated: false }" />
  </Step>
</Steps>

**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](/ai-teammates/control) for what runs on its own versus what always pauses for you.

## Tips for Better Results [#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 [#common-questions]

<Accordions type="single">
  <Accordion title="Does anything publish automatically?">
    No. Every draft is held for approval — nothing publishes until a person reviews the exact final text in the channel.
  </Accordion>

  <Accordion title="Which channels can it use as signal?">
    Only channels it's already a member of. Add it to #general, or wherever the relevant product updates and activity happen, before asking it to rank directions.
  </Accordion>

  <Accordion title="Does it make up details when a post is built around a screenshot?">
    No — it's instructed to read the image first and write down exactly what's visible, not invent details to make it sound more impressive.
  </Accordion>

  <Accordion title="Can this run on a schedule instead of me asking each time?">
    Yes. Set it up as an automation to rank directions and draft posts weekly. It still posts the drafts to a channel for approval rather than publishing them itself.
  </Accordion>

  <Accordion title="How does it match our actual voice instead of generic copy?">
    It drafts from your prior posts, notes, and team chat, not brand boilerplate — the more real signal it has, the closer the draft matches how you actually write.
  </Accordion>
</Accordions>

<Cards>
  <Card title="Content" href="/use-cases/content" description="Back to the content use case overview." />

  <Card title="Create brand guidelines" href="/use-cases/design/brand-guidelines" description="Turn a positioning line into a guideline every asset gets checked against." />
</Cards>