blog-calendar

Generate editorial calendars for blogs with topic clusters, publishing schedules, content decay detection, freshness update plans, seasonal opportunities, content mix formula, template integration, and distribution scheduling. Plans monthly or quarterly calendars optimized for SEO topic authority and freshness signals based on content priority. Use when user says "editorial calendar", "content calendar", "blog calendar", "publishing schedule", "blog plan", "content plan", "what should I write".

Quality

91%

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

82%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 detailed, actionable planning workflow with strong concrete guidance and clear sequencing. The main gaps are minor verbosity from repeated freshness caveats and references to bundle files that are not shipped with the skill.

Suggestions

Consolidate the repeated 'directional signal, not a universal rule' freshness caveat into a single note so it is stated once rather than at both Step 2.5 and Step 3.

Add an explicit verification checkpoint before Step 6 (e.g., confirm decay report, cluster progress, and distribution schedule are all populated) so the workflow has a clear validation gate.

Either ship the referenced files (content-templates.md, distribution-playbook.md) in the bundle or remove/inline the references so progressive disclosure points to resources that actually exist.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with actionable tables and scaffolds that earn their place, but the freshness caveat ('directional signal, not a universal rule') is repeated at Step 2.5 and Step 3, and some channel-timing prose could be tightened.	4 / 5
Actionability	Highly concrete for an instruction skill: specific decay-day thresholds, a 60/30/10 content-mix formula, cadence tables with exact post counts, enumerated template names, and copy-ready calendar scaffolds covering the common monthly and quarterly cases.	5 / 5
Workflow Clarity	Steps 1–6 (with sub-steps) are clearly sequenced and include prioritization rules and checklists, but there are no explicit validation/verification checkpoints confirming the output is complete before saving.	4 / 5
Progressive Disclosure	Well-organized into clearly headed sections with one-level-deep references signaled ('skills/blog/references/content-templates.md', '.../distribution-playbook.md'), but those referenced files are not present in the bundle, leaving the references unverifiable.	4 / 5
	Total	17 / 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.

A strong description: third-person voice, comprehensive concrete capabilities, and an explicit trigger clause with natural synonyms. It cleanly answers both what the skill does and when to invoke it.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'topic clusters, publishing schedules, content decay detection, freshness update plans, seasonal opportunities, content mix formula, template integration, and distribution scheduling' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	It explicitly answers both 'what' (generate editorial calendars with the listed capabilities) and 'when' (the concrete 'Use when user says ...' trigger phrases), matching the top anchor.	5 / 5
Trigger Term Quality	The 'Use when user says' clause enumerates natural synonyms users would actually say — 'editorial calendar', 'content calendar', 'blog calendar', 'publishing schedule', 'blog plan', 'content plan', 'what should I write' — covering variations comprehensively.	5 / 5
Distinctiveness Conflict Risk	Editorial/blog calendar planning is a clear niche with distinct trigger phrases; minimal overlap risk with adjacent blog skills since the calendar triggers are specific.	5 / 5
	Total	20 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: AgriciDaniel/claude-blog
Path: brain/.raw/sources/claude-blog-skill/skills/blog-calendar/SKILL.md
Commit: 84f7abf

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