booker

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

Quality

76%

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 an exemplary lean feature spec: terse, dense with project-specific facts (exact keys, breakpoints, ARIA attributes, library names) and cleanly sectioned. Its only weakness is actionability at the edges — several behaviors (stage width animation, clipboard fallback for mobile Safari, URL param names) are named but not given as executable code or exact values.

Dimension	Reasoning	Score
Conciseness	Every section is lean and project-specific — localStorage key 'scheduling.timezone', breakpoint '< 768px', 'aria-pressed', 'aria-live=polite' — with zero filler or explanation of concepts Claude already knows, matching 'every token earns its place'.	5 / 5
Actionability	Guidance is concrete throughout — named library ('motion/react' AnimatePresence with fadeInLeft variants), named component behaviors, exact keys, ARIA roles, and Sonner toasts — but there is no executable code for the stage transitions, width animation, or clipboard fallback, leaving minor gaps below the 'fully executable, copy-paste ready' anchor.	4 / 5
Workflow Clarity	The four stages (pick-date → pick-slot → fill-form → success) plus reschedule mode form a clear, well-ordered sequence, and the skill involves no destructive or batch operations so the validation cap does not apply; minor gaps remain in that no build/implementation order or error-handling checkpoints (e.g., mobile Safari clipboard failure) are spelled out.	4 / 5
Progressive Disclosure	At ~47 lines with well-organized headed sections and no external references needed (no references/, scripts/, or assets/ files exist and none are cited), this matches the simple-skill exception where compact, clearly sectioned content scores full marks.	5 / 5
	Total	18 / 20 Passed

Description

53%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 communicates a clear, specific scope for the skill but reads as a topic label rather than a capability statement: no third-person action verbs, no trigger guidance, and no user-facing synonyms. It is well above generic filler ('helps with documents') yet below the exemplar descriptions that pair concrete actions with an explicit 'Use when...' clause.

Suggestions

Add an explicit trigger clause, e.g. 'Use when working on the public booking flow, rescheduling, slot picking, or booking URL state.'

Convert the topic list into third-person action verbs, e.g. 'Implements the public booking flow state machine (pick-date, pick-slot, fill-form, success), stage animations, and URL/app-state sync.'

Include natural user-facing synonyms such as scheduling, calendar grid, time slots, and reschedule to improve trigger matching.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Public booking flow") and several concrete facets ("the state machine, animations, and URL/app-state sync"), but it is a noun-phrase scope statement with no action verbs — it names what the skill covers rather than what it does, matching the 'names domain and concrete items but not comprehensive actions' anchor.	3 / 5
Completeness	A clear 'what' is present (state machine, animations, URL/app-state sync for the public booking flow) but 'when' is entirely missing — there is no "Use when..." or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	"booking flow", "state machine", "animations", and "URL/app-state sync" are relevant keywords, but common natural phrasings users would say — scheduling, calendar, appointments, reschedule, booking page — are absent, matching the 'some relevant keywords but missing common variations or synonyms' anchor.	3 / 5
Distinctiveness Conflict Risk	"Public booking flow" with its named sub-domains carves a distinct niche unlikely to fire for unrelated skills; minor overlap risk remains with closely related scheduling/calendar UI skills, matching 'mostly distinct; minor overlap risk'.	4 / 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/booker/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.