slot-engine

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

Quality

56%

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

67%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 concise, well-structured, and provides a clear debugging workflow, making effective use of a small token budget without explaining concepts Claude already knows. Its main weakness is actionability: it is instruction/reference-oriented with only an import line and no executable code or commands, which keeps it at mid-level on that dimension.

Suggestions

Add at least one small executable example showing how to call computeAvailableSlots and inspect the returned Slot array, so the skill is copy-paste ready rather than reference-only.

Tighten the Inputs section into a typed schema or explicit parameter table so the actionability of the contract is unambiguous.

Optionally split the full invariant/buffer semantics into a referenced file (e.g., INVARIANTS.md) and keep the SKILL.md as a lean overview, which would lift progressive_disclosure toward 5.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-organized: it lists inputs as bullets, gives the output type, enumerates invariants and a debugging checklist with no padding or explanation of concepts Claude already knows. It is not a 5 only because the Inputs bullets are slightly informal and could be tightened into a precise schema.	4 / 5
Actionability	It gives concrete debugging steps and names specific checks (busy interval buffer expansion, booking limits, period caps), but there is no executable code or command in the body, only an import statement and prose. This matches the score-3 anchor of some concrete guidance but incomplete, with no copy-paste-ready code.	3 / 5
Workflow Clarity	The Debugging section provides a clear, ordered checklist for both 'unexpectedly missing' and 'unexpectedly present' slots with concrete checks, serving as an explicit feedback/diagnostic loop. Not a 5 because the steps are diagnostic checks rather than a numbered validate-then-fix loop with explicit pass/fail checkpoints.	4 / 5
Progressive Disclosure	The content is well structured into Inputs / Output / Invariants / Debugging sections with clear headers, and at roughly 40 lines there is no need for external references (none are present, and none are warranted). This fits the simple-skill exception for good structure; not a 5 only because some material (e.g., invariant details, buffer semantics) could be cleanly signaled as deeper reference.	4 / 5
	Total	15 / 20 Passed

Description

46%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 highly specific and distinct, naming a precise function and its documented facets, but it is missing any "Use when..." trigger guidance and uses technical jargon rather than the natural phrases a user would say. These gaps cap completeness and trigger-term quality well below the strong dimensions.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should invoke this skill (e.g., 'Use when debugging why a computed booking slot is missing or unexpectedly present, or when reasoning about the slot engine's invariants').

Include natural-language trigger terms users would actually say, such as 'available times', 'booking slots', 'scheduling', and 'calendar availability', alongside the function name.

Clarify the 'what' in plain terms (computing available booking slots) rather than only describing it as documentation of inputs/outputs/invariants.

Dimension	Reasoning	Score
Specificity	The description lists several concrete facets of the function ("inputs, outputs, invariants, and debugging guide") and names the specific function computeAvailableSlots, which is several specific actions rather than a single vague one. Not a 5 because the actions are facet labels rather than a comprehensive enumeration of concrete capabilities.	4 / 5
Completeness	It states a clear "what" (the pure function's inputs/outputs/invariants/debugging) but has no "when" / "Use when..." clause at all, so it sits at the low end of having a clear what with no when. Per judging guidelines, a missing Use-when clause should cap completeness at 3; here the what is also narrowly framed as documentation, so 2 fits.	2 / 5
Trigger Term Quality	It relies almost entirely on the technical symbol name computeAvailableSlots and the word "slots"; it lacks the natural phrases a user would say (e.g., "available times", "booking slots", "scheduling"). Only one or two generic-ish keywords are present, matching the score-2 anchor of missing the natural phrases users say.	2 / 5
Distinctiveness Conflict Risk	It targets a very specific named function (computeAvailableSlots from @agent-native/scheduling/core) with a clear niche, so it is highly distinct with minimal conflict risk against other skills. This clearly matches the score-5 anchor of a clear niche with distinct triggers.	5 / 5
	Total	13 / 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: bb282b1

Reviewed: ~21 hours 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.