Name: zoho-meeting
Rating: 52.8 (1 reviews)
Author: membranedev

zoho-meeting

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

Quality

59%

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/zoho-meeting/SKILL.md

Quality

Content

61%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 actionable and well-structured with executable Membrane CLI commands and a solid connection-state workflow, but it loses points to redundancy, a non-existent "Step 2" reference, and the absence of any Zoho-specific action example or result validation.

Suggestions

Fix the broken navigation: either add a real "Step 2" heading or replace the "skip to Step 2" references with the actual section name (e.g. "Searching for actions").

Add at least one concrete Zoho Meeting action example with real parameters and show how to validate the response in the `output` field.

Remove the redundant "Popular actions" section or merge it into "Searching for actions" to tighten token usage.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but includes some padding (the product description of Zoho Meeting, the "focus on integration logic rather than auth plumbing" phrasing) and a redundant "Popular actions" section that repeats the "Searching for actions" guidance.	3 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection, action search/run, and proxy requests with a clear flag table, but action-run examples use generic placeholders (CONNECTION_ID, <actionId>, '{"key": "value"}') with no Zoho-specific worked example.	4 / 5
Workflow Clarity	The connection flow has good state-based checkpoints and a poll-after-action feedback loop, but it references a "Step 2" heading that does not exist, uses a "1b" subsection with no "1a", and offers no validation guidance for verifying action results.	3 / 5
Progressive Disclosure	The body is well-organized into clear sections with no nested or broken references, and no bundle files are needed for this single-file integration overview; minor gaps are the inlined clientAction state detail and proxy flag table that could live in separate references.	4 / 5
	Total	14 / 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 answers both what and when and is anchored by a distinct brand trigger, but it relies on generic action language instead of concrete Zoho Meeting capabilities, capping specificity and trigger-term quality.

Suggestions

Replace generic verbs with concrete Zoho Meeting actions, e.g. "Schedule and manage meetings, retrieve recordings, and manage webinars and contacts."

Expand the trigger clause with natural phrases users say: "Use when the user wants to schedule or join Zoho Meetings, access recordings, or manage webinars."

Reference the specific resource types (Meetings, Recordings, Webinars, Contacts) that the skill exposes to improve distinctiveness.

Dimension	Reasoning	Score
Specificity	It names the domain ("Zoho Meeting") but the actions are generic — "Manage data, records, and automate workflows" — rather than concrete Zoho Meeting operations like scheduling meetings, managing recordings, or webinars.	2 / 5
Completeness	Both "what" (Zoho Meeting integration; manage data, records, automate workflows) and "when" ("Use when the user wants to interact with Zoho Meeting data") are present, though the trigger is generic rather than listing concrete use cases.	4 / 5
Trigger Term Quality	It includes the core keyword "Zoho Meeting" but misses natural variations and synonyms a user would say (webinars, recordings, video conferencing, online meetings).	3 / 5
Distinctiveness Conflict Risk	The "Zoho Meeting" brand name gives it a clear niche and low conflict risk with non-Zoho skills, though the generic action language leaves minor overlap with other Zoho app integrations.	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/zoho-meeting/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.