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

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

73%Weight 40%Scale 1-5

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

A well-structured, highly actionable process skill with an explicit, validated multi-step workflow and appropriate one-level-deep references to real bundle and peer-skill files. Its main weakness is conciseness: the same scope/gate/registry guardrails are restated verbatim across several sections, inflating tokens without adding clarity.

Suggestions

State each guardrail (SHIP-gate, registry-events propose-only path, no automation, Estimated labeling) once in its authoritative section and reference it rather than repeating full clauses in the intro, scope guard, Skill Contract, and each step.

Consolidate the overlapping scope/guardrail content of the opening paragraph and the 'Scope guard' bullet into a single concise scope block.

Move the long enumerated Data Sources connector list into a short reference pointer to CONNECTORS.md, keeping only the keyless-tier rationale inline.

Dimension	Reasoning	Score
Conciseness	The body is dense and mostly efficient but repeatedly restates the same guardrails (SHIP-gate, registry propose path, no automation, Estimated labeling) across the intro, scope guard, Skill Contract, and Instructions, adding padding a competent model does not need.	3 / 5
Actionability	Concrete and specific — names exact memory paths, registry-events.py operation:propose flow, package_ref/version/hash binding, and receipt fields — but it is an instruction/process skill with no copy-paste code or commands, leaving minor executable gaps.	4 / 5
Workflow Clarity	The 8-step Instructions are clearly sequenced with explicit validation checkpoints (confirm cadence/offset, E1 risk flag, SHIP-gate bound to exact hash, freshness re-check, human receipt required before 'published'), feedback loops (FIX/BLOCK returns to batch, crisis-pause freeze), and a 'Done when' checklist.	5 / 5
Progressive Disclosure	Well-organized sections with one-level-deep references to real bundle/peer files (human-action-control.md exists in references/, plus echo-benchmark.md, skill-contract.md, and peer SKILLs) and clear navigation; only the inline repetition of guardrails keeps it from a 5.	4 / 5
	Total	16 / 20 Passed

Description

100%Weight 40%Scale 1-5

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 a strong, specific, and complete trigger statement that clearly delineates scope and boundaries while providing natural user-facing trigger phrases in both English and Chinese. Its only weakness is significant verbosity — it crams scope guardrails, the SHIP-gate requirement, and tag strings into a single field, which slightly undercuts the 'do not reward verbosity' guideline.

Suggestions

Trim the embedded scope-guard and SHIP-gate clauses from the description field (move detail to when_to_use/body); keep it to the core capability and trigger phrases to reduce token cost.

Remove the trailing Chinese tag string '社媒排期/内容日历/栏目配比/常青循环复用' from the description; duplicate tags belong in metadata, not the trigger field.

Drop the parenthetical '(all labeled Estimated starting heuristics...)' aside — this nuance belongs in the body, not the discovery description.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — pillar allocation with hero/hub/help balance, give:ask targets, per-channel recurring slots with queue depth, batching workflow, evergreen recycle cycle with freshness re-checks, realtime/trend gaps, and first-comment/publish-order ops — giving comprehensive coverage of the calendar-building capability.	5 / 5
Completeness	Clearly answers both 'what' (produces the always-on brand calendar with the enumerated components) and 'when' (explicit 'Use when...' clause with concrete trigger phrases) and adds a 'Not for...' out-of-scope boundary.	5 / 5
Trigger Term Quality	Embeds natural user phrases ('build our social posting calendar', 'set weekly slots and queue depth per channel', 'plan the evergreen recycle rotation') plus synonyms and Chinese-language trigger terms, covering how a user would actually request this skill.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (standing calendar/cadence) and explicitly redirects adjacent tasks (content-amplifier, social-creative-builder, social-quality-auditor), minimizing the risk of triggering for the wrong skill.	5 / 5
	Total	20 / 20 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: 32 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: 64562bc

Reviewed: 3 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.