Bolta Draft Post

Bolta — Draft a Post

Turn a topic into a single on-brand social post and land it in Bolta as a Draft the user can review, edit, schedule, or publish from the app.

When to use

The user wants one post written and saved to Bolta. Default outcome is a Draft — never publish or schedule unless the user explicitly asks. Route scheduling to bolta-schedule-and-batch; for "publish it now" use publish-post (admin/owner only; blocked when workspace Safe Mode is ON — use submit-for-review instead).

Tools this skill uses

Prerequisites

• workspace_id — resolve once via list-workspaces, reuse for the whole flow. Auth is automatic via the Bolta connector's OAuth grant — never ask for an API key. Default new content to Draft; confirm before publish/delete.
• At least one connected social account (from list-accounts). If none, call get-connect-link(workspace_id) (pass platform if the user named one) and share the URL — OAuth finishes in the browser; re-check with list-accounts afterwards.
• A voice source: get-voice-context. If the workspace has no voice yet, still draft, but note the post is written from the request alone and offer to set up voice.

Workflow

1. Resolve the workspace

Call list-workspaces; use the active workspace's id. Never guess a UUID.

2. Pick the target account(s)

Call list-accounts(workspace_id) (optionally filter by platform). Match the user's intent (e.g. "for LinkedIn") to the right account UUID(s). If the platform is ambiguous and more than one account exists, ask which account(s) before writing. Collect the UUIDs into account_ids.

3. Load the voice

Call get-voice-context(workspace_id). Extract tone, dos/donts, terminology, and exemplars. Keep the draft within these boundaries. For a full brand-voice pass (guideline enforcement, validation), hand off to the brand-voice-enforce skill instead of writing here.

4. Write the post

Draft content that fits the chosen platform (length, format, hashtag/emoji norms) and stays on voice. One post, ready to save.

5. Save as a Draft

Call create-post with workspace_id, content, and account_ids — or social_buckets (bucket IDs from list-buckets) to target a whole named account group in one shot. account_ids is optional for a plain draft (required only to schedule/publish). Omit requested_action (or set draft) so it lands as a Draft. Always pass an idempotency_key (any stable value for this draft) — repeating the create with the same key returns the already-created post instead of duplicating it (24h window), which makes retries safe.

6. Confirm and offer next steps

Tell the user the Draft is saved in Bolta and reviewable/editable there. Offer to schedule it (bolta-schedule-and-batch), attach media (bolta-post-media), or — only if they explicitly ask — publish now via publish-post (confirm first; publishing is public; requires admin/owner, and Safe Mode blocks it — the fallback is submit-for-review).

Failure handling

• No workspace → stop; the connector may not be authorized. Explain and ask the user to connect.
• No accounts → call get-connect-link and share the URL so the user can connect one; do not fabricate an ID.
• Error on create-post that might still have saved (fetch/template/widget errors, timeouts, anything that isn't a clear 4xx rejection) → never blind-retry. There's a known open regression where the post-preview widget shows "Failed to fetch template" even though the draft saved. First call list-workspace-posts(workspace_id) and check whether the draft landed; if it did, report success and skip the retry. If it truly didn't, retry with the same idempotency_key so a hidden success can't turn into a duplicate.
• Permission error on create-post → report the missing role/scope (creator+ needed); still show the written content so nothing is lost.
• No voice context → draft anyway, flag that it was written without stored voice, offer voice setup.
• On setup_required or plan errors (plan_required / trial_runs_exhausted), switch to the bolta-setup flow — don't retry.

Example

User: "Draft a post about our new changelog for LinkedIn."

1. list-workspaces → workspace_id.
2. list-accounts(workspace_id, platform="linkedin") → LinkedIn account UUID → account_ids.
3. get-voice-context(workspace_id) → We Are: Direct, Builder-to-builder; not Hypey.
4. Write a tight, direct LinkedIn post about the changelog.
5. create-post(workspace_id, content, account_ids, idempotency_key) — no requested_action → Draft.
6. "Saved as a Draft in Bolta. Want me to schedule it or add an image?"