CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

blog-calendar

Build a dated monthly or quarterly editorial calendar: which posts to publish or review when, content mix, templates, distribution timing, and a material-change review queue. Use when the user says "editorial calendar", "content calendar", "publishing schedule", "what should I write this month". Not for positioning or pillars (blog-strategy), SERP-validated cluster maps (blog-cluster), or detecting declining pages from Search Console exports (blog-decay). Publication frequency is not a ranking signal.

Quality

92%

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

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.

The body is a strong, highly actionable planning workflow: concrete output templates, quantified heuristics, and explicit validation-before-scheduling checkpoints throughout a clear six-step sequence. Its main weaknesses are mild redundancy across the freshness sections, the absence of error-recovery feedback loops, and reliance on references outside its own bundle.

Suggestions

Deduplicate the freshness rules: state "Update lastUpdated only after substantive content changes" and the WebSearch trend-validation requirement once (e.g., in Step 3 / Step 4) and reference them from Steps 5.7 and the Seasonal Trends list.

Add a final verification checkpoint in Step 5 or 6 that the planned new/refresh/repurposed counts reconcile with the chosen cadence row before saving the calendar.

Consider condensing the two inlined multi-week calendar format templates into one canonical weekly-row format plus a note on the quarterly variant, or moving the full templates into a bundled references file inside this skill.

DimensionReasoningScore

Conciseness

The body is dense and table-driven — content mix percentages, cadence math, decay signal tables, and output templates that earn their tokens — with only minor redundancy: "Update lastUpdated only after substantive content changes" appears in both Step 3 and Step 5.7, and WebSearch trend validation is repeated in Step 4 and the Seasonal Trends Integration list. It is efficient with trimmable instances, not lean enough for the every-token-earns-its-place anchor.

4 / 5

Actionability

Guidance is fully executable for an instruction-only skill: copy-paste-ready monthly and quarterly calendar templates with exact table columns, the 60/30/10 mix formula with a cadence math table, 12 named templates, concrete channel timing rules ("Reddit: 2-3 days after publish"), numeric cluster prioritization thresholds, and a specific save path (calendars/[yyyy-mm]-editorial-calendar.md).

5 / 5

Workflow Clarity

Steps 1 through 6 are clearly sequenced with numbered sub-steps and explicit pre-scheduling validation checkpoints ("Validate the current Google Search Status Dashboard before scheduling", "Investigate before rewriting", "Use WebSearch to validate timing of trends before scheduling"). It falls short of anchor 5 because there are no error-recovery feedback loops and no final check that planned post counts reconcile with the cadence table.

4 / 5

Progressive Disclosure

Bulk detail is appropriately deferred to clearly signaled, one-level-deep references ("Reference: ${CLAUDE_SKILL_DIR}/../blog/references/content-templates.md for full template details"), and the bundle contains no nested or buried references. It is not anchor 5 because the referenced files live in a sibling ../blog bundle rather than this skill's own (no references/, scripts/, or assets/ directories exist here), and two full multi-week output format templates are inlined, making the body long.

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.

The description is exemplary: concrete and comprehensive on capabilities, rich in natural trigger phrases including a colloquial user query, explicit on both what and when, and sharply disambiguated from sibling skills via an explicit not-for list. It is concise while packing all required trigger guidance in third-person voice.

DimensionReasoningScore

Specificity

The description enumerates concrete, comprehensive capabilities: "which posts to publish or review when, content mix, templates, distribution timing, and a material-change review queue" alongside the core action of building a dated monthly or quarterly calendar. Coverage of the skill's outputs is complete with no meaningful gaps, matching the comprehensive multi-action anchor rather than the 'minor gaps' anchor below it.

5 / 5

Completeness

It explicitly answers both questions: the "what" is "Build a dated monthly or quarterly editorial calendar" with its components, and the "when" is a concrete "Use when the user says..." clause listing trigger phrases. This mirrors the anchor-5 example and additionally adds explicit "Not for" boundaries, so it cannot be the anchor-4 'when could be more explicit' case.

5 / 5

Trigger Term Quality

It lists natural trigger phrases users would actually say — "editorial calendar", "content calendar", "publishing schedule" — plus the colloquial query "what should I write this month", giving synonym-level coverage. No commonly used phrasing for this need is missing, so it fits the comprehensive anchor rather than 'a few natural terms missing'.

5 / 5

Distinctiveness Conflict Risk

A clear niche (editorial calendaring) with distinct triggers, plus an explicit negative boundary naming three sibling skills — "Not for positioning or pillars (blog-strategy), SERP-validated cluster maps (blog-cluster), or detecting declining pages from Search Console exports (blog-decay)". Conflict risk is addressed explicitly rather than merely implied, fitting the minimal-conflict anchor.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

AgriciDaniel/claude-blog

Path

skills/blog-calendar/SKILL.md

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.