bookings

Booking lifecycle — pending, confirmed, rescheduled, cancelled — plus attendees, references, no-shows, and reminders.

Quality

77%

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/bookings/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 concise, well-structured reference for the bookings domain with excellent token efficiency and organization. Its weakness is actionability and workflow clarity: it documents the model rather than instructing concrete actions, and lacks validation checkpoints for cancel/reschedule operations.

Suggestions

Add concrete, executable guidance for the key operations (e.g. how to call reschedule-booking, mark-no-show, or fetch the ICS endpoint) so Claude can act, not just reference.

Include a validation/verification step in the reschedule and cancel flows (e.g. confirm from_reschedule linkage and iCalSequence bump) to add a feedback loop.

Dimension	Reasoning	Score
Conciseness	Lean, well-organized reference content with no padding and no explanation of concepts Claude already knows; every line delivers a concrete fact (field names, endpoints, RFC references).	3 / 3
Actionability	It supplies concrete specifics (fromReschedule, iCalSequence, noShow, cancelToken, /booking/:uid.ics) but describes the data model rather than giving executable instructions or commands, so guidance is specific yet not copy-paste actionable.	2 / 3
Workflow Clarity	The lifecycle and reschedule chain are sequenced, but there are no validation checkpoints or feedback loops for the cancel/reschedule operations, capping workflow clarity at 2.	2 / 3
Progressive Disclosure	Under 50 lines with no external references needed, organized into clear single-purpose sections (Lifecycle, No-show, Tokens, References, ICS) — well-organized sections satisfy progressive disclosure for a simple skill.	3 / 3
	Total	10 / 12 Passed

Description

82%

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 and uses natural trigger terms within a clear niche, but it omits any explicit 'Use when...' guidance, so it does not fully answer when Claude should invoke the skill. Adding a trigger clause would raise completeness.

Suggestions

Append an explicit 'Use when...' clause, e.g. 'Use when the user asks about booking states, reschedules, cancellations, no-shows, or reminders.'

Lead with a verb-based action phrase (e.g. 'Manages the booking lifecycle...') to make the capability more action-oriented.

Dimension	Reasoning	Score
Specificity	Names a concrete domain (booking lifecycle) and enumerates specific states (pending, confirmed, rescheduled, cancelled) plus concrete feature areas (attendees, references, no-shows, reminders) — multiple specific concrete items rather than vague language.	3 / 3
Completeness	It clearly answers 'what' (booking lifecycle and related areas) but has no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	Includes natural terms a user would actually say — 'booking', 'rescheduled', 'cancelled', 'reminders', 'attendees', 'no-shows' — with good coverage of common variations rather than technical jargon.	3 / 3
Distinctiveness Conflict Risk	The bookings-lifecycle niche with its specific states and tokens is clearly distinguishable from other skills and unlikely to trigger for the wrong skill.	3 / 3
	Total	11 / 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/bookings/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.