Agent skill · Data & Analytics

social-calendar-builder

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 o

aaron-he-zhu2,508★ · 1 repos on radarProfile →
claude-codeApache-2.0
Install
npx skills add aaron-he-zhu/aaron-marketing-skills --skill social-calendar-builder --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 14 KB
Bundled scripts: none
Version: 19.1.0
Requires: Claude Code and compatible agent-skill hosts
Path: social/craft/social-calendar-builder/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,508
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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-scri

What's inside
Steps it walks through
  1. Quick Start
  2. Skill Contract
  3. Handoff Summary
  4. Data Sources
  5. Instructions
  6. Save Results
  7. Reference Materials
  8. Next Best Skill
More from aaron-marketing-skills
All skills →
About this skill
What does the social-calendar-builder skill do?

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 o

How do I install it?

Run `npx skills add aaron-he-zhu/aaron-marketing-skills --skill social-calendar-builder --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From aaron-he-zhu/aaron-marketing-skills, a repository with 2,508 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going