{"id":71157,"plugin_id":"plugin_asdk_app_6acfc6735c388191a829d4dca3ecb626","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-29T19:13:15.973Z","digest":"92812dfccdedacf7becc097fc4ff16edaadd6fbe4f24978b02634f4c76b969e0","against":null,"payload":{"description":"Plan a week or month of social media posts with PostEverywhere. Use when the user asks for a content calendar, a posting plan, a batch of posts, \"fill my queue\", or a campaign across several days or platforms.","included_files":[],"name":"plan-content-calendar","skill_md_contents":"---\nname: plan-content-calendar\ndescription: Plan a week or month of social media posts with PostEverywhere. Use when the user asks for a content calendar, a posting plan, a batch of posts, \"fill my queue\", or a campaign across several days or platforms.\n---\n\n# Plan a content calendar\n\nTurn a goal (a launch, a campaign, \"keep my accounts active\") into a set of drafts the user can review before anything is scheduled.\n\n## Steps\n\n1. **Understand the plan.** Ask for anything missing: the topic or goal, the date range, which accounts, and how often to post. Default to one post a day per platform when the user doesn't say.\n2. **See what's already there.** Call `list_posts_advanced` with `status: \"scheduled\"` and the date range, so the new plan doesn't clash with posts already booked. Call `get_queue` to see the user's regular posting slots.\n3. **Group it.** If the posts belong to one campaign, call `list_campaigns`, and create one with `create_campaign` if the user wants it grouped.\n4. **Draft the posts.** Write each post for its platform (see the `schedule-social-posts` skill for the rules). Vary the angle across days; don't post the same text daily.\n5. **Show the plan.** Present it as a table: date and time, accounts, and the first line of each post. Ask the user to confirm or change it.\n6. **Create the drafts.** After the user confirms, send them with `bulk_create_posts` (up to 50 per call). Create them as drafts (`draft: true` on each) unless the user said to schedule them straight away. Use each post's own `scheduled_for`, or `use_queue: true` to let the queue pick the times.\n7. **Report back.** List what was created and what, if anything, failed validation and why.\n\n## Good defaults\n\n- Spread posts through the day instead of stacking them at the same minute.\n- Keep one idea per post.\n- When the user has a website or product link, include it where the platform allows links. Don't make up URLs.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}