booker

Public booking flow — the state machine, animations, and URL/app-state sync.

Quality

72%

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/booker/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 a tight, well-structured spec that gives concrete libraries, keys, ARIA roles, and breakpoints without padding. Its main gap is the absence of executable code examples, which keeps actionability at 4.

Dimension	Reasoning	Score
Conciseness	The body is lean (~40 lines) with no padding or re-explanation of concepts Claude already knows; every line states a specific value (e.g. "localStorage key `scheduling.timezone`", "<768px: stack vertically"), matching the "lean and efficient; every token earns its place" anchor.	5 / 5
Actionability	Concrete specifics are given ("motion/react `AnimatePresence` with `fadeInLeft`", "Sonner", "ARIA `grid`/`gridcell`", "aria-live=polite") but there is no copy-paste executable code and the Stages section is descriptive, fitting anchor 4 ("mostly executable guidance; minor gaps") rather than the fully-executable anchor 5.	4 / 5
Workflow Clarity	The pick-date → pick-slot → fill-form → success stages (plus reschedule) form a clear, ordered state machine; validation checkpoints are absent but not applicable to this non-destructive UI flow, so anchor 4 ("clear sequence with most checkpoints present") fits better than anchor 3.	4 / 5
Progressive Disclosure	At under 50 lines with no external references needed, the content is organized into well-labeled sections (Stages, Animations, Timezone, URL sync, Copy-link, Accessibility, Mobile), satisfying the simple-skill exception that lets progressive disclosure score 5 on well-organized sections alone.	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.

The description is concise and names a clear domain with several concrete aspects, but it lacks any "Use when..." trigger guidance and leans on technical jargon over natural user keywords. Completeness is capped at 3 by the missing trigger clause.

Suggestions

Add a "Use when..." clause naming natural triggers, e.g. "Use when building or modifying the public booking/scheduling flow, calendar, or appointment UI."

Include natural synonyms users say (scheduling, appointment, calendar, reschedule) alongside "booking flow" to improve trigger term coverage.

Keep the concrete aspect list but consider framing them as actions (e.g. "renders the booking state machine, animates stage transitions, syncs state to the URL") to lift specificity toward 5.

Dimension	Reasoning	Score
Specificity	Names the domain ("Public booking flow") and three concrete aspects ("the state machine, animations, and URL/app-state sync"), matching the "several specific actions; minor gaps" anchor rather than the comprehensive anchor 5 which omits form/success/accessibility/timezone details found in the body.	4 / 5
Completeness	There is a clear "what" but no "Use when..." clause or equivalent trigger guidance, so per the rubric cap completeness stays at 3 ("clear 'what' but 'when' missing or weakly implied").	3 / 5
Trigger Term Quality	"booking flow" is a natural user phrase, but the rest ("state machine", "URL/app-state sync") is technical jargon and common synonyms like scheduling, appointment, calendar, and reschedule are absent, fitting anchor 3 rather than the well-covered anchor 4.	3 / 5
Distinctiveness Conflict Risk	"Public booking flow" carves a clear niche distinct from generic skills, with only minor overlap risk against a broad scheduling/calendar skill, matching anchor 4 rather than anchor 5 which expects explicit distinct trigger phrases.	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/booker/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.