Cross-Platform Campaign

Build one coherent campaign while respecting how each social channel works. Compose the generate-image and simplified-social capabilities when campaign visuals are needed.

Guardrails

Existing explicit authorization for unchanged content, accounts, timing, media, and comments is sufficient; ask only when that authorization is missing or the proposed effects change.

• Do not publish or schedule without explicit approval of the final campaign matrix.
• Create safe previews with action: "draft" when the user asks to prepare the campaign.
• Image generation spends credits. Proceed when the image request is explicit; confirm first when visual generation is ambiguous.
• Carry a generated image's permanent asset_id into social media; never rely on its expiring signed URL.
• Pause affected connected operations on authorization failure. Continue planning or requested accountless drafts when no accounts are connected; omit account_ids. Scheduling, queueing, and account analytics require suitable connected accounts.
• Use a native media preview when the client supports it and the user wants to review the result. Otherwise show a usable link. Refresh expired asset URLs; do not download remote media merely to bypass client display restrictions. Review bundles and other web pages remain links.

Workspace and handoff

Before connected operations, use simplified-workspace when the client/workspace/teamspace is named or uncertain. Resolve the exact numeric teamspace and carry its space_id on every related account, analytics, asset, generation, draft, tag, review, and continuation call. Re-list scoped resources after switching clients; stop on access failures rather than falling back to another space. Pass the resolved context to every delegated skill.