CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

calendar

Third 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/nested/second/calendar/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

30%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 placeholder: a title plus one vacuous sentence that adds nothing beyond the frontmatter. While it commits no conciseness or structure sins, it provides zero actionable guidance and no workflow, making the skill unusable as written.

Suggestions

State the skill's purpose and at least one concrete action (what to do and how) in the body — e.g., specific commands, code, or step-by-step guidance for the calendar task.

If the skill has any multi-step or risky operations, add an explicit numbered workflow with validation checkpoints before proceeding.

Replace 'This is the third calendar skill.' with content that distinguishes this skill's actual capabilities, or reference supporting files if deeper detail exists elsewhere.

DimensionReasoningScore

Conciseness

The body is only a heading and one sentence ('This is the third calendar skill.'), so there is no padding or explanation of concepts Claude already knows. The single sentence merely restates the H1 ('# Calendar (Third)'), a minor redundancy that could be trimmed, matching anchor 4 rather than 5's 'every token earns its place'.

4 / 5

Actionability

'This is the third calendar skill.' only describes; there is no concrete code, command, or executable guidance of any kind. This exactly matches anchor 1 ('only describes rather than instructs') and is not level 2, which requires at least high-level hints toward specific steps.

1 / 5

Workflow Clarity

No steps or sequence are present anywhere in the body — it never states what the skill does or how to do it. The simple-skill exception does not apply because there is no unambiguous single action defined, so this stays at anchor 1 ('steps missing or incoherent') rather than 2, which requires a rough sequence.

1 / 5

Progressive Disclosure

The body has a single heading and no wall of text, no buried or nested references, and no inline content that belongs in separate files. However, it cannot be called a clear, well-organized overview — it signals nothing and points nowhere — so it sits at anchor 3 rather than 4-5, which require demonstrated good structure.

3 / 5

Total

9

/

20

Passed

Description

18%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, not a description: it names the calendar domain but conveys no capabilities, no usage triggers, and nothing that distinguishes it from other calendar skills. It would rarely fire for the right task and could not be told apart from its siblings.

Suggestions

Replace 'Third calendar skill.' with concrete third-person actions, e.g. 'Creates and edits calendar events, checks availability, and converts .ics files.'

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

State the differentiating capability that makes this the 'third' calendar skill so it does not collide with the other calendar skills' triggers.

DimensionReasoningScore

Specificity

'Third calendar skill.' contains no action verbs or concrete capabilities whatsoever — it is a bare label. It matches anchor 1 ('no concrete actions') and falls below anchor 2, whose example ('Processes PDF files') still names an action; 'third' is ordinal filler, not a capability.

1 / 5

Completeness

Neither 'what' nor 'when' is answered: the description never states any capability and has no 'Use when...' clause or equivalent. This matches anchor 1 ('missing both what and when'), and the missing-trigger guidance caps it at 3 regardless — it cannot reach 2 because that requires at least a vague 'what' or a 'when'.

1 / 5

Trigger Term Quality

'calendar' is a relevant, natural keyword a user would actually say, but it is the sole keyword with no variations or synonyms (events, scheduling, dates, .ics). This fits anchor 3 ('some relevant keywords but missing common variations') rather than 2, whose example is a generic term like 'files' rather than a domain-specific one.

3 / 5

Distinctiveness Conflict Risk

By self-describing as the 'third' calendar skill, it guarantees high overlap with sibling calendar skills while providing nothing to distinguish itself. This matches anchor 2 ('very broad; high overlap risk with many similar skills'); it is above anchor 1 only because 'calendar' does narrow the domain.

2 / 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/nested/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.