Name: zoho-invoice
Rating: 55.2 (1 reviews)
Author: membranedev

zoho-invoice

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

Quality

63%

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

Quality

Content

68%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 a well-structured, command-rich guide with strong connection-state checkpoints, but it trims poorly on a few explanatory sentences and — critically — offers no validation or verification guidance before destructive action/proxy operations, which caps workflow clarity. Filling the placeholder-based commands with a worked example and adding a verify-before-destructive step would raise the two capped dimensions.

Suggestions

Add a validation/verification checkpoint before destructive calls: e.g. recommend a dry-run GET or a confirmation prompt before running mutating actions or proxy POST/PUT/DELETE requests, to lift workflow_clarity above the destructive-operations cap.

Include one fully-worked end-to-end example with concrete values (a real connection id and action) so the command patterns are unambiguously executable, improving actionability.

Trim the introductory paragraph defining Zoho Invoice and the 'so you can focus on the integration logic' filler to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is heavily command-driven and mostly efficient, with sectioned commands and a compact flag table. It is not a 5 because the opening paragraph explaining what Zoho Invoice is and a few explanatory sentences (e.g. 'so you can focus on the integration logic rather than auth plumbing') are padding Claude does not need, and not a 3 because the overall tone is efficient rather than noticeably verbose.	4 / 5
Actionability	It provides concrete, copy-paste-ready commands for install, login, connection ensure, action list/run, and proxy requests, plus a clear flag table. It is not a 5 because commands rely on unfilled placeholders (CONNECTION_ID, actionId) with no fully-worked end-to-end example showing instantiated values covering a common case.	4 / 5
Workflow Clarity	The connection flow has a clear sequence with state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-after-action feedback loop, but the action-running and proxy sections expose destructive operations (arbitrary POST/PUT/DELETE) with no validation or verify-before-execute guidance, triggering the destructive-operations cap of 3. It is not a 4 because that missing validation gap is material rather than minor.	3 / 5
Progressive Disclosure	The single SKILL.md is well organized into clearly headed sections (overview, install, auth, connecting, searching, running, proxy, best practices) with no bundle files needed for a CLI workflow. It is not a 5 because, at ~155 lines, the inline entity list and API overview sit in the main file rather than being split out, leaving minor organization gaps.	4 / 5
	Total	15 / 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 correctly includes both a 'what' and an explicit 'Use when...' trigger and is anchored to a distinct product, but its action language and trigger terms are generic rather than concrete. Tightening the verbs and adding natural synonyms (invoice, estimate, billing, customer) would lift the specificity and trigger-term dimensions.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete Zoho Invoice actions such as creating/sending invoices, estimates, credit notes, and tracking expenses.

Expand the 'Use when...' clause with natural trigger phrases users actually say, e.g. 'Use when the user wants to create or send invoices, estimates, or credit notes, or track expenses in Zoho Invoice.'

Add a few domain synonyms (billing, customers, payments) to broaden natural keyword coverage without adding fluff.

Dimension	Reasoning	Score
Specificity	The description names the domain (Zoho Invoice) but its actions — "Manage data, records, and automate workflows" — are generic rather than concrete, matching the anchor where actions are minimal or generic. It is not a 3 because none of the listed actions are specific (e.g. create invoices, send estimates) as required for that level.	2 / 5
Completeness	Both halves are present: "Zoho Invoice integration. Manage data, records, and automate workflows" states what it does, and "Use when the user wants to interact with Zoho Invoice data" states when. It is not a 5 because the 'when' clause is generic rather than packed with concrete trigger phrases, and not a 3 because both what and when are explicitly stated.	4 / 5
Trigger Term Quality	"Zoho Invoice" is a relevant natural keyword and "data", "records", "automate workflows" give some coverage, but common natural variations users would actually say (invoice, estimate, billing, customer, expense) are missing. It is not a 4 because the trigger language is thin on the natural synonyms a 4-level example would include.	3 / 5
Distinctiveness Conflict Risk	Tying the skill to the named product "Zoho Invoice" gives it a clear, mostly-distinct niche with minimal conflict risk. It is not a 5 because the single generic trigger ("interact with Zoho Invoice data") could still overlap with sibling Zoho or general invoicing skills, and lacks the rich distinct triggers of the 5 anchor.	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-invoice/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.