Name: zoho-commerce
Rating: 56.8 (1 reviews)
Author: membranedev

zoho-commerce

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

Quality

64%

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

Quality

Content

63%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 executable commands and a clear, state-aware connection workflow, but it leans on a monolithic single-file layout and includes a few explanatory passages Claude does not need. Splitting reference material into bundled files and trimming preamble would improve it.

Suggestions

Move the proxy flag reference and action-discovery details into a bundled reference file (e.g. references/proxy.md) and link to it from the body to improve progressive disclosure.

Trim the introductory Zoho Commerce description and the auth-plumbing commentary, which restate context Claude already knows.

Fix the inconsistent step numbering ("1b.") so the connection sequence reads as a coherent ordered list.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with tight code blocks and a flag table, but the opening Zoho Commerce description and phrases like "so you can focus on the integration logic rather than auth plumbing" explain context Claude largely already knows, fitting the 'mostly efficient but could be tightened' anchor.	3 / 5
Actionability	It provides concrete, executable commands throughout (install, login, connection ensure, action list/run, proxy flags) that are largely copy-paste ready, with only minor gaps such as omitted placeholder substitution examples.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with explicit state handling (READY / CLIENT_ACTION_REQUIRED / error states) and a poll-again feedback loop after user action, though the inconsistent "1b" step numbering is a minor blemish.	4 / 5
Progressive Disclosure	Sections are reasonably organized, but all content lives in a single monolithic file with no external references and no bundle files; material such as the action-discovery and proxy reference that could be split out is inlined, fitting the 'some structure but could be better organized' anchor.	3 / 5
	Total	14 / 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 identifies its niche and includes an explicit use-when clause, but its capability phrasing is generic and trigger coverage is thin. Sharpening the action list and adding natural synonyms would lift specificity and trigger quality.

Suggestions

Replace generic verbs with concrete Zoho Commerce actions, e.g. "create and update products, process orders, manage shipments, and apply coupons".

Add natural trigger synonyms a user might say, such as "online store", "e-commerce orders", or "Zoho Commerce store".

Tighten the when-clause to a specific scenario, e.g. "Use when the user wants to manage products, orders, or customers in a Zoho Commerce store."

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the domain with a couple of actions, but the actions are generic rather than concrete, matching the anchor for 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	It states both the what ("Zoho Commerce integration. Manage data, records, and automate workflows.") and an explicit when ("Use when the user wants to interact with Zoho Commerce data."), though the when is somewhat generic, matching the anchor for both present with room to be more specific.	4 / 5
Trigger Term Quality	"Zoho Commerce" recurs and "interact with Zoho Commerce data" is a relevant phrase, but it lacks common synonyms or variations a user would naturally say, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The description is clearly niched to Zoho Commerce with distinct triggers and minimal risk of firing for an unrelated skill.	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-commerce/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.