dopost-social-content8.14 KB
View saved version →
---
name: dopost-social-content
description: Plan, draft, schedule, publish, and review social-media content with dopost when the user asks to manage their connected social accounts.
metadata:
short-description: Safely manage social content with dopost
---
# dopost social content
Use this skill for requests involving a user's dopost workspaces, connected social accounts, posts, recurring content, media, or analytics.
## Access and account state
- The hosted ChatGPT app requires an authenticated dopost OAuth connection with API access on at least one workspace. If the connection is missing, ask the user to connect dopost. If the connection is rejected because no workspace has API access, explain that Creator, Pro or Agency access is required and do not imply that a purchase can be completed in ChatGPT.
- Resolve the target account from the user's wording. Use `list_accounts` when the account, workspace, or platform is ambiguous; do not ask the user to choose a workspace when an account or resource ID already identifies it.
- If there is no matching connected account, explain what is missing and ask the user to connect it in dopost. Never invent account IDs, posts, metrics, or permissions.
## Drafting and publishing
- Draft or revise copy in the conversation first. Preserve the requested language, tone, platform constraints, links, hashtags, and media requirements.
- Before any write operation, show the final text, target account(s), media, publish time/time zone, and recurrence when applicable. Wait for explicit user approval of that exact plan.
- Only then call `publish_post`, `reschedule_post`, `create_recurring_post`, or another write tool. Treat “draft”, “prepare”, or “what would you post?” as non-publishing requests.
- After a successful write, report the returned status, post ID when useful, destination, and scheduled/publication time. If a write fails, report the error without claiming it was published.
- Deletions are destructive: identify the exact post or media item and obtain explicit confirmation immediately before calling `delete_post` or `delete_media`.
## Drafts, groups, and platform checks
- For a request to save a draft in dopost, use `publish_post` with `draft: true` and omit `publishAt`. For a request to propose copy, draft in the conversation without saving. Saved drafts return `status: "draft"` and a `postId`, with no publication job or monthly publishing charge; readback uses `DRAFT`. Continue editing or publish them in the dopost dashboard.
- Draft content can be incomplete or exceed platform publishing limits. Its attached files still pass upload size, format and integrity checks. Never switch to publishing just to save a draft.
- Before publishing or scheduling, call `get_platform_limits` once per distinct destination platform. Use the chosen post type's requirements to check text, media count, thread entries and each account's overrides. Only assess file properties from verified metadata; filenames and URLs do not establish dimensions, duration or codecs. Explain known violations with the affected field, actual value and limit. The server validates actual received files before creating posts.
- Use `accountId` for one account or `posts` for a group of 1–20 distinct active accounts in the same workspace. Each item requires `accountId` and inherits top-level `text`, `media`, `platformOptions`, `replyTo` and `thread`. A supplied item field replaces the entire default field; arrays and objects are not merged. Use `media: []` to clear shared media for one account.
- Put `draft`, `publishAt` and `timezone` only at the top level. Shared media URLs are imported and inspected once per request; different media URLs are prepared separately. A group validation failure rejects the whole request before creating posts and identifies `accountId`, zero-based `postIndex` and the affected field.
- A group returns `groupId` and a `postId` per account. Track each post ID; a group ID is not a post ID, and delivery
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.
