availability

How schedules, weekly rules, date overrides, travel schedules, and out-of-office entries combine to determine when someone is bookable.

Quality

75%

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/availability/SKILL.md

Quality

Content

80%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 reference: dense domain facts, exact data schemas, and a task-to-command mapping table with no wasted tokens. Its only notable gap is the absence of any validation/verification step for batch-style changes like wholesale weekly-availability updates, and a few placeholder-styled examples that are not fully executable.

Suggestions

Add a quick verification step after schedule-wide changes, e.g., re-check the resulting availability or confirm the affected days with the user before finishing.

Replace '[...]' placeholders in the weekly availability examples with one fully concrete example (e.g., day intervals in the exact expected format) so the commands are copy-paste ready.

Dimension	Reasoning	Score
Conciseness	Every line carries domain-specific, non-obvious information (e.g., 'Timezone is set on the schedule, not the user', 'intervals: [] → day fully blocked', 'day 0-6, startTime "HH:MM"'), with zero padding and no explanation of concepts Claude already knows. This matches the 'lean and efficient; every token earns its place' anchor.	5 / 5
Actionability	The Common tasks table gives concrete commands with real flags ('add-date-override --scheduleId <id> --date 2026-04-10 --intervals []', 'create-schedule --name Evenings --weeklyAvailability [...]') and the data-model sections specify exact schemas. It falls short of 5 because '[...]' placeholders and 'Insert a travel_schedules row (no dedicated action yet)' are not copy-paste ready, but it is well above 3 since the commands are concrete and cover the common cases.	4 / 5
Workflow Clarity	The per-request task mapping is unambiguous, but 'update-schedule --weeklyAvailability [...]' batch-overwrites the user's entire week and other operations block bookings with no validation or verification guidance (e.g., confirm the resulting availability), so the rubric's cap for batch operations without validation applies. Not 2, because each task maps to a clear, specific action with no sequence gaps.	3 / 5
Progressive Disclosure	The body is under 50 lines with well-organized sections (Schedule, Weekly availability, Date overrides, Travel schedules, Out of office, Common tasks) and no external references are needed, satisfying the simple-skill exception for progressive disclosure.	5 / 5
	Total	17 / 20 Passed

Description

57%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 precisely scoped, clearly explaining what the skill covers (how availability is computed from schedules, overrides, travel, and out-of-office entries). Its main weakness is the complete absence of a 'when to use' trigger clause, which caps completeness and weakens both trigger-term coverage and distinctiveness against adjacent calendar/booking skills.

Suggestions

Append an explicit trigger clause, e.g. 'Use when a user asks about their availability, wants to block dates, mention out-of-office, or asks when someone is bookable.'

Mention natural synonyms such as 'calendar', 'free/busy', and 'unavailable' so common user phrasings match the description.

Add one or two concrete actions (e.g., 'create schedules, add date overrides, block time') to raise capability specificity.

Dimension	Reasoning	Score
Specificity	The description names the domain and five concrete constituent concepts ("schedules, weekly rules, date overrides, travel schedules, and out-of-office entries") but lists no capabilities or actions (e.g., create schedules, block dates), matching the 'names domain with some concrete specifics, not comprehensive' anchor. It is more specific than anchor 2 ('names the domain but actions are minimal or generic') because the enumerated concepts are precise, but lacks the multiple concrete actions needed for 4.	3 / 5
Completeness	It clearly answers 'what' ("how schedules, weekly rules, date overrides, travel schedules, and out-of-office entries combine to determine when someone is bookable") but contains no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3. It is not a 2 because the 'what' is concrete and specific, not vague.	3 / 5
Trigger Term Quality	Terms like "schedules", "date overrides", "out-of-office", "travel schedules", and "bookable" are natural phrases a user would say when needing this skill, giving good keyword coverage. It falls short of 5 because common variations such as "calendar", "free/busy", and "availability" itself are absent.	4 / 5
Distinctiveness Conflict Risk	The availability/bookability niche is fairly specific, but without explicit triggers it could still overlap with related calendar, booking, or event-scheduling skills, matching 'somewhat specific but could still overlap with similar skills'. Not 4, since no trigger phrasing distinguishes it from those adjacent skills.	3 / 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/availability/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.