event-types

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

Quality

70%

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

86%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 exceptionally lean, well-organized reference with concrete enums, paths, and API names, achieving top conciseness and progressive-disclosure scores; it is held back only slightly on actionability and workflow clarity because it is a catalog rather than a sequenced, executable procedure.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient — terse bullets, a compact table, and specific enums with no padding or explanation of concepts Claude already knows, so every token earns its place.	5 / 5
Actionability	It provides concrete specifics (location-kind enums, the hashed-link path `/d/:hash/:slug`, the `add-private-link` action with `expiresAt`/`isSingleUse`), but as an instruction-only reference it stops short of fully executable copy-paste examples, leaving minor gaps.	4 / 5
Workflow Clarity	Sections are clearly sequenced and well-organized with no destructive or batch operations requiring validation, but this is a reference catalog rather than a multi-step workflow, so it does not reach the explicit-checkpoint clarity of a score-5 workflow.	4 / 5
Progressive Disclosure	The skill is under 50 lines, needs no external references, and is organized into clearly labeled sections (Editor tabs, Scheduling types, Location kinds, Custom fields, Hashed links), meeting the simple-skill exception for well-organized structure.	5 / 5
	Total	18 / 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 is third-person and names a clear, distinct niche with several concrete facets, but it lacks any explicit "Use when..." trigger guidance, which caps completeness and limits trigger-term quality to adequate rather than comprehensive.

Suggestions

Add an explicit 'Use when...' clause naming natural user triggers (e.g., 'Use when configuring or explaining event types, scheduling types, or booking options').

Reframe the facet list as concrete actions (e.g., 'Configure event type fields, scheduling types, editor tabs, and booking options') to lift specificity above the topic-listing anchor.

Include common synonyms users might say (e.g., 'booking types', 'meeting types', 'scheduling') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ("event types") and lists several concrete facets ("fields, scheduling types, tabs in the editor, and the full set of configurable options"), but these are topics rather than executable actions, so it sits at the anchor that names the domain with a few concrete items rather than comprehensive actions.	3 / 5
Completeness	It gives a clear "what" (how event types work and their configurable options) but includes no "Use when..." clause or equivalent trigger guidance, so per the judging guidelines completeness is capped at 3.	3 / 5
Trigger Term Quality	"event types", "scheduling types", and "tabs in the editor" are relevant keywords a user might say, but common synonyms and variations are missing, matching the anchor for some relevant keywords without comprehensive coverage.	3 / 5
Distinctiveness Conflict Risk	"event types" is a specific niche within scheduling/calendar tooling with distinct triggers, leaving only minor overlap risk with closely related scheduling skills rather than the broader overlap of a score-3 anchor.	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: 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.