content-calendar

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

Quality

58%

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

58%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 admirably lean and well-structured but stops at stating the trigger, offering no actionable method, template, or workflow for actually building the calendar. Adding a concrete format and a short mapping workflow would address the weakest dimensions.

Suggestions

Provide a concrete output template (e.g., a weekly table with columns for topic, owner, status, and verification notes) so Claude knows exactly what to produce.

Add a short sequenced workflow for mapping company goals to calendar entries, including how to derive topics and assign owners.

Include a verification/check step (e.g., confirm each entry has an owner and a verification note before finalizing) to add a validation checkpoint.

Dimension	Reasoning	Score
Conciseness	The body is just a heading and a single trigger sentence with zero padding or restated common knowledge; every token earns its place and it fully assumes Claude's competence.	5 / 5
Actionability	The body only states when to invoke the skill ("Use this skill when creating or maintaining a lightweight content calendar") with no concrete steps, template, or format for producing the calendar; not a 1 because it does name the task, but not a 3 because there is no executable guidance at all.	2 / 5
Workflow Clarity	No sequence is given for an inherently multi-step task (mapping goals to topics, owners, status, notes), and no validation checkpoint exists; not a 1 because the intent is coherent, but the simple-skill exception does not fully apply since planning a calendar is not a single unambiguous action.	2 / 5
Progressive Disclosure	This is a simple skill well under 50 lines with no need for external references, and the body is cleanly organized into a heading plus trigger sentence, satisfying the simple-skill exception for progressive disclosure.	5 / 5
	Total	14 / 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 gives a clear, fairly specific statement of what the skill does but omits any "when to use it" trigger guidance, capping completeness. Adding a Use-when clause with natural trigger phrases would lift the weakest dimensions.

Suggestions

Append a 'Use when...' clause with natural triggers (e.g., 'Use when planning a content calendar, scheduling editorial posts, or assigning content owners from company priorities').

Add common user-facing synonyms like 'content schedule', 'editorial schedule', or 'publishing calendar' to broaden trigger term coverage.

Clarify the output format (e.g., a weekly table of topic/owner/status/notes) to push specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Maps company goals to several concrete outputs ("publishable topics, owners, status, and verification notes"), listing multiple specific actions with only minor coverage gaps; not a 5 because it is essentially one planning action rather than a comprehensive set of distinct capabilities.	4 / 5
Completeness	It clearly states the "what" (plan a weekly editorial calendar by mapping goals to topics/owners/status/notes) but contains no "when"/trigger guidance, so per the missing-Use-when cap it cannot exceed 3; not a 2 because the "what" is clear and concrete.	3 / 5
Trigger Term Quality	Relevant terms like "editorial calendar", "company goals", and "publishable topics" appear but common user variations/synonyms are missing and there is no "Use when..." trigger phrase; not a 4 because keyword coverage is thin rather than merely missing a few.	3 / 5
Distinctiveness Conflict Risk	"Content calendar" / "editorial calendar" is a fairly distinct niche with limited overlap risk; not a 5 because without explicit trigger phrases it could still overlap with general planning or project-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: 890ab9a

Reviewed: about 16 hours 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.