CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

calendar

First calendar skill.

32

Quality

41%

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/mirror/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 an empty stub: beyond a title and a redundant one-line label it contains no actionable guidance, no workflow, and no content to disclose. Its only virtues are brevity and the absence of any structural or progressive-disclosure problems.

Suggestions

Replace the label sentence with concrete instructions for at least the primary task (e.g. how to create or query an event, with executable command/code examples).

If the skill involves multi-step or destructive operations (editing or deleting events, batch updates), list the steps in order with an explicit validation checkpoint before committing changes.

Use the body to state what the skill does and when to use it, rather than repeating the frontmatter description.

DimensionReasoningScore

Conciseness

The body is two lines with zero padding or concept explanation, but the sole sentence 'This is the first calendar skill.' is redundant with the frontmatter description and could be trimmed entirely — a minor instance of tokens not earning their place (anchor 4), not the fully lean anchor-5 body where every token adds value.

4 / 5

Actionability

The body provides no code, commands, examples, or instructions of any kind — 'This is the first calendar skill.' only labels rather than instructs, squarely matching anchor 1 ('entirely vague or abstract; no concrete code or commands; only describes rather than instructs').

1 / 5

Workflow Clarity

No steps or sequence exist at all, matching anchor 1 ('steps missing or incoherent; no sequence'). The simple-skill exception cannot apply because the skill's task is undefined — there is no unambiguous single action whose clarity could be credited.

1 / 5

Progressive Disclosure

The skill is under 50 lines, no bundle files (references/, scripts/, assets/) exist, nothing is inlined that belongs in a separate file, and nothing is buried. Per the judging guideline ('For skills under 50 lines with no need for external references, progressive disclosure can score 5 with just well-organized sections'), the trivial heading-plus-sentence structure qualifies.

5 / 5

Total

11

/

20

Passed

Description

15%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 placeholder label: it names the calendar domain but states no capabilities, no trigger conditions, and no distinguishing details. It sits at or near the floor on specificity, trigger terms, and completeness, with only the calendar niche itself preventing a total collapse on distinctiveness.

Suggestions

State concrete capabilities in third person, e.g. 'Creates, edits, and queries calendar events and schedules.'

Add an explicit trigger clause: 'Use when the user mentions calendars, scheduling, events, appointments, or .ics files.'

Remove 'First' and instead differentiate from sibling calendar skills by scope (e.g. personal vs. shared/team calendars) to reduce conflict risk.

DimensionReasoningScore

Specificity

The entire description is 'First calendar skill.' — it names a domain but contains no action verb or capability whatsoever ('no concrete actions'), making it even less informative than the anchor-1 example 'Helps with documents'. It does not rise to anchor 2 ('Processes PDF files') because that anchor still states an action.

1 / 5

Completeness

There is no 'what' (the description is a label, not a capability statement) and no 'when' (no 'Use when...' clause or any trigger guidance). Both are missing or extremely vague, matching anchor 1; the judging guideline that a missing 'Use when...' clause caps completeness at 3 is comfortably satisfied by this floor score.

1 / 5

Trigger Term Quality

'calendar' is one natural, relevant domain keyword, but every natural phrase a user would say — 'schedule a meeting', 'create an event', 'appointments', '.ics' — is absent. This matches anchor 2 ('one or two generic keywords; missing the natural phrases users say') better than anchor 3, which expects multiple relevant keywords as in 'Works with PDF files'.

2 / 5

Distinctiveness Conflict Risk

'calendar' is a distinct niche that would not trigger for unrelated skills, but the description provides nothing to distinguish it from other calendar skills — and 'First' explicitly implies sibling calendar skills exist. This matches anchor 3 ('somewhat specific but could still overlap with similar skills') rather than anchor 4, which requires a mostly distinct description with distinguishing triggers.

3 / 5

Total

7

/

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

can1357/oh-my-pi

Path

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