team-scheduling

Team event types, round-robin assignment, collective bookings, host weights, and no-show calibration.

Quality

69%

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/team-scheduling/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 content is a concise, well-structured domain reference with concrete commands and data-model details; its only real weakness is the absence of validation checkpoints in the multi-step host-configuration workflow.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-organized with no padding and no explanation of concepts Claude already knows; every section (types, strategies, hosts, OOO, tasks) earns its place.	5 / 5
Actionability	Concrete commands and data structures are given (e.g. 'create-event-type --schedulingType round-robin --teamId ...', the event_type_hosts row shape, inserting an out_of_office_entries row), but commands use placeholders rather than being fully copy-paste ready.	4 / 5
Workflow Clarity	The common-tasks table gives a sequenced action pair (create-event-type then set-event-type-hosts), but there are no validation checkpoints or feedback loops for batch host operations.	3 / 5
Progressive Disclosure	At roughly 50 lines with no external references needed, the body is cleanly split into well-signaled sections and tables, satisfying the simple-skill exception for progressive disclosure.	5 / 5
	Total	17 / 20 Passed

Description

58%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 specific and distinct, naming a clear team-scheduling niche, but it is a noun-phrase list with no 'Use when' trigger guidance and only partial coverage of natural user phrasings.

Suggestions

Add an explicit trigger clause, e.g. 'Use when configuring team event types, round-robin or collective bookings, or adjusting host assignment weights.'

Lead with a third-person verb phrase (e.g. 'Configures team event types...') instead of a bare noun list to strengthen the 'what'.

Include a few natural user-facing synonyms such as 'rotate hosts', 'team scheduling', and 'team meeting' to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete capabilities ('round-robin assignment, collective bookings, host weights, and no-show calibration'), but they are noun phrases rather than verb-driven actions, leaving a minor gap versus the comprehensive-action anchor.	4 / 5
Completeness	A clear 'what' is present (team event types and the listed scheduling features), but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Relevant keywords like 'team', 'round-robin', 'collective bookings', and 'no-show' appear, but common natural variations users would say ('team scheduling', 'rotate hosts', 'team meeting') are missing and several terms lean toward domain jargon.	3 / 5
Distinctiveness Conflict Risk	The niche is clearly team-based scheduling with distinct terms ('round-robin', 'collective', 'no-show calibration'), with only minor overlap risk against generic calendar/scheduling skills.	4 / 5
	Total	14 / 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/team-scheduling/SKILL.md
Commit: bb282b1

Reviewed: ~21 hours 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.