calendar

Second calendar skill.

Quality

26%

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 ./legacy_pi_mono_code/pi-mono/packages/coding-agent/test/fixtures/skills-collision/second/calendar/SKILL.md

The canonical home for this skill is calendar in can1357/oh-my-pi

Quality

Content

33%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 stub: one heading and one declarative sentence with no actionable guidance, workflow, or referenced materials. It is token-efficient only because it contains almost nothing of use.

Suggestions

Add concrete, executable guidance or a minimal code example for the skill's core calendar task.

Include a brief sequenced workflow with any validation needed for calendar operations.

State the skill's distinct purpose so the body is not merely a restatement of the description.

Dimension	Reasoning	Score
Conciseness	The body ("# Calendar (Second)\n\nThis is the second calendar skill.") is extremely lean with no padding or over-explanation of concepts Claude already knows, fitting the 'efficient; minor instances that could be trimmed' anchor rather than a 5 because the tokens convey essentially no useful information.	4 / 5
Actionability	"This is the second calendar skill." provides no code, commands, or concrete steps, only a descriptive statement, matching the 'entirely vague or abstract; no concrete guidance' anchor.	1 / 5
Workflow Clarity	There are no sequenced steps or validation checkpoints whatsoever, only a single declarative sentence, matching the 'steps missing or incoherent' anchor.	1 / 5
Progressive Disclosure	This is a simple under-50-line skill with no bundle files, and it has a single organizing heading; per the simple-skills note it can score well for organization, landing at 4 rather than 5 because the structure is minimal rather than clearly well-organized.	4 / 5
	Total	10 / 20 Passed

Description

20%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 a near-empty label that names the calendar domain but provides no actions, triggers, or usage guidance, making it indistinguishable from a sibling skill. It fails on specificity, completeness, and distinctiveness while offering only a single generic trigger term.

Suggestions

Replace the placeholder with concrete calendar actions (e.g., create events, query free/busy, set reminders).

Add an explicit 'Use when...' clause listing natural trigger phrases users would say.

Differentiate this skill from the first calendar skill by stating its distinct purpose or scope.

Dimension	Reasoning	Score
Specificity	"Second calendar skill." names a domain but states zero concrete actions (no verbs describing capabilities), fitting the entirely-vague anchor rather than the 'names domain with minimal actions' anchor which requires at least a generic action verb.	1 / 5
Completeness	It gives a vague 'what' (a calendar skill) and no 'when' / trigger guidance at all, matching the 'vague what and no when' anchor; the missing 'Use when...' clause also caps completeness at 3.	2 / 5
Trigger Term Quality	The only natural keyword is "calendar"; it is a relevant term but the description lacks common variations or phrases a user would say, matching the 'one or two generic keywords' anchor.	2 / 5
Distinctiveness Conflict Risk	"Second calendar skill." is very broad and, by labeling itself as a second instance, signals direct overlap with another calendar skill, matching the 'very broad; high overlap risk' anchor.	2 / 5
	Total	7 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: Dicklesworthstone/pi_agent_rust
Path: legacy_pi_mono_code/pi-mono/packages/coding-agent/test/fixtures/skills-collision/second/calendar/SKILL.md
Commit: 38d4f88

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