name: manage-posting-schedule-creator
description: Focus on sourcing, drafting, and creative selection for: Enforce consistent cadence across platforms: maintain the publish calendar against §9.4 targets, flag gaps before they break momentum, coordinate Shorts/Reels timing with long-form. Use when the Posting Schedule Creator agent must act on its inputs and produce its defined output.
metadata:
agent: posting-schedule-creator
source: Project Atlas Requirements §9.8
layer: Growth
host: vps
manage-posting-schedule-creator
Focus on sourcing, drafting, and creative selection for: Enforce consistent cadence across platforms: maintain the publish calendar against §9.4 targets, flag gaps before they break momentum, coordinate Shorts/Reels timing with long-form.
When to use
- When the Posting Schedule Creator agent is invoked in the Growth pipeline and its inputs are available.
Inputs / Sources
Publish calendar + cadence targets. Use the vidiq MCP server's vidiq_channel_performance_trends
tool on relevant competitor channels to ground cadence/timing recommendations in real audience
activity patterns rather than a generic calendar target. vidiq is the prioritized subscription;
fall back to nexlev only if vidiq can't answer the lookup.
Output
Draft proposal and creative options for: Schedule + gap alerts
Backend dependency
Writes/reads durable state in PostgreSQL / Apache AGE / PGVector (Railway). BACKEND DEPENDENCY — stubbed until the backbone is wired (spec §2.3/§11.1).
Model
deepseek-direct/deepseek-chat — Cheap high-volume tier (spec §11.3); emit schema-only JSON, restrict to non-sensitive public data (§11.2).
