integrations

Calendar + video provider integrations — Google Calendar, Office 365, Zoom, built-in video, Google Meet — and how to write new ones.

Quality

73%

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

Quality

Content

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is concise and highly actionable with concrete commands and identifiers, but multi-step workflows lack explicit validation checkpoints and the single external reference points to a file that does not exist in the bundle.

Suggestions

Add explicit validation/checkpoint steps to the credential lifecycle and refresh flow (e.g. verify token validity after exchange; on refresh failure, confirm re-connect banner state).

Either create docs/providers.md so the 'See docs/providers.md' reference resolves, or inline the provider interface contract so the reference is not dangling.

Dimension	Reasoning	Score
Conciseness	The body is lean and dense with concrete identifiers, commands, and DB rows, assuming Claude's competence and avoiding explanatory padding about what calendars or OAuth are.	3 / 3
Actionability	Concrete executable commands (connect-calendar --kind ..., set-default-conferencing-app --credentialId, refresh-busy-times) and a precise function signature with parameters make guidance copy-paste ready.	3 / 3
Workflow Clarity	The credential lifecycle is numbered and sequenced, but there are no explicit validation checkpoints or error-recovery feedback loops for the OAuth/refresh flow that handles token invalidation, capping clarity at 2.	2 / 3
Progressive Disclosure	Structure is present via clear sections and a one-level pointer to docs/providers.md, but no bundle file exists at that path so the reference is unverifiable, and some detail (Teams setup, busy aggregation) is inline rather than split out.	2 / 3
	Total	10 / 12 Passed

Description

67%

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 distinctive, naming concrete providers and the 'write new ones' capability, but it omits an explicit 'Use when...' trigger clause, so completeness is capped. Voice is correctly third person.

Suggestions

Add an explicit trigger clause, e.g. 'Use when working with calendar or video integrations, connecting Google Calendar/Office 365/Zoom/Teams, or writing new scheduling providers.'

Include more natural user-facing variations (e.g. 'meeting links', 'video conferencing', 'booking providers') to broaden trigger term coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities and named providers (Google Calendar, Office 365, Zoom, built-in video, Google Meet) plus the action of writing new ones, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	It clearly answers 'what' (integrations and how to write new ones) but the 'when' is only implied; there is no explicit 'Use when...' trigger clause, which caps completeness at 2 per the guidelines.	2 / 3
Trigger Term Quality	Names recognizable provider/product terms (Google Calendar, Zoom, Microsoft Teams) a user might say, but lacks common natural variations and has no 'Use when...' phrasing, leaving coverage partial.	2 / 3
Distinctiveness Conflict Risk	The calendaring/video-provider integration niche is specific and unlikely to trigger for unrelated skills, fitting the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	10 / 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/integrations/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.