Name: zoho-docs
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

zoho-docs

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

Quality

61%

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

Quality

Content

61%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 solid, executable CLI guide with well-organized sections and copy-paste commands, but it lacks validation checkpoints in its workflow and carries minor redundancy and padding. Adding a verify-connection step and removing the duplicated discovery block would improve it.

Suggestions

Add an explicit verification checkpoint after connecting, e.g. 'Verify: `membrane connection list --json` should show the new connectionId before proceeding'.

Remove the duplicated `membrane action list --intent=QUERY` instruction that appears in both 'Searching for actions' and 'Popular actions'; consolidate into one section.

Trim the conceptual opener ('Zoho Docs is a cloud-based document management system...') and the 'rather than auth plumbing' aside to assume Claude's competence and save tokens.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command listings, but the opening 'Zoho Docs is a cloud-based document management system...' explainer, the 'so you can focus on the integration logic rather than auth plumbing' padding, and the duplicated `membrane action list --intent=QUERY` command across two sections could be tightened.	3 / 5
Actionability	Concrete, copy-paste-ready bash commands cover the common cases (install, login, connect, list actions, run actions, proxy) with a clear flags table, but every example uses placeholders (CONNECTION_ID, ACTION_ID, /path/to/endpoint) with no concrete end-to-end example using real values, capping it below 5.	4 / 5
Workflow Clarity	A clear install -> login -> connect -> search -> run sequence exists with a useful 'check existing connections' branch, but validation/verification checkpoints are absent or implicit (no 'verify the connection succeeded' or error-recovery feedback loop), matching the 'sequence present but checkpoints missing' anchor.	3 / 5
Progressive Disclosure	The single-file skill is well-organized into clearly headed sections (Overview, Working with Zoho Docs, Popular actions, Best practices) with no nested references and easy navigation, though it exceeds 50 lines and could optionally split the proxy flags table or action reference into a separate file.	4 / 5
	Total	14 / 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 well-formed with an explicit 'Use when...' trigger and a named product niche, but its action wording is generic rather than concrete. Tightening 'manage data, records, and automate workflows' into specific operations would raise specificity and completeness.

Suggestions

Replace generic actions ('Manage data, records, and automate workflows') with concrete Zoho Docs operations such as 'upload, download, organize, and share files and folders'.

Add natural trigger synonyms users actually say, e.g. 'Use when the user wants to upload or share Zoho Docs files, manage WorkDrive team folders, or automate document workflows'.

Mention Zoho WorkDrive explicitly in the description since it is a distinct sub-product covered in the body.

Dimension	Reasoning	Score
Specificity	Names the domain ('Zoho Docs integration') and lists several actions ('Manage data, records, and automate workflows'), but the actions are generic abstractions rather than concrete operations like 'extract text' or 'fill forms', keeping it below a 4.	3 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Zoho Docs data') are explicitly present, but neither is highly specific or backed by concrete trigger phrases, so it falls short of a 5.	4 / 5
Trigger Term Quality	'Zoho Docs' is a strong natural keyword, and 'data', 'records', 'workflows' add some coverage, but common variations, synonyms, and file extensions are missing, matching the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product 'Zoho Docs' gives it a clear, distinct niche with minimal conflict risk, but the generic action wording ('manage data, records, automate workflows') could overlap with other data-integration skills, preventing a 5.	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-docs/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.