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

zoho-workdrive

Zoho WorkDrive integration. Manage data, records, and automate workflows. Use when the user wants to interact with Zoho WorkDrive 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-workdrive/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 body is a well-structured, actionable guide to driving Zoho WorkDrive through the Membrane CLI, with strong command examples and a clear connection workflow. It loses points for a padded marketing intro, lack of WorkDrive-specific worked examples, missing pre-execution validation, and no progressive disclosure to separate reference files.

Suggestions

Remove the opening marketing paragraph describing what Zoho WorkDrive is; assume Claude knows the product and lead directly with the CLI workflow.

Add at least one concrete WorkDrive worked example (e.g. 'membrane action list --intent \"list files in a Team Folder\"' followed by running the matched action with real input).

Add a validation/check step before running destructive or batch actions (e.g. confirm with the user or run a dry-run/list before a DELETE), and consider moving the proxy flag reference and clientAction state detail into separate reference files.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete CLI commands, but it opens with a marketing-style paragraph explaining what Zoho WorkDrive is ('a secure file management and collaboration platform... used by organizations of all sizes looking to streamline document management') and a few asides that Claude does not need and could be trimmed.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands for install, login, connection setup, action search/run, and proxy requests with a full flags table; the gap is that no WorkDrive-specific worked example (e.g. listing files in a Team Folder) is shown — the action examples stay generic with <actionId> placeholders.	4 / 5
Workflow Clarity	The connection workflow has a clear state-driven sequence with explicit validation via polling (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR branches and a re-poll feedback loop), but action and proxy execution lack any pre-flight validation for potentially destructive operations (e.g. DELETE).	4 / 5
Progressive Disclosure	No bundle files exist and everything is inlined in a single ~150-line SKILL.md with good section headers; at over 50 lines with no external references, content that could live in separate files (the detailed clientAction state machine, the proxy flag reference, best practices) is inlined rather than split out.	3 / 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 functional: it names the product, lists a few action areas, and includes an explicit 'Use when' trigger. Its main weakness is generic, non-concrete action language and a thin set of trigger synonyms.

Suggestions

Replace generic actions with concrete WorkDrive operations, e.g. 'upload and share files, manage Team Folders, create and assign tasks, and generate share links'.

Expand the 'Use when' clause with natural triggers users actually say: 'Use when the user wants to manage files or folders, share documents, or automate workflows in Zoho WorkDrive'.

Add file-type and object synonyms (files, folders, documents, Team Folders, share links) to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Zoho WorkDrive integration') and a few action areas ('Manage data, records, and automate workflows'), but the actions are generic categories rather than concrete operations like uploading files, sharing folders, or creating tasks, so it is not comprehensive.	3 / 5
Completeness	It states both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Zoho WorkDrive data'), but the 'when' clause is generic and could name concrete triggers like files, folders, or sharing.	4 / 5
Trigger Term Quality	The product name 'Zoho WorkDrive' is a strong natural trigger, but the description omits common variations and synonyms users would say such as files, folders, documents, Team Folders, or share links.	3 / 5
Distinctiveness Conflict Risk	Naming the specific SaaS product 'Zoho WorkDrive' gives it a clear niche with minimal conflict risk, though the generic action phrasing ('manage data, automate workflows') could in principle overlap with other data-integration 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-workdrive/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.