Name: calendarhero
Rating: 58.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

calendarhero

CalendarHero integration. Manage Persons, Meetings. Use when the user wants to interact with CalendarHero data.

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/calendarhero/SKILL.md

Quality

Content

68%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 commands and a well-validated connection state machine, but it loses conciseness to a marketing intro and loses workflow clarity points because destructive action execution lacks verification steps.

Suggestions

Delete the opening marketing paragraph ("CalendarHero is an AI-powered meeting scheduling platform...") and rhetorical asides; keep only operational context Claude needs to execute.

Add a validation checkpoint after running mutating actions, e.g. re-fetch the contact with get-contact to confirm an update applied, or instruct Claude to confirm with the user before destructive operations like deletions.

Optionally move the Popular actions and Proxy flag tables into a references/ file linked from SKILL.md to tighten the main body and improve progressive disclosure toward 5.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight, copy-paste CLI commands, but the opening marketing paragraph ("AI-powered meeting scheduling platform... used by sales, marketing, and customer success teams") and asides like "so you can focus on the integration logic rather than auth plumbing" are unnecessary padding Claude does not need.	3 / 5
Actionability	It provides copy-paste ready commands for every common case (install, login, connection ensure, action list/run, request proxy) plus concrete action-key and flag tables, fully covering execution without pseudocode gaps.	5 / 5
Workflow Clarity	The connection flow has a strong validation loop (poll --wait, branch on READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but mutating actions like Update Contact and Create Contact run with no verify/confirm step, so the destructive-operation cap at 3 applies.	3 / 5
Progressive Disclosure	Content is organized into well-labeled sections (Install, Authentication, Connecting, Searching, Popular actions, Running actions, Proxy, Best practices) with no nested references and appropriately inline material for a single-file CLI wrapper, though some tables could optionally live in a reference file.	4 / 5
	Total	15 / 20 Passed

Description

66%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 cleanly states what the skill does and when to use it for a distinct, named integration, with an explicit third-person trigger clause. Its main weakness is generic action verbs and missing synonyms (contacts, scheduling, bookings) that would improve trigger coverage and specificity.

Suggestions

Replace the generic verb "Manage" with concrete actions, e.g. "Create, update, and search contacts; list and schedule meetings" to lift specificity toward 4-5.

Expand the "Use when" clause with natural trigger phrases and synonyms, e.g. "Use when the user wants to manage CalendarHero contacts, meetings, scheduling, or bookings," to improve trigger term quality.

Dimension	Reasoning	Score
Specificity	"Manage Persons, Meetings" names the CalendarHero domain plus two entity-level actions, but the verb "Manage" is generic and coverage is not comprehensive, matching the 1-2 concrete actions anchor rather than the several-actions anchor at 4.	3 / 5
Completeness	Both "what" ("CalendarHero integration. Manage Persons, Meetings.") and an explicit "Use when the user wants to interact with CalendarHero data" trigger are present, but the "when" clause is generic rather than enumerating concrete triggers, matching the both-present-but-when-could-be-more-specific anchor.	4 / 5
Trigger Term Quality	It surfaces "CalendarHero", "Persons", and "Meetings", but misses common synonyms and variations a user might say such as contacts, scheduling, bookings, or calendar, so it sits at the some-relevant-keywords anchor rather than good coverage at 4.	3 / 5
Distinctiveness Conflict Risk	"CalendarHero integration" pins the skill to a specific named SaaS product with CalendarHero-anchored triggers, giving it a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	15 / 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/calendarhero/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.