Social Media Scheduling

npx skills add https://secondshiftos.com/skills/social-media-scheduling.md

https://secondshiftos.com/skills/social-media-scheduling.md

---
name: social-media-scheduling
description: Run a local business's social posting as weekly preparation: build the content calendar, draft every post in the owner's voice, size every image for its surface, and stage one pack the owner reviews once. Use when a business wants steady Facebook, Instagram, or X posting without handing an agent the keys. Nothing posts, and nothing schedules, until the owner has reviewed the pack.
license: MIT
metadata:
  author: Second Shift
---

# Social Media Scheduling

This skill is preparation, not posting. The agent builds the whole week;
the owner reviews it once; only then does anything get scheduled, through
the platforms' own scheduling tools, on the owner's own accounts.

There is no Second Shift social scheduler, and this skill does not use the
Second Shift pipe. It works for any local business, tenant or not, with
the owner's own files, photos, and platform accounts.

## The doctrine

- The agent prepares everything: calendar, captions, images, sizes.
- The owner's review is the gate. An unreviewed post does not exist yet.
- Nothing auto-posts unreviewed, ever. Approval of last week's pack is
  not approval of this week's.
- Scheduling happens only in the platforms' own native tools (for
  example Meta's planner for Facebook and Instagram, or X's own
  scheduler). No third-party poster standing between the owner and their
  accounts.

## Step 1: Learn the voice

Before the first calendar, gather what the owner sounds like: posts they
wrote and liked, how they talk to customers in person, the names of their
people, products, and town, spelled the way they spell them. Note what is
off limits (competitors, politics, other people's kids, before-and-after
photos without permission). Write this down once and reuse it; ask again
only when something changes.

## Step 2: Build the week's calendar

One week per pack. For each surface the business actually uses, lay out
the days and the mix. A steady local rhythm to start from:

- One offer or announcement post.
- One proof post: finished work, a full parking lot, a real result.
- One helpful post: a tip, a how-to, a myth corrected.
- One community post: the town, a partner business, the team.

Tie the calendar to the business's own week first (specials, events,
seasonal work) and fill gaps from the mix. Every slot names its surface,
because the surface decides the image size and the caption length.

## Step 3: Draft every post in full

Write the finished caption for every slot, not a topic line. Draft in the
owner's voice from step 1: their words, their offers, their town. Claims
come only from facts the owner gave you; no invented reviews, results, or
counts. Where a post needs a fact you do not have, leave a visible blank
and list it in the pack's open questions instead of guessing.

## Step 4: Size every image for its surface

Name the surface first, then make the image at that surface's size:

| Surface | Size |
|---|---|
| Facebook post | 1200x630 |
| Instagram portrait post | 1080x1350 |
| Instagram square post | 1080x1080 |
| Facebook cover | 1640x924 |
| X post | 1600x900 |

Check every finished image with your own eyes: the crop is right, the
product looks real, and nothing important is clipped by the edges or the
platform's own overlays. Then spell: every proper name and every word
baked into the artwork gets spelled out letter by letter against the
owner's own source. Artwork garbles names silently, and an eyeballed
check is not a spelling check.

## Step 5: Stage the pack

Deliver the week as one pack the owner can review in a single sitting:

1. The calendar: day, surface, and slot for every post.
2. Every caption, written in full, in day order.
3. Every image, at its surface size, beside its caption.
4. The open questions and blanks the owner needs to fill or confirm.

One pack, one review. Do not drip posts at the owner one at a time
through the week; the batch is the point.

## Step 6: Schedule, only after review

When the owner has reviewed the pack and approved it, schedule each post
in the platform's own native scheduling tool, on the owner's accounts, at
the calendar's times. If a scheduling step needs the owner's own hands
(a login, a confirmation tap), hand it over plainly and wait; never work
around an account check. If native scheduling is not available for a
surface, say so in the pack and leave that post ready to publish by hand
at its slot. Nothing in this step happens before the review in step 5,
and edits the owner made during review are the versions that schedule.

## Step 7: Read last week before building the next

Start each new pack by looking at what the platforms themselves report
about the week just posted: which posts earned replies, saves, calls, or
clicks, and which fell flat. Use the platforms' own numbers only; do not
invent reach or engagement you cannot see. Then adjust: more of the kind
that earned attention, retire the kind that did not, and carry one
question into the new week (a new slot type, a different day, a
different hook). Bring that one-paragraph readout to the top of the new
pack, so the owner sees the week improving, not just continuing.

## The ground rules

- The owner reviews before anything schedules. Every week, every pack.
- Work only in the owner's own accounts and tools. This skill grants no
  access and moves nothing to any third-party service.
- Names get spelled letter by letter. Images get looked at, not assumed.