Name: zoho-inventory
Rating: 58.4 (1 reviews)
Author: membranedev

zoho-inventory

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

Quality

68%

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-inventory/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 body is highly actionable with concrete, executable Membrane CLI commands and a well-structured connection workflow that includes state polling and error handling. Its main weaknesses are conciseness padding and a couple of workflow gaps (an undefined 'Step 2' and no validation before destructive operations).

Suggestions

Trim padding Claude does not need: drop the 'who uses Zoho Inventory' sentence and marketing phrases ('focus on integration logic rather than auth plumbing', 'burn less tokens').

Label the 'Searching for actions' section as 'Step 2' (or remove the dangling 'skip to Step 2' references) so the connection-to-action workflow is unambiguous.

Add a validation/confirmation step before destructive action runs or proxy POST/PUT/DELETE calls (e.g., confirm the target record or dry-run where supported) to satisfy the destructive-operations workflow guidance.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete commands, but includes unnecessary padding Claude does not need ('It's typically used by small to medium-sized businesses in retail, manufacturing, and e-commerce') and marketing phrasing ('so you can focus on the integration logic rather than auth plumbing', 'burn less tokens'), placing it at 'mostly efficient but includes some unnecessary explanation that could be tightened'.	3 / 5
Actionability	It provides copy-paste-ready, executable commands across install, login, connection ensure, polling, action list/run, and proxy, plus a flag table for proxy options, covering the common cases the way the 5 anchor asks.	5 / 5
Workflow Clarity	The connection workflow has an explicit state-machine with validation checkpoints and feedback loops (poll until READY, handle CLIENT_ACTION_REQUIRED, re-poll, inspect error on CONFIGURATION_ERROR), but it references an unlabeled 'Step 2' and offers no pre-flight validation for potentially destructive action runs or proxy DELETE/POST calls, matching 'clear sequence with most checkpoints, minor validation gaps'.	4 / 5
Progressive Disclosure	No bundle files exist and the content is a single well-sectioned file (~155 lines) with clear headers; because it exceeds the 50-line auto-5 threshold and has no one-level-deep reference files to navigate, it sits at 'good structure, most content appropriately placed, minor organization gaps' rather than 5.	4 / 5
	Total	16 / 20 Passed

Description

61%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 is clearly scoped to Zoho Inventory and includes an explicit 'Use when' trigger, but it relies on generic verbs ('manage data, records, automate workflows') and repeats the app name rather than listing concrete actions or natural task-level keywords. It is distinct but lacks specificity and trigger richness.

Suggestions

Replace generic verbs with concrete Zoho Inventory operations, e.g. 'Create and track items, manage purchase and sales orders, adjust stock levels, and handle shipments'.

Add natural trigger keywords users actually say, such as 'stock', 'inventory', 'orders', 'purchase orders', or 'warehouse', alongside the app name.

Tighten the 'Use when' clause to name concrete scenarios, e.g. 'Use when the user wants to manage stock, create or fulfill orders, or adjust inventory in Zoho Inventory.'

Dimension	Reasoning	Score
Specificity	It names the domain ('Zoho Inventory integration') but the actions ('Manage data, records, and automate workflows') are generic abstractions rather than concrete operations like create/track/adjust, so it sits at the 'names domain, actions minimal or generic' anchor rather than the 3 which requires 1-2 concrete actions.	2 / 5
Completeness	Both halves are present: a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Zoho Inventory data'), but the 'what' is generic and the 'when' is a single broad phrase rather than concrete trigger phrases, matching the 'has both, when could be more specific' anchor.	4 / 5
Trigger Term Quality	The only natural keyword is the app name 'Zoho Inventory', and the trigger restates it ('interact with Zoho Inventory data'); it omits common task-level synonyms users would say such as stock, orders, purchase orders, or inventory management, so it lands at 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	Tying the skill to a specific named commercial app ('Zoho Inventory') with an app-scoped trigger gives it a clear niche with distinct triggers and minimal overlap with other skills, matching the 'clear niche, minimal conflict risk' anchor.	5 / 5
	Total	14 / 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-inventory/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.