schedule-week

Installation
SKILL.md

Schedule a week

Use this for "plan next week's posts", "fill my content calendar", "schedule this week across my channels". It plans the week, writes every post the way that channel's skill writes it, shows the whole week for approval, then schedules all of it in one pass. Uplika's server holds each post and sends it at its time.

1. Channels, dates and time zone

  1. Call select_channels with no scope to get the connected candidates and let the person choose (or all). Never assume a channel is connected; if nothing comes back, send them to https://uplika.com/dashboard/connections. Read out skipped (expired or not-yet-live channels, with the sentence and reconnect link it gives). If it answers workspace_required, show the workspaces it lists, ask which one, and pass workspaceId on every later call.
  2. Ask which time zone the times are in, and use the one the person states. Do not guess it from their language, their location or this machine.
  3. Turn "next week" into real dates in that time zone and say them back.
  4. Ask what the week should hold: topics or content pillars, source material, dates that matter (a launch, an event), how often each channel should post, and preferred times. If they have no times in mind, do not invent "best times": suggest times from their own past results (the performance-review skill reads them) and say that is where the suggestion came from. With no results to go on, say so and let them pick.

2. The plan table

Before writing any post, show a table with a row per day and a column per chosen channel. Each cell holds the topic, the format (single post, chain, carousel, reel, story, video, blog post) and the time, or stays empty.

  • Read each channel's rules from list_platforms (limits, whether media is required, and the features table) so the plan only holds formats that channel takes. Do not plan from memory.
  • Spread the formats. Do not stack the heavy pieces (a video, a blog post, a long chain) on one day, and space posts on the same account apart instead of sending several at the same minute.
  • Leave a slot open for something timely if the person wants one.
Installs
26
GitHub Stars
3
First Seen
Oct 9, 2026