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 skills/context-engine/platform-publishing-specs.md for character limits (Twitter/X: 280, LinkedIn: 3,000, Instagram: 2,200, TikTok: 2,200, Pinterest: 500), image dimensions (1:1, 4:5, 9:16, 16:9), video length caps, carousel slide limits, and link preview behavior. Create distinct variations where content cannot be shared identically across platforms.
4. Optimize posting times — the brand's data first: If the brand has post-level engagement history (exported from platform analytics: timestamps + engagement per post), write it to a JSON file and run python "${CLAUDE_PLUGIN_ROOT}/scripts/posting-time-analyzer.py" --platform {platform} --history {file} — first-party windows come back ranked with sample sizes and are the only recommendations that can earn high confidence. Without history, run it with --platform {platform} --industry {industry} --audience-type {b2b|b2c|mixed} for the DATED population baseline (baseline_as_of + capped-at-medium ceiling in the output; a stale baseline refuses with exit 3 — refresh it or supply history). Surface the output's algorithm_note — on interest-ranked feeds, content strength dominates timing. Factor in audience timezone distribution.
5. Analyze and optimize hashtags: Run hashtag-analyzer.py to evaluate proposed hashtags for reach potential, competition level, relevance score, and trending status. Recommend a balanced hashtag mix per platform — branded hashtags, niche community hashtags, and broad reach hashtags — with platform-specific counts (Instagram: 15-20, Twitter/X: 2-3, LinkedIn: 3-5, TikTok: 4-6, Pinterest: 2-5 as keyword tags).
6. Score content for brand voice: Run on each platform variation to verify alignment with brand tone, vocabulary, and messaging guidelines. Flag any variation that falls below the brand's minimum score and suggest specific edits.

Output

A structured scheduling confirmation containing:

• Scheduled post confirmations: Per-platform confirmation with post ID, scheduled date and time with timezone, and preview link or draft URL where available
• Platform-specific content: Final copy for each platform showing character count versus limit, hashtags with position (inline or comment), media attachments with dimensions, and UTM-tagged link
• Posting times with rationale: Scheduled time per platform with data-driven justification — historical engagement peak hours, audience timezone alignment, competitive posting window analysis, or user-specified timing
• Hashtag recommendations: Final hashtag set per platform with supporting metrics — estimated reach per hashtag, competition level, trending status, and relevance score
• Brand voice scores: Per-platform alignment scores with notes on tone adjustments made during variation creation and any remaining recommendations
• Media spec compliance: Confirmation that all images and videos meet platform requirements for dimensions, file size, format, aspect ratio, and video duration with any crops or adjustments applied
• UTM tracking summary: Complete UTM parameters per platform (source, medium, campaign, content) for attribution tracking in Google Analytics or the brand's analytics platform
• Cross-platform coordination notes: Posting sequence rationale if posts are staggered, and any cross-promotion references between platforms (e.g., "Full video on YouTube" link in Twitter/X post)
• Accessibility compliance: Alt text applied to all images, caption files attached to videos, and plain-language verification for accessible content across platforms
• First comment or thread status: Confirmation of scheduled follow-up comments per platform with content preview and timing (immediate after main post)
• Content calendar placement: Campaign name, content pillar, and calendar date for cross-referencing with the brand's publishing schedule
• Mentions and tags applied: Confirmation of all @mentions and account tags included per platform with handle verification status
• Execution log entries: Timestamped records per platform for audit trail, content calendar synchronization, and cross-channel scheduling coordination

Agents Used

• social-media-manager — Content formatting per platform conventions, posting time optimization, hashtag strategy and analysis, brand voice scoring, platform-specific variation creation, media asset validation, accessibility compliance, first comment scheduling, and engagement monitoring configuration
• execution-coordinator — Approval workflow, multi-platform scheduling execution via MCP servers, per-platform status verification, first comment and thread queuing, content calendar update, retry handling for failed schedules, and per-platform execution logging