slot-engine

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

Quality

78%

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

86%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 exemplary lean reference document: it captures the non-obvious contract (ordered invariants, DST handling, buffer expansion, defaults) and provides two concrete ordered debugging checklists without a wasted token. Its only real gap is the lack of a worked example showing a call and its output, which keeps actionability and workflow clarity at 4.

Dimension	Reasoning	Score
Conciseness	The body is a lean reference: every line carries non-obvious information (input list, ordered invariants, concrete debugging checks) with zero padding and no explanation of concepts Claude already knows — the 5 anchor 'every token earns its place'.	5 / 5
Actionability	The guidance is concrete and specific — "empty intervals = fully blocked", "including the before/after buffer expansion", "default = duration", "check weekly availability ... in the schedule's timezone (not UTC)" — with a real import line. It is not a 5 because there is no example invocation or sample input/output showing the function in use, a minor gap for a code-reference skill.	4 / 5
Workflow Clarity	The two debugging checklists are clearly sequenced triage workflows with concrete checkpoints per step ("a single existing booking can close a day", "busy intervals from providers are in UTC"), and the invariants are explicitly ordered 'in order'. It falls short of 5 because there are no explicit feedback/recovery loops (e.g., what to do once a failing check is identified) — reasonable for a diagnostic reference, but the 5 anchor requires explicit validation steps and error-recovery loops.	4 / 5
Progressive Disclosure	This is a short (under 50 lines of body), single-purpose reference with no bundle files (references/, scripts/, assets/ do not exist) and no need for them; the guideline for such skills allows a 5 with well-organized sections, and the Inputs / Output / Invariants / Debugging structure is clean and navigable.	5 / 5
	Total	18 / 20 Passed

Description

58%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.

A compact, specific description that accurately scopes the skill to a single function and its reference material, written in third person without fluff. Its main weakness is the complete absence of 'when to use' trigger guidance, which caps completeness and limits natural trigger-term coverage.

Suggestions

Add an explicit trigger clause, e.g. "Use when investigating why an available slot is missing or unexpectedly shown, or when modifying computeAvailableSlots' scheduling/availability logic."

Include natural user vocabulary — availability, booking, busy intervals, timezone/DST — so the description matches how users actually phrase scheduling problems.

Mention the invariant guarantees (e.g., no past slots, no busy overlaps, DST-safe) briefly to sharpen the 'what' for a 5-level completeness anchor.

Dimension	Reasoning	Score
Specificity	The description names the exact artifact (`computeAvailableSlots`) and enumerates several specific content areas — "inputs, outputs, invariants, and debugging guide" — which is several specific items with only minor gaps (e.g., slot/DST semantics not mentioned). It is not a 5 because it describes the document's contents rather than comprehensively stating the concrete actions covered, and not a 3 because it goes beyond naming a domain with only 1-2 actions.	4 / 5
Completeness	It has a clear 'what' (a reference for the pure computeAvailableSlots function covering inputs, outputs, invariants, and debugging) but no 'when' — there is no "Use when..." clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Relevant keywords are present ("computeAvailableSlots", "slots", "debugging"), matching the 'some relevant keywords but missing common variations' anchor. It misses the natural phrases a user would say — "availability", "booking", "scheduling", "calendar", "why is this slot missing" — so it falls short of the 4 anchor's good keyword coverage.	3 / 5
Distinctiveness Conflict Risk	Naming a specific, unique function (`computeAvailableSlots` from `@agent-native/scheduling/core`) gives it a clear niche with low conflict risk against unrelated skills, but with no trigger phrases it could still be picked over sibling scheduling/booking skills in the same area — mostly distinct with minor overlap risk, the 4 anchor.	4 / 5
	Total	14 / 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: BuilderIO/agent-native
Path: packages/scheduling/docs/skills/slot-engine/SKILL.md
Commit: a941a2e

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