CtrlK
BlogDocsLog inGet started
Tessl Logo

zoho-bookings

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

57

Quality

66%

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 ./skills/zoho-bookings/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 concrete, copy-paste Membrane CLI commands and a clear connection state-polling workflow, but it carries some over-explanation and redundancy that slightly reduce conciseness.

Suggestions

Trim the introductory paragraph explaining what Zoho Bookings is, since Claude can infer the product's purpose from its name and the official-docs link.

Consolidate the duplicated action-discovery command between 'Searching for actions' and 'Popular actions' into a single section to remove redundancy.

Fix the step numbering inconsistency (referencing 'Step 2' without a labeled 'Step 1') so the workflow sequence is unambiguous.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete commands, but the opening paragraph explaining what Zoho Bookings is and the near-duplicate action-list command in 'Popular actions' (repeating the 'Searching for actions' guidance) are unnecessary padding.

3 / 5

Actionability

It provides copy-paste-ready commands for install, login, connection ensure/get with --wait, action list/run with JSON input, and proxy requests with a full flag table, covering the common cases fully.

5 / 5

Workflow Clarity

The connect-and-poll sequence is clearly laid out with a state-based feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR and re-polling), though the inconsistent step numbering ('Step 2' referenced without a labeled Step 1) leaves a minor gap.

4 / 5

Progressive Disclosure

Content is well-organized into clear sections with no nested references and only an official-docs link, but the skill is a single ~140-line file with some redundancy between 'Searching for actions' and 'Popular actions' that could be tightened.

4 / 5

Total

16

/

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 cleanly identifies the Zoho Bookings product and includes an explicit 'Use when' clause, but its capability verbs are generic and it omits natural scheduling-domain trigger terms like appointments or bookings.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Zoho Bookings actions such as 'create and manage appointments, services, and staff bookings'.

Add natural trigger terms users would say — e.g. 'appointments', 'scheduling', 'bookings' — to improve trigger-term coverage.

Tighten the 'Use when' clause with concrete triggers, e.g. 'Use when the user wants to create, view, or reschedule Zoho Bookings appointments'.

DimensionReasoningScore

Specificity

The description names the Zoho Bookings domain but its actions ('Manage data, records, and automate workflows') are minimal and generic rather than concrete, matching the 'names the domain but actions are minimal or generic' anchor.

2 / 5

Completeness

Both 'what' (Zoho Bookings integration; manage data/records; automate workflows) and 'when' ('Use when the user wants to interact with Zoho Bookings data') are present, though the trigger clause could be more specific with concrete phrases.

4 / 5

Trigger Term Quality

It surfaces the product name 'Zoho Bookings' and 'data, records, workflows', but misses the natural domain phrases users would say (appointments, bookings, scheduling), so keyword coverage is only partial.

3 / 5

Distinctiveness Conflict Risk

Naming the specific product 'Zoho Bookings' gives it a clear niche with low conflict risk, though the generic 'manage data, records, and automate workflows' phrasing leaves minor overlap risk with adjacent Zoho or data skills.

4 / 5

Total

13

/

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.