availability

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

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

Quality

Content

85%

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 reference that maps user requests to concrete actions with real table and field names. Its only weakness is actionability: a few table rows rely on "[...]" placeholders and one task lacks a dedicated command, preventing fully copy-paste-ready guidance.

Suggestions

Replace the "[...]" placeholders in the Common tasks table with concrete example values (e.g., real weeklyAvailability JSON for the lunch and evenings rows) so commands are copy-paste ready.

Add an explicit action or scripted step for the travel-schedules row instead of "Insert a travel_schedules row (no dedicated action yet)", or note the exact SQL/endpoint to use.

Optionally include a one-line worked example of an intervals JSON payload for date_overrides so the [] vs [{start,end}] distinction is immediately usable.

Dimension	Reasoning	Score
Conciseness	Lean ~40-line body that describes the model (tables, fields, interval semantics) and a compact task table with no padding or explanation of concepts Claude already knows; every token earns its place.	3 / 3
Actionability	Gives concrete table/field names and real commands ("add-date-override --scheduleId <id> --date 2026-04-10 --intervals []", "create-schedule", "update-schedule"), but several rows use "[...]" placeholders and one row is a manual insert ("no dedicated action yet"), so it is not fully copy-paste ready.	2 / 3
Workflow Clarity	As a reference/model skill the "Common tasks" table provides a clear, unambiguous request-to-action mapping; no destructive or batch operations exist that would require validation checkpoints.	3 / 3
Progressive Disclosure	Under 50 lines, single-purpose, with no need for external references, and cleanly organized into labeled sections (Schedule, Weekly availability, Date overrides, Travel schedules, Out of office, Common tasks).	3 / 3
	Total	11 / 12 Passed

Description

60%

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 precisely names the domain's components and outcome but omits any explicit "Use when..." trigger guidance, which limits completeness and trigger-term quality. It is specific and non-generic, yet not fully distinguishable from a general scheduling skill.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user asks about bookable hours, availability, OOO, travel timezones, or scheduling conflicts."

Add common natural phrasings users would actually say ("availability", "when am I free", "block my calendar") to broaden trigger-term coverage.

Sharpen distinctiveness by naming the booking-calculus framing ("combine to determine when someone is bookable") up front as the unique purpose versus a generic calendar skill.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete components ("schedules, weekly rules, date overrides, travel schedules, and out-of-office entries") and a concrete outcome ("when someone is bookable"), matching the anchor for multiple specific concrete items.	3 / 3
Completeness	Clearly answers "what does this do" (how the entities combine to determine bookability) but has no "Use when..." clause or equivalent explicit trigger guidance for when to invoke it, capping completeness at 2.	2 / 3
Trigger Term Quality	Contains some relevant natural terms ("schedules", "out-of-office", "travel", "bookable") but lacks common user phrasings like "availability" or "when am I free", so coverage of natural variations is incomplete.	2 / 3
Distinctiveness Conflict Risk	It targets a specific booking/availability niche but could still overlap with a broader calendar/scheduling skill, and lacks an explicit trigger clause to clearly separate it.	2 / 3
	Total	9 / 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/availability/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.