Menu

Individual skill

social-calendar-builder

0upvotes

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. 社媒排期/内容日历/栏目配比/常青循环复用

social/craft/social-calendar-builder/SKILL.md

Read pinned source

Source commit 8be02f1f0b18253bd5f2b85f858278f042637b9a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
3,134
Repository last updated
Nov 12, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Declared tags are partial or unavailable.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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](../../../references/echo-benchmark.md). Realtime slots consume go/skip verdicts from [trend-spotter](../../../influencer/scout/trend-spotter/SKILL.md). 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](../social-creative-builder/SKILL.md)), write video beat sheets ([short-video-scripter](../short-video-scripter/SKILL.md)), repurpose an existing asset or plan the paid-amplification calendar ([content-amplifier](../../../influencer/activate/content-amplifier/SKILL.md)), compute the ECHO profile result or run ECHO vetoes ([social-quality-auditor](../../host/social-quality-auditor/SKILL.md)), 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](../../../protocol/channel-registry/SKILL.md) 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.
```

```
We are over-posting on LinkedIn and the inbox is slipping. Rebalance slots and queue depth against the committed cadence and hosting capacity.
Back to top