Name: calendso
Rating: 60.8 (1 reviews)
Author: membranedev

calendso

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

Quality

71%

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

Quality

Content

82%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 content is highly actionable with concrete CLI commands and a well-validated connection workflow, suffering only from minor padding and slightly inconsistent step numbering rather than structural problems.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient, built around concrete commands, but includes mild padding such as the introductory 'It's used by businesses and individuals...' line and the filler 'Use action names and parameters as needed.'	4 / 5
Actionability	It provides fully executable, copy-paste-ready CLI commands with flags and a complete options table, covering connection, action discovery, running actions, and proxying requests.	5 / 5
Workflow Clarity	The connection workflow has a clear sequence with validation checkpoints (polling state, handling READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR and re-polling), though step numbering is inconsistent (references an unlabeled 'Step 2').	4 / 5
Progressive Disclosure	Content is well-organized into clear sections in a single file with no nested references, but material like the proxy options table and full clientAction schema could arguably live in a separate reference file.	4 / 5
	Total	17 / 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 is distinct and includes both a 'what' and a 'when' clause, but its capability actions are generic and its trigger vocabulary is limited to the product name without natural synonyms.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete Calendso actions such as managing bookings, event types, availability, and calendars.

Broaden the trigger with natural terms users actually say, e.g. 'Use when the user wants to manage Calendso/Cal.com bookings, appointments, event types, or scheduling.'

Dimension	Reasoning	Score
Specificity	It names the Calendso domain but the actions ('Manage data, records, and automate workflows') are minimal and generic rather than concrete scheduling actions like booking or event-type management.	2 / 5
Completeness	It states both what ('Calendso integration. Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Calendso data'), though the 'when' trigger is somewhat generic.	4 / 5
Trigger Term Quality	The keyword 'Calendso' is a relevant natural term, but there are no common variations or synonyms (e.g. bookings, appointments, scheduling, Cal.com) users might also say.	3 / 5
Distinctiveness Conflict Risk	'Calendso integration' is a clear niche tied to a named product, with distinct triggers and minimal risk of conflicting with other skills.	5 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/calendso/SKILL.md
Commit: f484c82

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.