Update to dopost

{
  "description": "Plan, draft, schedule, publish, and review social-media content with dopost when the user asks to manage their connected social accounts.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 239
    }
  ],
  "name": "dopost-social-content",
  "skill_md_contents": "---\nname: dopost-social-content\ndescription: Plan, draft, schedule, publish, and review social-media content with dopost when the user asks to manage their connected social accounts.\nmetadata:\n  short-description: Safely manage social content with dopost\n---\n\n# dopost social content\n\nUse this skill for requests involving a user's dopost workspaces, connected social accounts, posts, recurring content, media, or analytics.\n\n## Access and account state\n\n- 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 Pro or Agency access is required and do not imply that a purchase can be completed in ChatGPT.\n- 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.\n- 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.\n\n## Drafting and publishing\n\n- Draft or revise copy in the conversation first. Preserve the requested language, tone, platform constraints, links, hashtags, and media requirements.\n- 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.\n- 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.\n- 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.\n- Deletions are destructive: identify the exact post or media item and obtain explicit confirmation immediately before calling `delete_post` or `delete_media`.\n\n## Reading and analytics\n\n- For read-only requests, use the narrowest tool that answers the question and summarize the result in plain language. Include the data-through/freshness information when analytics provide it.\n- Explain partial, unavailable, or stale metrics rather than filling gaps with estimates. Analytics may require the `analytics:read` scope and an active paid plan.\n\n## Public-media downloads\n\n- Only assist with supported public YouTube, Instagram, or TikTok URLs when the user owns the content or has permission to use it. Refuse private, access-controlled, or clearly unauthorized download requests.\n- Explain that returned download URLs are temporary and that the tool prepares a URL rather than placing binary media into the conversation.\n\n## Communication\n\n- Match the user's language; reply in Spanish when the user writes in Spanish.\n- Be transparent that dopost is an external service and that account connection and plan eligibility are handled by dopost. Do not present ChatGPT as completing signup, billing, upgrades, or purchases.\n"
}