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

zoho-projects

Zoho Projects integration. Manage data, records, and automate workflows. Use when the user wants to interact with Zoho Projects 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/zoho-projects/SKILL.md

Quality

Content

71%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 delivers highly actionable, well-sequenced CLI guidance with genuine polling/retry feedback loops, but it is a single inline document with no progressive disclosure and a couple of trimmable explanatory/marketing lines.

Suggestions

Fix the incoherent step references: replace the dangling "Step 2" mentions and lone "1b" header with a coherent numbered sequence (e.g. Step 1 connect, Step 2 search actions, Step 3 run).

Populate the "Popular actions" section with actual common action names/examples or move the action catalog to a referenced file (e.g. ACTIONS.md) to add progressive disclosure.

Trim concept explanations Claude already knows, such as the opening "Zoho Projects is a project management application..." paragraph and the Membrane marketing phrasing.

Dimension	Reasoning	Score
Conciseness	The body is largely lean with executable CLI commands, but a few lines over-explain concepts Claude already knows (the Zoho Projects intro paragraph and Membrane marketing prose like "so you can focus on the integration logic rather than auth plumbing"), keeping it at 4 rather than 5.	4 / 5
Actionability	Concrete, copy-paste-ready `membrane` commands with flags are provided throughout (login, connection ensure, action list/run, request) along with a proxy flag table, but placeholder substitution (CONNECTION_ID, <actionId>) and an empty "Popular actions" section leave minor gaps versus 5.	4 / 5
Workflow Clarity	A clear sequence (install, auth, ensure connection, poll until READY, handle clientAction states, search then run/proxy) with explicit polling and retry feedback loops is present; the only gap is incoherent step labeling ("Step 2" and "1b" referenced with no Step 1 or Step 2 headers), which is minor enough to stay at 4.	4 / 5
Progressive Disclosure	No bundle files exist and all ~145 lines live inline in SKILL.md with no file references or layering; while sections are well-organized, content that could be externalized (a full action catalog, expanded best practices) is inlined, matching the 3 anchor.	3 / 5
	Total	15 / 20 Passed

Description

66%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 cleanly names a specific app and includes an explicit "Use when" trigger, but its capability list is generic and its trigger terms lack the synonyms and concrete phrases that would make it comprehensive.

Suggestions

Replace "Manage data, records, and automate workflows" with concrete actions, e.g. "Create and manage projects, tasks, tasklists, milestones, and bugs, and run automation workflows."

Broaden the trigger with natural synonyms, e.g. "Use when the user wants to manage Zoho Projects, tasks, tasklists, milestones, or bugs."

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the domain and a couple of actions, but the actions are generic ("manage data, records") rather than concrete operations like creating tasks or listing projects, so it sits at the 3 anchor rather than 4.	3 / 5
Completeness	Both a "what" (Zoho Projects integration, manage data/records, automate workflows) and an explicit "when" ("Use when the user wants to interact with Zoho Projects data") are present, but the trigger is somewhat generic rather than concrete, fitting 4 better than 5.	4 / 5
Trigger Term Quality	The trigger "Use when the user wants to interact with Zoho Projects data" includes the natural keyword "Zoho Projects," but lacks common variations or synonyms users would say (e.g. "Zoho tasks," "manage projects in Zoho"), matching the 3 anchor.	3 / 5
Distinctiveness Conflict Risk	"Zoho Projects" is a specific named application with a distinct trigger tied to that app, giving a clear niche and minimal conflict risk, matching the 5 anchor.	5 / 5
	Total	15 / 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-projects/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.