Name: zoho-expense
Rating: 59.2 (1 reviews)
Author: membranedev

zoho-expense

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

Quality

69%

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

Quality

Content

76%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 skill body is highly actionable with executable commands and a solid connection-state workflow, and it is well-structured for a single-file integration guide. The main gap is missing validation guidance around destructive proxy/action operations and a couple of minor structural redundancies.

Suggestions

Add a validation checkpoint before destructive proxy or action calls (e.g. confirm or dry-run DELETE/PUT requests and verify the response status before proceeding).

Fix the step numbering so the referenced "Step 2" maps to an actual header, or relabel the connection subsections consistently.

Merge or differentiate "Searching for actions" and "Popular actions", which both demonstrate `membrane action list`, to remove redundancy.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean commands and a flag table with only minor over-explanation (the "what is Zoho Expense" sentence and "so you can focus on the integration logic" aside), fitting the efficient-with-minor-trim anchor.	4 / 5
Actionability	It provides copy-paste-ready commands for the common cases (install, login, connection ensure, action list/run, proxy) with appropriate placeholders, matching the fully-executable anchor.	5 / 5
Workflow Clarity	The connection flow has a clear state-based feedback loop (poll until READY, handle CLIENT_ACTION_REQUIRED), but the proxy section exposes destructive methods (DELETE, PUT) with no validation checkpoint, and "Step 2" is referenced without a matching header, so the destructive-ops cap applies.	3 / 5
Progressive Disclosure	Content is well-organized into clear sections with no nested references and appropriately kept in one file, with only minor organization gaps such as redundancy between "Searching for actions" and "Popular actions".	4 / 5
	Total	16 / 20 Passed

Description

62%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 adequately specific and distinct thanks to the named app, with an explicit Use-when clause covering both what and when. Its main weakness is generic action language and missing natural expense-domain trigger phrases.

Suggestions

Replace generic verbs with concrete Zoho Expense actions, e.g. "submit and approve expense reports, track reimbursements, manage expenses and projects".

Expand the Use-when clause with natural trigger phrases users actually say, e.g. "Use when the user wants to submit or approve expense reports, track reimbursements, or manage expenses in Zoho Expense."

Drop vague filler like "Manage data, records" in favor of domain-specific terminology to reduce overlap with other Zoho app skills.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Zoho Expense domain plus a few actions, but the actions are generic rather than concrete, fitting the anchor that lists 1-2 actions without comprehensive coverage.	3 / 5
Completeness	It states both a what ("Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with Zoho Expense data"), but the when is generic rather than offering concrete trigger phrases, so it sits below the top anchor.	4 / 5
Trigger Term Quality	"Zoho Expense" is a strong specific trigger term, but common task-level natural phrases users would say (expense reports, approvals, reimbursements) are missing, matching the anchor with relevant keywords but missing common variations.	3 / 5
Distinctiveness Conflict Risk	The named app "Zoho Expense" gives a clear niche with minimal conflict risk, though the generic "manage data, records" wording leaves minor overlap risk with closely related sibling Zoho skills.	4 / 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-expense/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.