CtrlK
BlogDocsLog inGet started
Tessl Logo

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

67

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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.

The body is a well-structured, actionable instruction skill with a clear sequenced workflow and explicit validation feedback loops for its batch publish gate. Its main weakness is redundancy — the SHIP gate, registry write path, and scope guard are each restated several times, inflating the token budget without adding guidance.

Suggestions

State the SHIP publish-gate requirement once in the Skill Contract/Publish gate section and reference it from step 7 rather than restating it in the intro, scope guard, Data Sources, and Done-when clauses.

Consolidate the 'via an authorized operation: propose request to registry-events.py' write-path rule into one place (e.g. the Writes bullet) and link back to it instead of repeating the full phrase in steps 1, 8, and Save Results.

Collapse the intro paragraph and Scope guard bullet, which overlap heavily on out-of-scope skill disambiguation, into a single concise scope statement.

DimensionReasoningScore

Conciseness

The body mostly assumes Claude's competence (no explaining of basic concepts) but restates the SHIP publish gate, the registry write path, and the scope guard multiple times across sections, which is noticeable padding that could be tightened.

3 / 5

Actionability

Concrete guidance dominates — specific paths (memory/social/social-calendar-builder/, memory/events/channels.ndjson), a named operation ('operation: propose' to registry-events.py), and verdict-driven gates (SHIP/FIX/BLOCK) — with minor gaps where allocation methodology is left to referenced materials.

4 / 5

Workflow Clarity

Eight numbered steps form a clear sequence with an explicit validation checkpoint (the SHIP publish gate) and a feedback loop (FIX/BLOCK returns the batch for re-gating), plus a 'Done when' checklist — satisfying the batch-operation validation requirement.

5 / 5

Progressive Disclosure

Well-organized into overview sections with a dedicated Reference Materials list of one-level-deep, clearly signaled cross-skill links; minor gaps because some constraint detail is inlined repeatedly rather than factored out.

4 / 5

Total

16

/

20

Passed

Description

92%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 strong: it pairs an explicit 'Use when' trigger clause with a comprehensive, concrete list of outputs and clear boundary guidance against sibling skills. Its main weakness is mild verbosity from the parenthetical Estimated-labeling caveat, but this does not undermine specificity or completeness.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — pillar allocation, 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 what the skill produces.

5 / 5

Completeness

Explicitly answers both 'what' ('produces the always-on brand calendar — pillar allocation...') and 'when' via a concrete 'Use when the user asks to...' clause with multiple trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases a user would say ('build our social posting calendar', 'set weekly slots and queue depth per channel', 'plan the evergreen recycle rotation') plus bilingual keywords, but a few common synonyms like 'content calendar' or 'posting schedule' are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (always-on calendar planning) and explicitly disambiguates adjacent skills ('Not for repurposing an existing asset or the paid-amplification calendar — use content-amplifier'), keeping conflict risk minimal.

5 / 5

Total

19

/

20

Passed

Validation

75%

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

Validation12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
Reviewed

Table of Contents

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.