CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

integrations

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

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./packages/scheduling/docs/skills/integrations/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 efficient, highly specific operational reference: terse provider facts, a sequenced credential lifecycle with failure handling, exact error codes, and a useful command-to-intent table. Its main weaknesses are placeholder-laden commands and a 'Writing a new provider' section that defers entirely to a docs/providers.md file that is not part of the bundle.

Suggestions

Ship docs/providers.md inside the bundle (e.g. references/providers.md) or inline the provider interface contract, since 'Writing a new provider' currently points to a file that does not exist in the skill.

Replace placeholder arguments ('--redirectUri ...', '<zoom-cred>') with one complete, copy-paste-ready example per command.

Add a short verification step after the OAuth callback (e.g. confirm the scheduling_credentials row and fetched calendar list) to close the connect workflow with a checkpoint.

DimensionReasoningScore

Conciseness

Phrases like 'Daily.co-backed; zero OAuth; server-to-server API key' and 'Cached in calendar_cache (short TTL, default 5 min). Busted on any booking write for that host' are maximally terse and entirely project-specific; nothing explains concepts Claude already knows, and every line carries non-obvious operational detail. Not level 4: there are no trimmable over-explanations to point at.

5 / 5

Actionability

The Common tasks table gives concrete commands ('connect-calendar --kind google_calendar --redirectUri ...', 'set-default-conferencing-app --credentialId <zoom-cred>', 'completeVideoOAuth()') and error semantics are precise ('errorCode: "calendar_availability_unavailable"', 'status 503, or 429 with Retry-After'). Not level 5: commands carry placeholders ('--redirectUri ...', '<zoom-cred>') and the 'Writing a new provider' section contains no inline guidance at all; not level 3: the guidance given is executable and specific, not pseudocode.

4 / 5

Workflow Clarity

The credential lifecycle is a clearly sequenced 5-step flow that includes failure handling ('on failure, set invalid: true and show re-connect banner'), and the Teams section flags a real pitfall ('inserting a teams_video row with install-conferencing-app alone does not grant Microsoft access'). Not level 5: there is no explicit validate-before-proceeding checkpoint anywhere; not level 3: sequence and failure handling are explicit, and no destructive/batch cap applies.

4 / 5

Progressive Disclosure

In-file structure is good (clear sections, a task table), and the single reference is clearly signaled ('See docs/providers.md for the full interface'), but the bundle contains no files at all (no references/, scripts/, or assets/) and docs/providers.md is not present, leaving the core 'Writing a new provider' path dangling. Not level 4: the one reference cannot be verified against the actual bundle; not level 2: the inlined content is well organized, not an undifferentiated wall.

3 / 5

Total

16

/

20

Passed

Description

61%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 names a clear, provider-specific domain but reads as a topic label rather than a trigger-optimized description. It has good natural keywords from product names yet completely lacks a 'when to use' clause and omits Microsoft Teams, which the skill itself covers. Adding explicit trigger guidance and the missing provider terms would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. 'Use when connecting or troubleshooting calendar/video integrations — Google Calendar, Office 365/Outlook, Zoom, Google Meet, or Microsoft Teams — or when writing a new provider.'

Include the natural terms users say: 'Teams', 'Outlook', 'connect calendar', 'sync busy times', 'create Zoom/Teams meetings'.

State the concrete actions the skill supports (OAuth connect flows, busy-time aggregation, default conferencing app) rather than the bare word 'integrations'.

DimensionReasoningScore

Specificity

Names the domain ('Calendar + video provider integrations') with one concrete capability ('how to write new ones') and enumerates the covered providers ('Google Calendar, Office 365, Zoom, built-in video, Google Meet'), but never states what the integrations actually do (connect accounts, read freeBusy, create meetings). Not the level above: score 4 requires 'several specific actions'; not level 2: the provider enumeration and 'write new ones' go beyond a purely generic domain label.

3 / 5

Completeness

The 'what' is clear (integrations for the listed providers plus writing new ones), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not level 2: the 'what' is concrete, not vague; not level 4: 'when' is entirely absent rather than just imprecise.

3 / 5

Trigger Term Quality

Natural product names users would actually say are present ('Google Calendar', 'Office 365', 'Zoom', 'Google Meet'), but common variations are missing: 'Teams' and 'Outlook' (despite the skill covering teams_video), plus 'meeting', 'scheduling', 'connect'. Not level 5: coverage is not comprehensive (no synonyms or phrasing variants); not level 3: it does more than 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

Naming five specific providers ('Google Calendar, Office 365, Zoom, built-in video, Google Meet') carves a mostly distinct niche with minor overlap risk against generic calendar/scheduling skills. Not level 5: it lacks distinct trigger phrasing and omits Teams, so it could still collide with provider-specific or scheduling skills.

4 / 5

Total

14

/

20

Passed

Validation

100%

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

Reviewed

Table of Contents

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.