/schedule-social

name: schedule-social
description: "Schedule social posts to Twitter/X, Instagram, LinkedIn, TikTok, YouTube, and Pinterest through connected platform MCPs — generating per-platform copy variations, hashtag mixes, media-spec validation, UTM-tagged links, and posting-time analysis (the brand's own engagement history first, dated population baselines second), then verifying each queued post and updating the content calendar. Nothing goes live without the mandatory execution gate: a full scheduling summary you must explicitly approve first. Triggers on \"/digital-marketing-pro:schedule-social\", \"schedule this post for Monday\", \"publish this across our social channels\", \"queue the launch announcement on LinkedIn and X\", \"post this everywhere at the best times\". Reads the brand profile, guidelines, and platform publishing specs."
disable-model-invocation: false
argument-hint: "[platform]"

/digital-marketing-pro:schedule-social

Purpose

Schedule social media posts to one or more platforms with platform-specific formatting, optimized posting times, hashtag strategy, and engagement monitoring setup. Handles multi-platform distribution from a single content brief by generating tailored variations that respect each platform's character limits, media specs, and audience conventions while preserving the core message across all channels.

Execution gate (MANDATORY — cannot be skipped)

1. Present the full preview — recipients / spend / changes / compliance — as an **Execution Summary** before touching any live system. 2. The user must type `yes` (or an equivalent explicit approval). ANY other input — ambiguous, implied, partial, or absent approval — cancels the run. 3. Never proceed on ambiguous input. Never auto-retry a failed execution; a failure needs human review before any re-run. 4. Record the approval with `python "${CLAUDE_PLUGIN_ROOT}/scripts/approval-manager.py" --brand {slug} --action create-approval --data '{"type":"schedule-social","platform":"{platform}","content_summary":"...","risk_level":"<tier>"}'` **before** executing, then `python "${CLAUDE_PLUGIN_ROOT}/scripts/approval-manager.py" --brand {slug} --action mark-executed --id {approval_id} --data '{"execution_result":"success","platform_response":"..."}'` after the platform confirms success.

Input Required

The user must provide (or will be prompted for):

• **Post content**: Core message text, along with any images, video, carousel assets, or links to include — can be a single unified draft or pre-written per-platform variants
• **Target platforms**: Which platforms to post on — Twitter/X, Instagram (feed, Stories, Reels), LinkedIn (post or article), TikTok, YouTube (Shorts or Community), or Pinterest — must have corresponding MCP servers connected
• **Posting date and time**: Specific date and time per platform with timezone, or "optimal" to use data-driven timing recommendations based on audience engagement patterns
• **Hashtags**: Specific hashtags to use, a topic for auto-suggestion, or "auto" to generate hashtags based on content analysis, trending tags, and brand hashtag strategy
• **Platform-specific variations**: Any per-platform tweaks — different copy length, different images or aspect ratios, different CTAs, tone adjustments, or platform-native features (Instagram polls, LinkedIn document carousels, Twitter/X threads)
• **Link and UTM parameters**: URL to include with UTM tracking parameters (source, medium, campaign, content) for attribution, or auto-generate UTMs based on campaign naming conventions from brand profile
• **Media assets**: Image files or URLs with aspect ratio preferences per platform, video files with duration compliance, or carousel image sets in posting order
• **Engagement instructions**: Whether to set up reply monitoring, comment response guidelines, engagement boost triggers (promote if engagement exceeds threshold), or cross-posting rules
• **Content calendar context**: Optional — campaign name or content pillar this post belongs to, for calendar tracking and thematic consistency across the publishing schedule
• **Accessibility requirements**: Alt text for images, video captions or subtitle files, and any accessibility-specific formatting (plain language, high contrast text overlays)
• **First comment or thread**: Optional — follow-up comment to post immediately after the main post (Instagram first comment for hashtags, Twitter/X thread continuation, LinkedIn engagement prompt)
• **Geo-targeting**: Optional — restrict post visibility to specific regions or languages where supported by the platform (LinkedIn geo-targeting, Facebook location targeting)
• **Cross-promotion references**: Optional — references to related content on other platforms to include in the post (e.g., "Watch the full video on YouTube" or "Read the full article on our blog")
• **Mentions and tags**: Optional — accounts to @mention or tag in the post (partners, collaborators, influencers, featured customers) per platform tagging conventions

Process

1. **Load brand context**: Read `~/.claude-marketing/brands/_active-brand.json` for the active slug, then load `~/.claude-marketing/brands/{slug}/profile.json`. Apply brand voice, compliance rules for target markets (`skills/context-engine/compliance-rules.md`), and industry context. Also check for guidelines at `~/.claude-marketing/brands/{slug}/guidelines/_manifest.json` — if present, load restrictions. Check for agency SOPs at `~/.claude-marketing/sops/`. If no brand exists, ask: "Set up a brand first (/digital-marketing-pro:brand-setup)?" — or proceed with defaults. 2. **Verify connected social MCPs**: Check which social media platform MCP servers are connected and confirm they cover all the user's target platforms. List any missing connections with setup instructions. Verify API permissions include scheduling capability for each platform. 3. **Format content per platform specs**: Adapt the content for each platform's requirements — consult `sk