Update to WoopSocial Social Scheduler

{
  "description": "Weekly social media autopilot through WoopSocial: each week read how last week's posts did, draft next week's posts in the user's voice, get approval, then schedule them. Use when the user says \"run my social media on autopilot\", \"be my social media manager\", \"do my posts every week\", \"set up a weekly content routine\". Nothing is scheduled without approval; as a recurring task, unattended runs only save drafts for review.",
  "included_files": [],
  "name": "weekly-social-autopilot",
  "skill_md_contents": "---\nname: weekly-social-autopilot\ndescription: \"Weekly social media autopilot through WoopSocial: each week read how last week's posts did, draft next week's posts in the user's voice, get approval, then schedule them. Use when the user says \\\"run my social media on autopilot\\\", \\\"be my social media manager\\\", \\\"do my posts every week\\\", \\\"set up a weekly content routine\\\". Nothing is scheduled without approval; as a recurring task, unattended runs only save drafts for review.\"\n---\n\n# Weekly social autopilot\n\nRun the same loop every week: look at last week, plan next week, draft in the user's voice, get approval, schedule. The assistant does the planning and writing; the user supplies media and approves. Nothing is scheduled without a person's yes.\n\nThe user's explicit instructions take priority over these guidelines, except that you never post, delete or change posts beyond what the user asked for.\n\n## If WoopSocial isn't connected\n\nIf no WoopSocial tools are available, say the WoopSocial connector isn't set up. The user can create an account at https://app.woopsocial.com/signup?utm_source=chatgpt-plugin&utm_medium=skill&utm_campaign=woop-plugin-v1&utm_content=weekly-social-autopilot, connect WoopSocial in the app's plugin or connector settings, sign in and retry. You can still do onboarding and draft a first week now, so offer that. Never pretend to schedule.\n\n## First run: onboarding\n\nResolve accounts first: projects_list (ask by name if several), then social_accounts_list. Use CONNECTED accounts only. Offer to connect a missing or DISCONNECTED one with oauth_create_authorization. Never show IDs.\n\nThen ask, in one short message, only what you don't know:\n\n1. **Accounts:** which of the connected accounts to post to (show them by platform and username).\n2. **Goal:** reach, traffic (clicks to a site or shop), or community (comments, DMs).\n3. **Posts per week** per platform, and preferred days and times. Be realistic about what they can supply media for.\n4. **Mix:** the kinds of posts they want (for example tips, behind the scenes, product, customer stories, opinions) and anything off limits.\n5. **Voice samples:** 3 to 5 past posts or texts they like.\n6. Time zone.\n\nThen write a short **voice and brand notes** block (10 to 20 lines): who they are, audience, tone, words and emoji they use or avoid, recurring hashtags, links, claims never to make, the weekly plan. Show it and get it approved. If you can write files, save it as `social-autopilot-notes.md` and read it at the start of every run. If you can't, ask the user to keep it and paste it next time.\n\nGet TikTok privacy options and Pinterest boards with social_accounts_get_platform_inputs, ask once, save the choices in the notes, and show them in the approval list.\n\n## The weekly loop\n\n### 1. Review last week (brief)\n\nCall social_account_posts_list with projectIds and deliveryStatus PUBLISHED, limit 100, following nextCursor. Keep posts whose deliveryCompletedAt is in the last 7 days. For each, read the latest analytics snapshot per metric. Name the top one or two posts for the goal (saves and shares for reach, clicks for traffic, comments for community; per view where views exist) and one that trailed. Three to five lines, no more.\n\nHonesty: only posts sent through WoopSocial count. Missing metrics mean the platform doesn't report them, 0 is real, posts under about 48 hours old are still moving, and data refreshes about daily. If there's no data yet, say so and plan from the notes alone. For a full breakdown, social-media-report is an option.\n\nAlso list NOT_STARTED posts: SCHEDULE_FOR_LATER ones fill slots already, so don't double-book them. DRAFT ones may come from an unattended run; start the plan from them instead of drafting again.\n\n### 2. Plan next week\n\nMake a table: day, time (user's zone), platform, post type, topic, which part of the mix, and the media it needs. Follow the posts-per-week and mix from the notes. Lean towards what worked last week, and keep one slot for a test.\n\n### 3. Draft every post\n\nWrite each post in the voice from the notes, adapted per platform (a strong first line, the platform's length and style, one clear ask that fits the goal). Never invent prices, results, reviews, quotes or claims; use a clearly marked `[placeholder]` and list them. Never schedule a post that still contains a placeholder. Ask for the fact, or save the post as a draft and flag it.\n\n### 4. Approve\n\nShow the week post by post: day and time, account, post type, full text, media needed or attached. The user can approve, edit, swap or drop each post. Apply edits and show the changed posts again. Say which posts will be saved as drafts because their media is missing. Ask for one clear yes on the final list.\n\n### 5. Schedule\n\nFor each approved post, one at a time:\n\n1. **Media:** for local files, upload them (media_uploads_create_session with projectId and fileSizeInBytes, PUT each part to its uploadUrl, every part but the last exactly partSizeInBytes, then media_uploads_complete_session). Files already in WoopSocial: find them with media_list. If uploads are blocked, ask the user to allow `*.r2.cloudflarestorage.com` (in the app's code execution or sandbox network settings). If you can't make HTTP requests at all, say so: the user can upload in the WoopSocial app (then find it with media_list), and posts that still lack media are saved as drafts (step 3).\n2. **Build the payload:** one content item, `schedule: {type: SCHEDULE_FOR_LATER, scheduledFor: <UTC>}`, the account targets with their platform fields, and `retryPolicy: {maxRetries: 2, delaySeconds: 300}` unless they don't want retries.\n3. **No media on a platform that needs it** (Instagram, TikTok, YouTube, Pinterest): don't schedule it. Save it as a DRAFT (`schedule: {type: DRAFT}`, no date) and flag it in the summary so the user can add media in the WoopSocial app or send the file next time. If posts_validate rejects even the draft, keep the post in the summary as text to add later, and don't create it.\n4. posts_validate, fix and re-validate, then posts_create. It returns `isValid` and a list of `errors` (each with a `path` and a `message`); treat `isValid: false` as a failure even though the call succeeded. If an error names a field you don't recognize, schema_describe shows the tool's full input schema. If a fix changes the text, media or settings the user approved, show the change and get a yes before posts_create. On a 429, wait briefly and retry.\n\nThen report: scheduled posts by day and platform, drafts waiting for media, and anything that failed validation and why.\n\n## Making it weekly\n\nSuggest running it as a recurring task where the client supports it: the app's scheduled or recurring tasks. A good slot is a fixed day before the week starts. The task prompt should say: read `social-autopilot-notes.md`, review last week, plan and draft next week.\n\n**Unattended runs** (no person in the conversation): only create DRAFT posts and write a summary of what was drafted and why. Never schedule or publish. If `social-autopilot-notes.md` can't be read, stop and write a note saying so instead of drafting. The user reviews the drafts later, in WoopSocial or in a follow-up conversation, and approves scheduling then. In an attended run, the normal approval in step 4 applies.\n\nTo schedule approved drafts later: posts_get each draft, posts_create the same payload with SCHEDULE_FOR_LATER and the approved time (validate first), then delete the draft (posts_delete) once the new post is confirmed. The approval covers these deletes.\n\n## Never\n\n- Schedule or publish without a person's explicit yes in this conversation.\n- Say a draft is set for a date. Drafts are undated; put the planned day in the summary instead.\n- Invent results, benchmarks or claims.\n- Show internal IDs.\n"
}