slot-engine

The pure `computeAvailableSlots` function — inputs, outputs, invariants, and debugging guide.

Quality

71%

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/scheduling/docs/skills/slot-engine/SKILL.md

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a tight, well-structured reference and diagnostic guide with clear ordered invariants and actionable debugging checklists; its main gap is the absence of executable code or commands, which limits actionability.

Suggestions

Add a short executable snippet showing how to call `computeAvailableSlots` with a minimal valid input set, so the reference is copy-paste ready rather than purely descriptive.

Optionally include a one-line expected-output example so users can sanity-check a call without reading the full invariants list.

Dimension	Reasoning	Score
Conciseness	The body is lean — tight bullet lists and numbered steps with no padding and no explanation of concepts Claude already knows (e.g. what a timezone or DST is); every line earns its place, matching the 'lean and efficient' anchor.	3 / 3
Actionability	The debugging guidance is concrete and specific (named fields, exact checks, expected values like 'empty intervals = fully blocked'), but it offers diagnostic hints rather than executable code or copy-paste commands, falling short of the 'fully executable; copy-paste ready' anchor.	2 / 3
Workflow Clarity	The Invariants are an explicitly ordered ('in order') sequence of guarantees, and the Debugging section provides two clear, scenario-based error-recovery checklists (missing → 5 checks; present → 3 checks), matching the 'checklists for complex processes' / 'feedback loops for error recovery' anchor; the destructive-operation validation cap does not apply to this read-only reference.	3 / 3
Progressive Disclosure	The body is a self-contained, well-organized file under 50 lines with clear sections (Inputs, Output, Invariants, Debugging) and no need for external references, which the rubric allows to score 3 on progressive disclosure.	3 / 3
	Total	11 / 12 Passed

Description

57%

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 specific and distinctive thanks to the named function, but it reads as a table-of-contents for a reference rather than a capability statement, and it entirely lacks explicit 'when to use' trigger guidance.

Suggestions

Add an explicit trigger clause, e.g. 'Use when debugging missing/unexpected scheduling slots or reasoning about the contract of computeAvailableSlots.'

Reframe the description around concrete actions the skill enables (e.g. 'Diagnoses why computed slots are missing or present; documents the inputs, outputs, and invariants of computeAvailableSlots') rather than listing document sections.

Include natural user terms like 'scheduling', 'availability', and 'booking' alongside 'slots' to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain (the `computeAvailableSlots` function) and enumerates content areas ('inputs, outputs, invariants, and debugging guide'), but these are facets of a reference doc rather than multiple concrete actions the skill performs, so it sits above 'vague' yet below the 'lists multiple specific concrete actions' anchor.	2 / 3
Completeness	The 'what' is present (a reference for the function covering inputs/outputs/invariants/debugging), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 2 per the rubric guidelines.	2 / 3
Trigger Term Quality	It includes some natural terms a user might say ('slots', 'debugging') but leans on the code identifier `computeAvailableSlots` and jargon like 'invariants', missing common variations such as 'scheduling', 'availability', or 'booking'.	2 / 3
Distinctiveness Conflict Risk	Naming a specific internal function (`computeAvailableSlots`) gives the skill a clear, narrow niche that is unlikely to conflict with unrelated skills, satisfying the 'clear niche with distinct triggers; unlikely to conflict' anchor.	3 / 3
	Total	9 / 12 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: BuilderIO/agent-native
Path: packages/scheduling/docs/skills/slot-engine/SKILL.md
Commit: e9a2f0e

Reviewed: 4 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.