calendar

First calendar skill.

Quality

25%

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/coding-agent/test/fixtures/skills-collision/first/calendar/SKILL.md

Quality

Content

26%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 near-empty placeholder: organized but conveying no actionable guidance or workflow. Progressive disclosure is acceptable only because there is essentially nothing to disclose.

Suggestions

Add concrete, executable guidance for the skill's core task (e.g. specific commands, code, or step-by-step instructions for creating/viewing calendar events).

If multi-step or destructive operations are involved, include explicit validation checkpoints so workflow clarity can rise above the cap.

Replace the placeholder sentence with real overview content that points to any detailed references if the skill grows beyond a simple single task.

Dimension	Reasoning	Score
Conciseness	The body ('This is the first calendar skill.') is lean with no padding or over-explanation, but the tokens convey no actionable information, so it is efficient yet not earning every token's place.	3 / 5
Actionability	The body only describes that this is a calendar skill with no code, commands, or concrete steps, matching 'entirely vague or abstract; no concrete code or commands; only describes rather than instructs'.	1 / 5
Workflow Clarity	There is no action or sequence of steps stated at all; the single-purpose exception cannot apply because no unambiguous action is described.	1 / 5
Progressive Disclosure	The skill is under 50 lines with no external references needed and the body is cleanly organized into a heading plus a line; structure is appropriate for its tiny scope, with only minor gaps from the vacuous content.	4 / 5
	Total	9 / 20 Passed

Description

25%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 that names the calendar domain but conveys no capabilities, no natural trigger terms, and no usage guidance. It scores uniformly low across all dimensions.

Suggestions

Replace 'First calendar skill' with concrete actions, e.g. 'Create, view, and edit calendar events and reminders'.

Add an explicit trigger clause such as 'Use when the user asks to schedule, view, or modify calendar events or reminders'.

Include natural synonyms and specifics (e.g. 'events', 'appointments', 'scheduling', 'reminders') to improve trigger quality and distinctiveness.

Dimension	Reasoning	Score
Specificity	The phrase 'First calendar skill' names the calendar domain but states no concrete actions at all, matching the anchor where the domain is named yet actions are minimal or generic.	2 / 5
Completeness	It offers only a vague 'what' (a calendar skill) and entirely lacks a 'when'/'Use when' clause, matching 'has a vague what and no when'; the missing trigger guidance also caps completeness at 3, and this is below that.	2 / 5
Trigger Term Quality	Only the single generic keyword 'calendar' appears; there are no natural trigger phrases a user would actually say, fitting 'one or two generic keywords; missing the natural phrases users say'.	2 / 5
Distinctiveness Conflict Risk	'First calendar skill' is very broad and provides no distinguishing triggers beyond naming the domain, giving high overlap risk with any calendar-related skill.	2 / 5
	Total	8 / 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: can1357/oh-my-pi
Path: packages/coding-agent/test/fixtures/skills-collision/first/calendar/SKILL.md
Commit: df624f5

Reviewed: 8 days 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.