CtrlK
BlogDocsLog inGet started
Tessl Logo

cronofy

Cronofy integration. Manage data, records, and automate workflows. Use when the user wants to interact with Cronofy data.

56

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/cronofy/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%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 highly actionable with executable CLI commands and a clearly sequenced connection workflow with state-based checkpoints, slightly weakened by an unnecessary introductory explanation of what Cronofy is and an unanchored API resource list.

DimensionReasoningScore

Conciseness

The body is mostly efficient with copy-pasteable CLI commands, but the opening paragraph explaining what Cronofy is ('a scheduling automation platform that connects to users' calendars...') is background Claude already knows and could be trimmed.

3 / 5

Actionability

It provides fully executable, copy-paste-ready commands throughout (install, login, connection ensure/get with --wait, action list/run, request proxy) with concrete flags and a parameter table covering the common cases.

5 / 5

Workflow Clarity

The connection flow is clearly sequenced with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and poll-again feedback, but running actions lacks explicit validation of the output before proceeding.

4 / 5

Progressive Disclosure

Content is well-organized into clearly headed sections (Install, Auth, Connecting, Searching, Running, Proxy, Best practices) with no bundle files to link to; minor gap is the overview bullet list of API resources is unanchored to any detail.

4 / 5

Total

16

/

20

Passed

Description

51%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 includes an explicit 'Use when' trigger and names the Cronofy domain, satisfying the what/when requirement, but its action vocabulary is generic and it omits the natural scheduling/calendar terms users would actually say.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete Cronofy actions such as 'Sync calendars, schedule events, and manage bookings'.

Add natural trigger terms users would say: calendars, appointments, scheduling, availability, meetings.

Tighten the trigger clause to reference Cronofy-specific signals (e.g. 'Use when working with Cronofy calendars or scheduling automation').

DimensionReasoningScore

Specificity

It names the domain (Cronofy) but the actions are generic — 'Manage data, records, and automate workflows' lists no concrete Cronofy operations such as scheduling, calendar sync, or booking.

2 / 5

Completeness

It states both a clear 'what' (manage Cronofy data, records, workflows) and an explicit 'when' ('Use when the user wants to interact with Cronofy data'), though the trigger phrase could be more specific.

4 / 5

Trigger Term Quality

'interact with Cronofy data' and 'Cronofy integration' are relevant keywords, but it misses the natural scheduling phrases a user would say (appointments, calendars, scheduling, booking) and any file-type tokens.

3 / 5

Distinctiveness Conflict Risk

'Manage data, records, and automate workflows' is broad and could overlap with generic data-management skills, though the Cronofy name provides a clear niche anchor.

3 / 5

Total

12

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
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.