Name: zoho-catalyst
Rating: 60 (1 reviews)
Author: membranedev

zoho-catalyst

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

Quality

70%

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

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 content is highly actionable with concrete CLI commands and a clear state-driven connection workflow. It is weakened mainly by minor padding and a dangling "Step 2" reference rather than by structural problems.

Suggestions

Trim the marketing intro paragraph and remove the filler "Use action names and parameters as needed" plus the duplicated action-list command under Popular actions to tighten token efficiency.

Resolve the undefined "Step 2" reference by either adding a numbered Step 2 heading (e.g., Searching for actions) or replacing the cross-reference with the actual next action.

Expand the thin Overview bullet list (Data Store/Rows, Functions, Cache, File Store) into one-line concrete pointers so the overview earns its place.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI reference that Claude would not already know, but it carries padding: the marketing-style intro paragraph about what Zoho Catalyst is, the filler line "Use action names and parameters as needed", and a duplicated action-list command under "Popular actions".	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands throughout (install, login, connection ensure, connection get --wait, action list/run, request) plus a concrete proxy-flag table, covering the common integration cases.	5 / 5
Workflow Clarity	There is a clear sequenced workflow (install → login → connection ensure → poll for READY → search → run) with explicit state checkpoints and polling feedback loops, but the referenced "Step 2" is never defined as a heading, leaving a minor navigation gap.	4 / 5
Progressive Disclosure	Content is organized into clear sections (Overview, Working with, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) in a single self-contained file with no bundle references; structure is good with minor gaps such as the thin Overview list and the dangling "Step 2" reference.	4 / 5
	Total	16 / 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 clearly names the product and includes an explicit Use-when trigger, giving it strong distinctiveness and solid completeness. It is held back by somewhat generic action wording and limited trigger-term variation.

Suggestions

Replace generic verbs/objects ("manage data, records") with more specific Zoho Catalyst capabilities (e.g., query Data Store rows, invoke Functions, read/write File Store) to lift specificity.

Expand the Use-when clause with multiple concrete trigger phrases users would actually say (e.g., "Use when the user wants to query Catalyst Data Store, run Catalyst Functions, manage Cache, or read/write File Store").

Add the main sub-products as trigger keywords (Data Store, Functions, Cache, File Store) to broaden natural-term coverage.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Zoho Catalyst domain plus two to three actions, but the action objects ("data", "records", "workflows") are generic rather than concrete, so it is not comprehensive enough for a 4.	3 / 5
Completeness	It explicitly states both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Zoho Catalyst data"), but the when clause is a single narrow trigger rather than multiple concrete trigger phrases, so it falls short of a 5.	4 / 5
Trigger Term Quality	The natural product name "Zoho Catalyst" appears as the primary trigger and is repeated in the Use-when clause, but the clause offers only one trigger phrasing ("interact with Zoho Catalyst data") with limited synonyms or variations, matching the anchor with relevant-but-incomplete keyword coverage.	3 / 5
Distinctiveness Conflict Risk	The named product "Zoho Catalyst" gives the skill a clear niche with a distinct trigger ("interact with Zoho Catalyst data") and minimal overlap risk with 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/zoho-catalyst/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.