Social Ops Automation

Design the posting rhythm for an automated social operation — daily slots anchored to one timezone, auto-fill versus manually-scheduled slot types, per-channel timing adaptation, and a queue-depth target the agent loop maintains. Use when someone asks "when should we post", "set up our posting schedule", "how many posts per day", or "design the queue for our scheduler". Do NOT use for deciding content themes or pillars — that is strategy/calendar territory; for connecting and probing the scheduler, use social-stack-bootstrap; for keeping the queue actually filled, use scheduling-agent-loop.

Build the batch visual-asset production system for an automated social operation — a locked format set with exact dimensions, brand constants as declared inputs, a one-deliberate-risk composition rule, programmatic SVG-to-PNG rendering, and a staged-media-first rule that checks the scheduler before generating anything new. Use when someone asks "set up our social image pipeline", "produce this week's post images", "batch-generate assets for the queue", or "systematize our social visuals". Do NOT use for one-off OG images or quote cards — use social-image-designer; for captions and copy, use caption/thread skills; for defining the brand palette and type itself, use brand-guidelines or color/typography system skills.

Run the recurring maintenance pass that keeps an automated social queue healthy — audit scheduled drafts for stale content, check staged media, fill the queue to its depth target, verify recent publishes against known API inconsistencies, and report every manual action needed. Use when someone says "run the social queue check", "fill the queue", "is next week's social covered", or wants a recurring/scheduled social posting agent. Do NOT use for first-time setup — use social-stack-bootstrap; for changing slot times or depth targets, use posting-cadence-designer; for producing the images themselves, use social-asset-pipeline.

Migrate an automated social operation from one scheduler platform to another without dropping posts — an overlap window with split channel ownership, a dated cutover keyed to the last scheduled draft, per-channel handoff verification, and a single governing takeover document. Use when someone says "we're moving from Typefully to Postiz", "migrate our scheduler", "switch social tools without losing the queue", or is running two schedulers during a transition. Do NOT use for first-time scheduler setup — use social-stack-bootstrap; for ongoing queue maintenance during or after the migration, use scheduling-agent-loop.