content-calendar

Plan a weekly editorial calendar by mapping company goals to publishable topics, owners, status, and verification notes.

Quality

51%

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

Fix and improve this skill with Tessl

tessl review fix ./packages/teams-catalog/catalog/optional/content/content-machine/skills/content-calendar/SKILL.md

Quality

Content

45%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 maximally concise but effectively empty: it states one vague directive and provides no calendar structure, field definitions, examples, or process for mapping company goals to publishable topics. Nearly all instructional value lives only in the description's phrasing, leaving the skill un-executable as written.

Suggestions

Add a concrete calendar template or example table showing the columns (week, topic, owner, status, verification note) with one filled-in row so output format is unambiguous.

Include a short numbered workflow for deriving topics from company goals (e.g., list goals → brainstorm 1-2 topics per goal → assign owner → set status values) with defined status values.

State where the calendar should be written (file name/format, e.g. Markdown table in content-calendar.md) and how to update an existing calendar when maintaining one.

Dimension	Reasoning	Score
Conciseness	The body is two sentences with zero padding, no explanation of concepts Claude already knows, and full assumption of Claude's competence, matching 'lean and efficient; every token earns its place'. It cannot be penalized for verbosity — the problem lies in other dimensions, not token efficiency.	5 / 5
Actionability	"Use this skill when creating or maintaining a lightweight content calendar from company priorities" only describes intent — there is no calendar format, no field definitions, no example entry, no template, and no commands, matching 'entirely vague or abstract; only describes rather than instructs'. Not 2 because even high-level hints about how to build or structure the calendar are absent.	1 / 5
Workflow Clarity	No steps or sequence exist anywhere in the body — the mapping of goals to topics/owners/status/verification notes (a multi-step process per the description) is never broken down, matching 'steps missing or incoherent; no sequence'. The simple-skill exception does not apply because the skill's own description defines a multi-step process that the body never sequences.	1 / 5
Progressive Disclosure	The skill is under 50 lines with no bundle files and no content that needs splitting, so per the rubric's guidance for small self-contained skills, a heading plus a single clear sentence scores 5 for structure and navigation. There are no buried or nested references to penalize.	5 / 5
	Total	12 / 20 Passed

Description

58%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 clearly and specifically states what the skill does, with concrete calendar elements, but entirely omits any 'when to use' trigger guidance and misses the most natural user phrasings like 'content calendar' or 'publishing schedule'. Adding an explicit trigger clause would most improve the score.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to plan a content calendar, editorial calendar, weekly publishing schedule, or wants to turn company goals into upcoming posts.'

Include natural synonyms users would actually say — 'content calendar', 'publishing schedule', 'weekly post plan' — not just 'editorial calendar'.

Consider mentioning typical inputs (company goals, priorities, OKRs) as trigger words to strengthen distinctiveness against generic planning skills.

Dimension	Reasoning	Score
Specificity	"Plan a weekly editorial calendar by mapping company goals to publishable topics, owners, status, and verification notes" names the domain and concrete output elements (topics, owners, status, verification notes), which matches the 'several specific actions; minor gaps' anchor. Not 5 because it is essentially one planning verb rather than multiple distinct concrete actions with comprehensive coverage.	4 / 5
Completeness	The description gives a clear 'what' (plan a weekly editorial calendar mapping goals to topics, owners, status, verification notes) but has no 'Use when...' clause or any 'when' guidance, which per the rubric caps completeness at 3 ('what' present, 'when' missing). Not 4 because the 'when' is not even weakly implied; not 2 because the 'what' is clear and specific.	3 / 5
Trigger Term Quality	Relevant natural terms like "editorial calendar", "company goals", and "publishable topics" are present, but common user phrasings such as "content calendar", "content schedule", or "publishing schedule" are missing, matching 'some relevant keywords but missing common variations or synonyms'. Not 4 because the most likely user phrasing for this skill is largely absent from the description itself.	3 / 5
Distinctiveness Conflict Risk	Editorial/content calendar planning from company priorities is a fairly distinct niche with specific vocabulary (owners, status, verification notes), so it is 'mostly distinct; minor overlap risk' with general planning or scheduling skills. Not 5 because the absence of trigger guidance leaves some ambiguity against generic planning/task-management skills.	4 / 5
	Total	14 / 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: paperclipai/paperclip
Path: packages/teams-catalog/catalog/optional/content/content-machine/skills/content-calendar/SKILL.md
Commit: 1c07b59

Reviewed: 1 day 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.