social-calendar-builder

name	social-calendar-builder
slug	aaron-social-calendar-builder
displayName	Social Calendar Builder · 社媒排期日历
summary	常青内容日历/栏目配比/批量生产/循环复用/发布节奏
description	Use when the user asks to "build our social posting calendar", "set weekly slots and queue depth per channel", or "plan the evergreen recycle rotation"; produces the always-on brand calendar — pillar allocation with hero/hub/help balance and give:ask targets (all labeled Estimated starting heuristics to calibrate against own analytics, never scored rules), per-channel recurring slots with queue depth, a batching workflow, an evergreen recycle cycle with freshness re-checks, deliberate open slots for realtime/trend moments fed by trend-spotter go/skip verdicts, and first-comment/publish-order ops — cadence commitments filed to the channel registry, and no batch ships to the queue without a SHIP verdict from social-quality-auditor pre-publish mode. Not for repurposing an existing asset or the paid-amplification calendar — use content-amplifier. 社媒排期/内容日历/栏目配比/常青循环复用
version	20.1.0
license	Apache-2.0
compatibility	Claude Code and compatible agent-skill hosts
homepage	https://github.com/aaron-he-zhu/aaron-marketing-skills
when_to_use	Use when standing up or rebalancing the always-on social posting calendar: pillar allocation, hero/hub/help mix, give:ask ratio targets, per-channel recurring slots and queue depth, batching days, evergreen recycle rotation with freshness re-checks, deliberate realtime/trend gaps, and first-comment/publish-order ops. Not the per-post copy (social-creative-builder) and not repurposing or paid amplification (content-amplifier); no batch ships to the queue without the SHIP verdict from social-quality-auditor pre-publish mode.
argument-hint	<channels + committed cadence> [content pillars] [planning horizon]
metadata	{"author":"aaron-he-zhu","version":"20.1.0","discipline":"social","phase":"craft","geo-relevance":"low","hermes":{"tags":["marketing","social","craft"],"category":"social"},"openclaw":{"emoji":"📣","homepage":"https://github.com/aaron-he-zhu/aaron-marketing-skills"}}

Social Calendar Builder

Builds the always-on brand posting calendar — the standing rhythm of the ECHO Craft phase: pillar allocation with hero/hub/help balance and give:ask targets, per-channel recurring slots with queue depth, a batching workflow, an evergreen recycle cycle, and deliberate gaps held open for realtime/trend moments. It feeds the ECHO C pillar-allocation adherence and evergreen recycled only with a freshness pass sub-items, the H cadence consistency vs the committed calendar sub-item (the over-posting guardrail's scored twin), and the E give:ask ledger cadence facts — see echo-benchmark.md. Realtime slots consume go/skip verdicts from trend-spotter. Every ratio in the calendar is an Estimated starting heuristic to calibrate against own analytics — platform folklore is never a scored rule. The calendar plans; a human ships.

Scope guard: this skill plans the calendar only. It does not write per-post copy or packages (social-creative-builder), write video beat sheets (short-video-scripter), repurpose an existing asset or plan the paid-amplification calendar (content-amplifier), compute the ECHO profile result or run ECHO vetoes (social-quality-auditor), or own the cadence record — commitments go to memory/events/channels.ndjson via an authorized operation: propose request to registry-events.py only, and channel-registry promotes them into calendar-commitments.md as sole writer of memory/channels/. Its publish step hard-requires a SHIP verdict from social-quality-auditor's pre-publish mode before any batch ships to the queue. No posting or scheduling automation anywhere; 中文 platforms (小红书 / 微信公众号 / 视频号 / 抖音) are manual-package / user-export access class — automation there is a hard red line (风控/封号).

Quick Start

Build the always-on calendar for Bluesky, LinkedIn, and 小红书 — pillars: [list]. Use the committed cadence in the registry; horizon 4 weeks.