booker

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

Quality

61%

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

72%

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 lean, well-organized overview that assumes Claude's competence, but it offers no executable code and lacks validation/error-recovery checkpoints for the multi-stage flow.

Suggestions

Add at least one minimal executable snippet (e.g. an AnimatePresence stage wrapper or the URL↔application_state sync effect) to move actionability toward copy-paste ready.

Specify validation/error-recovery behavior in the flow: form-field validation, slot-unavailability handling, and how a failed reschedule is surfaced.

Clarify the state-machine transitions explicitly (allowed forward/backward moves and what triggers each) so the workflow sequence has explicit checkpoints.

Dimension	Reasoning	Score
Conciseness	The body is lean and information-dense — it names specific libraries (motion/react, Sonner), keys (scheduling.timezone, application_state.booker-state), and attributes without explaining concepts Claude already knows, so every token earns its place.	3 / 3
Actionability	Guidance is concrete — naming AnimatePresence + fadeInLeft, specific ARIA attributes, the 768px breakpoint, and exact state keys — but there is no executable code or copy-paste snippet, so it is more specific than the vague score-1 anchor yet incomplete versus the fully-executable score-3 anchor.	2 / 3
Workflow Clarity	The four stages (pick-date → pick-slot → fill-form → success) give a clear sequence, but there are no validation checkpoints or error-recovery handling (e.g. form validation failure, no-slots case), matching 'sequence present but checkpoints missing or implicit'.	2 / 3
Progressive Disclosure	At ~47 lines with no external references and no bundle files, the body is organized into well-labeled sections (Stages, Animations, Timezone, URL sync, Copy-link, Accessibility, Mobile), which the rubric's simple-skills note says can score 3 on well-organized sections alone.	3 / 3
	Total	10 / 12 Passed

Description

50%

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 about the booking-flow niche and its facets but stops short of stating concrete actions or an explicit 'Use when' trigger, leaving all dimensions at the midpoint.

Suggestions

Add an explicit trigger clause, e.g. 'Use when working on the public booking/scheduling flow: stage transitions, animations, or URL/app-state sync.'

Reframe facets as concrete actions (e.g. 'drives the pick-date → pick-slot → fill-form → success state machine, animates stage transitions, and syncs selection to URL + application_state') to lift specificity.

Include natural user variations such as 'scheduling', 'appointment', 'calendar', and 'reschedule' to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The phrase 'the state machine, animations, and URL/app-state sync' names the domain and enumerates three concrete facets, but these are noun-phrase features rather than the concrete actions (verbs) the score-3 anchor calls for, so it sits above the vague score-1 anchor but below comprehensive action listing.	2 / 3
Completeness	It clearly answers what ('Public booking flow — the state machine, animations, and URL/app-state sync') but has no 'Use when...' clause or equivalent explicit trigger guidance, which the guidelines say caps completeness at 2.	2 / 3
Trigger Term Quality	'Public booking flow' is a natural term a user might say, but common variations a user would actually use (scheduling, appointment, calendar, reschedule) are absent, matching the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	'Public booking flow' carves a recognizable niche, but with no explicit triggers it could still overlap with a broader scheduling/calendar skill, fitting the 'somewhat specific but could still overlap' anchor rather than the distinct-trigger score-3 example.	2 / 3
	Total	8 / 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/booker/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.