CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

calendar

Second calendar skill.

31

Quality

39%

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

Fix and improve this skill with Tessl

tessl review fix ./packages/coding-agent/test/fixtures/skills-collision/second/calendar/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

37%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 vacuous stub: a title plus one sentence that restates it. It contains no actionable guidance and no workflow, though it also commits no structural or token-efficiency sins. Progressive disclosure is trivially satisfied only because there is no content to disclose.

Suggestions

State the skill's actual purpose and the concrete actions to perform (e.g. specific commands, code, or decision rules) instead of the sentence "This is the second calendar skill."

If the skill involves a multi-step or destructive/batch operation, sequence the steps explicitly and include a validation checkpoint before proceeding.

Remove the redundant body sentence that repeats the H1 title, or replace it with the first real instruction.

DimensionReasoningScore

Conciseness

The two-line body has no padding or over-explanation, but "This is the second calendar skill." merely restates the header "# Calendar (Second)" — a minor redundancy that could be trimmed, matching anchor 4.

4 / 5

Actionability

"This is the second calendar skill." only describes (barely) and provides no code, commands, or concrete steps — matching anchor 1 ("only describes rather than instructs").

1 / 5

Workflow Clarity

No steps or sequence of any kind appear; the simple-skill exception requires an unambiguous single action, and none is stated, so anchor 1 ("steps missing") applies.

1 / 5

Progressive Disclosure

The skill is under 50 lines, has no bundle files, no nested or buried references, and nothing that belongs in a separate file — per the rubric's simple-skill guideline this trivially satisfies the dimension.

5 / 5

Total

11

/

20

Passed

Description

11%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 bare label: it identifies a domain (calendar) and its ordinal position but states no capability, no use condition, and nothing that distinguishes it from a sibling calendar skill. It sits at or near the bottom anchor on every dimension.

Suggestions

Replace the label with concrete third-person capabilities, e.g. "Creates calendar events, checks availability, and resolves scheduling conflicts across time zones."

Add an explicit trigger clause such as "Use when the user mentions calendar events, meetings, scheduling, availability, or .ics files."

State what differentiates this skill from the other calendar skill (e.g. different provider, format, or task) so the two do not conflict at trigger time.

DimensionReasoningScore

Specificity

"Second calendar skill." names a domain but contains no action verbs whatsoever — less concrete than anchor 2's "Processes PDF files", which at least states a minimal action.

1 / 5

Completeness

Neither "what" (no capability is stated, only a label) nor "when" (no 'Use when...' clause or equivalent) is present, matching anchor 1 where both are extremely vague or missing.

1 / 5

Trigger Term Quality

The lone keyword "calendar" is a term a user might naturally say, but there are no verb phrases, variations, or synonyms — matching anchor 2 ("one or two generic keywords; missing the natural phrases users say").

2 / 5

Distinctiveness Conflict Risk

The word "Second" explicitly signals it duplicates another calendar skill and offers no distinguishing trigger, creating high overlap risk with its sibling — anchor 2. Not 3 because no differentiator at all is provided.

2 / 5

Total

6

/

20

Passed

Validation

100%

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

Kiz8-Team/pi-cwl

Path

packages/coding-agent/test/fixtures/skills-collision/second/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.