event-types

How event types work — fields, scheduling types, tabs in the editor, and the full set of configurable options.

Quality

78%

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

Quality

Content

92%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 factual tables, exact identifiers, and non-obvious domain details with no filler. Its only soft spot is actionability — it documents rather than instructs, so a single example of using add-private-link (or a sample payload) would close the gap.

Dimension	Reasoning	Score
Conciseness	Lean tables and lists with zero padding and no explanation of concepts Claude already knows. Facts like 'Stored on the event type; responses stored on the booking' are exactly the non-obvious details that earn their tokens. Matches the 'lean and efficient; every token earns its place' anchor.	5 / 5
Actionability	Concrete, usable reference data: exact enum values ('builtin-video', 'attendee-choice'), a real URL pattern ('/d/:hash/:slug'), and a concrete operation ('add-private-link') with parameters ('expiresAt', 'isSingleUse'). Mostly actionable with minor gaps — one operation is named but no example command/payload is shown, keeping it below fully copy-paste-ready.	4 / 5
Workflow Clarity	This is a single-purpose reference skill under 50 lines with no multi-step process and no destructive or batch operations, so the simple-skill exception applies: the content's single purpose (documenting event-type structure) is unambiguous and clearly organized. No validation checkpoints are needed for read-only reference material.	5 / 5
Progressive Disclosure	Under 50 lines with no need for external references (no bundle files exist and none are referenced), and the body is organized into clear sections with a well-formed table. Direct match for the simple-skill anchor: 'well-organized sections' suffice at this size.	5 / 5
	Total	19 / 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 gives a clear, compact picture of what the skill covers, and its domain term is distinct. Its main weakness is the complete absence of a 'when to use' clause plus sparse natural trigger phrases, which leaves it relying on a reader already knowing they want event-type configuration.

Suggestions

Add an explicit trigger clause, e.g. 'Use when creating, configuring, or debugging event types, booking limits, or scheduling links.'

Include natural user phrases/synonyms such as 'bookings', 'availability', or 'meeting types' to improve trigger-term coverage.

Convert at least part of the topic list into action language (e.g. 'Configure fields, scheduling types, limits, and private links') to raise capability specificity.

Dimension	Reasoning	Score
Specificity	Names the domain ('event types') and enumerates concrete topics ('fields, scheduling types, tabs in the editor, and the full set of configurable options'), but lists no concrete actions or verbs — it describes scope rather than capabilities. This sits between the domain-only anchor (2) and a list of specific actions (4).	3 / 5
Completeness	The 'what' is clear ('How event types work — fields, scheduling types, tabs in the editor, and the full set of configurable options') but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because the 'when' is entirely absent, not merely implicit.	3 / 5
Trigger Term Quality	'event types', 'scheduling types', 'tabs', 'editor', and 'configurable options' are relevant keywords, but common natural variations a user might say — 'bookings', 'availability', 'meetings', 'calendar' — are missing. Matches 'some relevant keywords but missing common variations or synonyms' rather than good coverage with a few gaps.	3 / 5
Distinctiveness Conflict Risk	'Event types' is a niche, domain-specific term with minimal conflict risk against generic skills. Not 5 because no explicit trigger phrases are present to fully lock in the niche, and adjacent topics (schedules, workflows, locations) could pull related queries.	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/event-types/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.