Name: you-can-book-me
Rating: 55.2 (1 reviews)
Author: membranedev

you-can-book-me

You Can Book Me integration. Manage data, records, and automate workflows. Use when the user wants to interact with You Can Book Me data.

Quality

63%

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/you-can-book-me/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 command-dense and largely efficient, with concrete copy-paste-ready Membrane CLI commands covering install, auth, connection, action discovery, and proxy use. Workflow clarity is held back by a dangling 'Step 2' reference and the absence of validation/verification guidance for destructive proxy operations (DELETE/PUT/PATCH).

Suggestions

Add explicit validation/verification guidance for destructive proxy operations — e.g., after a DELETE/PUT, check the response status and confirm the resource state before proceeding — to lift workflow clarity above the destructive-operation cap.

Fix the dangling 'Step 2' reference by explicitly labeling the 'Searching for actions' section as 'Step 2' (and the connection section as 'Step 1') so the skip-to instructions resolve.

Make the 'Popular actions' section earn its heading by listing a few concrete common You Can Book Me actions (e.g., list bookings, get availability, create a booking) instead of only repeating the discovery command.

Dimension	Reasoning	Score
Conciseness	The body is command-dense and largely tight, with brief explanations attached to each bash block. It is not a 5 because the intro paragraph ('It eliminates back-and-forth emails... consultants, therapists, or service providers') and a few editorial phrases ('focus on the integration logic rather than auth plumbing') could be trimmed.	4 / 5
Actionability	It provides concrete, executable commands for install, login, connect, poll, action list/run, and proxy (with a complete flags table). It is not a 5 because the YCBM-specific action examples are templates ('--input {"key": "value"}') and discovery-driven rather than worked concrete examples.	4 / 5
Workflow Clarity	The connection flow has a clear state-based sequence with feedback loops (poll --wait, re-poll after CLIENT_ACTION_REQUIRED, check error on failure). It is capped at 3 because the proxy supports destructive methods (DELETE/PUT/PATCH) with no validation/verification step, and the 'skip to Step 2' reference is dangling with no labeled Step 2.	3 / 5
Progressive Disclosure	With no bundle files, the single document is well-organized into clear navigable section headers appropriate for a CLI-usage skill. It is not a 5 because the 'Popular actions' heading promises a list but only repeats the discovery command instead of enumerating common actions.	4 / 5
	Total	15 / 20 Passed

Description

57%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 the product clearly and includes an explicit 'Use when' trigger clause, giving it solid completeness and distinctiveness. Its capability list is generic and lacks concrete YCBM-specific actions, and trigger coverage relies on the product name alone without synonyms like 'scheduling' or 'appointments'.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete YCBM-specific actions such as 'create and manage bookings, set availability, and view appointment schedules'.

Expand trigger terms beyond the product name to include natural synonyms users say, e.g. 'scheduling', 'appointments', 'booking pages', or 'availability'.

Make the 'Use when' clause more specific by naming concrete scenarios, e.g. 'Use when the user wants to create bookings, check availability, or manage You Can Book Me appointments.'

Dimension	Reasoning	Score
Specificity	It names the domain ('You Can Book Me integration') but the actions — 'Manage data, records, and automate workflows' — are generic and abstract rather than concrete YCBM-specific operations (e.g. create bookings, set availability). It is not a 3 because no concrete domain-specific actions are enumerated.	2 / 5
Completeness	It states a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with You Can Book Me data'). It is not a 5 because the 'what' is generic and the trigger phrase ('interact with ... data') lacks concrete scenarios.	4 / 5
Trigger Term Quality	The product name 'You Can Book Me' appears twice and is a natural keyword a user would say, but no synonyms or variations (scheduling, appointments, bookings, availability) are included. It is not a 4 because coverage is thin — only the product name, not a breadth of natural terms.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product gives a clear niche and distinct trigger ('You Can Book Me data'). It is not a 5 because the generic action phrasing ('Manage data, records, automate workflows') could apply to many scheduling/CRM integrations, creating minor overlap risk.	4 / 5
	Total	13 / 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/you-can-book-me/SKILL.md
Commit: f484c82

Reviewed: 3 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.