Name: zoho-desk
Rating: 62.4 (1 reviews)
Author: membranedev

zoho-desk

Zoho Desk integration. Manage Tickets, Contacts, Accounts, Agents, Departments, Articles and more. Use when the user wants to interact with Zoho Desk data.

Quality

73%

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-desk/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 highly actionable with concrete, copy-paste-ready CLI commands and a well-structured layout. It loses points on conciseness (intro padding) and workflow clarity (unlabeled step references and missing validation for destructive Create/Update operations).

Suggestions

Trim the introductory paragraph explaining what Zoho Desk is and remove filler lines like 'Use action names and parameters as needed.' to tighten token usage.

Add an explicit verification/check step after Create and Update actions (e.g., re-fetch the record or check the response status) to satisfy the destructive-operation validation expectation.

Relabel the connection flow with explicit Step 1 / Step 2 headings so the 'skip to Step 2' references resolve cleanly.

Dimension	Reasoning	Score
Conciseness	Most content is lean executable commands, but the opening paragraph explaining what Zoho Desk is, the line 'Use action names and parameters as needed.', and phrases like 'so you can focus on the integration logic rather than auth plumbing' are unnecessary padding Claude does not need.	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request) with flags documented in tables and concrete JSON-input examples covering the common cases.	5 / 5
Workflow Clarity	The connection setup has a clear sequence with explicit state polling and feedback (READY/BUILDING/CLIENT_ACTION_REQUIRED), but 'skip to Step 2' is referenced without a clearly labeled Step 1/Step 2, and destructive Create/Update operations lack any validation or verification checkpoint, capping the score at 3.	3 / 5
Progressive Disclosure	Well-organized into clear navigable sections (Install, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) with no nested references and appropriately inline CLI material; minor gaps include the sparse, somewhat redundant 'Zoho Desk Overview' section and a bulky inline actions table.	4 / 5
	Total	15 / 20 Passed

Description

78%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 specific, distinctive, and answers both what the skill does and when to use it with natural trigger terms. It could be elevated by replacing the generic verb 'Manage' with distinct concrete actions and adding richer trigger synonyms.

Suggestions

Replace the single generic verb 'Manage' with distinct concrete actions (e.g., 'Create, update, and retrieve Tickets, Contacts, Accounts...') to reach full specificity.

Add richer trigger synonyms in the 'Use when' clause (e.g., 'when the user mentions support tickets, customer contacts, or Zoho Desk records').

Dimension	Reasoning	Score
Specificity	Lists several specific objects to 'Manage' (Tickets, Contacts, Accounts, Agents, Departments, Articles) but relies on a single generic verb 'Manage' rather than distinct concrete actions, leaving minor coverage gaps versus the comprehensive anchor.	4 / 5
Completeness	Answers both 'what' (manage Tickets/Contacts/etc.) and 'when' ('Use when the user wants to interact with Zoho Desk data'); the 'when' is explicit but a single generic trigger rather than multiple concrete trigger phrases, so it sits below the 5 anchor.	4 / 5
Trigger Term Quality	Includes natural object names a user would say (Tickets, Contacts, Accounts, Agents, Departments, Articles) plus 'Zoho Desk data', but lacks synonyms or related phrasings like 'support tickets' or 'customer service', so coverage is good rather than comprehensive.	4 / 5
Distinctiveness Conflict Risk	Names the specific product 'Zoho Desk' and its named data objects, giving it a clear niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	17 / 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-desk/SKILL.md
Commit: f484c82

Reviewed: ~23 hours 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.