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

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, actionable instruction skill with clear sequencing and validation gates, and clean one-level-deep references. Its main weakness is redundancy: the publish-gate rule and the registry-events.py write-path are restated many times and could be consolidated.

Suggestions

State the SHIP/FIX/BLOCK publish-gate requirement once in a dedicated section and reference it from the other locations instead of restating the full rule 4-5 times.

Consolidate the "authorized operation: propose request to registry-events.py" write-path phrasing into a single Write-Policy block rather than repeating it verbatim in the contract, instructions, and Save Results sections.

Trim repeated scope-exclusion cross-links (content-amplifier, social-creative-builder) to a single Scope Guard + Reference Materials listing to recover tokens.

Dimension	Reasoning	Score
Conciseness	The body is information-dense and avoids explaining concepts Claude already knows, but the SHIP/publish-gate requirement and the "authorized operation: propose request to registry-events.py" phrasing are each repeated ~5 times across the scope guard, contract, instructions, and references, which could be tightened.	2 / 3
Actionability	For an instruction-only skill the guidance is concrete and actionable: exact memory paths (memory/social/social-calendar-builder/, memory/events/channels.ndjson), named gates (SHIP/FIX/BLOCK from social-quality-auditor pre-publish mode), required labels (Estimated with named source + calibration date), and a precise "Done when" checklist.	3 / 3
Workflow Clarity	Eight numbered steps form a clear sequence with explicit validation checkpoints — the publish-gate SHIP/FIX/BLOCK feedback loop, the freshness re-check rule, the over-posting guardrail, and an E1 risk flag — so the batch/destructive-adjacent operations are not left without verification.	3 / 3
Progressive Disclosure	Content is organized into clear sections (Quick Start, Skill Contract, Data Sources, Instructions, Save Results, Reference Materials, Next Best Skill) with one-level-deep, well-signaled references to echo-benchmark.md, skill-contract.md, and adjacent skill SKILL.md files; no bundle files exist to evaluate.	3 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is highly specific, trigger-rich, complete, and well-differentiated, with natural quoted triggers and explicit scope exclusions in third-person voice. Its only weakness is verbosity — the same SHIP-gate and Estimated-heuristic caveats could be trimmed without losing any scored signal.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "pillar allocation with hero/hub/help balance and give:ask targets", "per-channel recurring slots with queue depth", "evergreen recycle cycle with freshness re-checks", "first-comment/publish-order ops" — matching the top anchor.	3 / 3
Completeness	Explicitly answers both what ("produces the always-on brand calendar — ...") and when ("Use when the user asks to ..."), with an explicit "Not for ..." exclusion clause.	3 / 3
Trigger Term Quality	Quotes natural user phrases ("build our social posting calendar", "set weekly slots and queue depth per channel", "plan the evergreen recycle rotation") plus plain-language keywords (社媒排期/内容日历/栏目配比/常青循环复用), giving good coverage of terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (always-on posting calendar) and explicitly disambiguates from adjacent skills ("Not for repurposing an existing asset or the paid-amplification calendar — use content-amplifier"), making wrong-skill triggering unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

75%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 12 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 35 suspicious	Warning
referenced_paths_exist	Referenced path issues: 1 missing, 1 deeper-than-1-level	Warning

	Total	12 / 16 Passed

Repository: aaron-he-zhu/aaron-marketing-skills
Path: social/craft/social-calendar-builder/SKILL.md
Commit: 4a77c48

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.