Name: zoho-assist
Rating: 61.6 (1 reviews)
Author: membranedev

zoho-assist

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

Quality

72%

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

Quality

Content

82%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 content is highly actionable with copy-paste CLI commands and a clear, checkpoint-driven connection workflow. It is held back only by minor verbosity, a dangling 'Step 2' reference, and no explicit action-result verification.

Suggestions

Resolve the dangling 'Skip to Step 2' reference by labeling the 'Searching for actions' section as 'Step 2' or rewording the jump.

Add a brief verification step after running actions (e.g. check the `output` field and handle non-zero/error states) to close the workflow feedback loop for potentially destructive or batch operations.

Trim conversational filler such as 'so you can focus on the integration logic rather than auth plumbing' to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient — dominated by copy-paste commands and a compact flags table — with only minor padding such as 'so you can focus on the integration logic rather than auth plumbing' and 'This is the fastest way to get a connection', fitting 'efficient; minor instances of over-explanation that could be trimmed'.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands covering the common cases (install, login, connection ensure/get with --wait, action list/run, request proxy) plus a concrete flags table, matching 'fully executable; copy-paste ready commands; specific examples cover the common cases'.	5 / 5
Workflow Clarity	The connection setup has a clear sequence with explicit state-based checkpoints and a re-poll feedback loop (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but 'Skip to Step 2' references a Step 2 that is never labeled, and running actions lacks an explicit result-verification step, keeping it at 'clear sequence with most checkpoints; minor validation gaps'.	4 / 5
Progressive Disclosure	The skill is a single well-organized file with clear section headers and no nested references, but at ~140 lines it inlines reference-like material (the proxy flags table and the clientAction schema) that could live in a separate file, placing it at 'good structure; most content appropriately placed; minor organization gaps' rather than a 5.	4 / 5
	Total	17 / 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 correctly answers both what and when and is anchored to a specific product, giving it solid distinctiveness. Its main weakness is generic, non-concrete action language and limited natural trigger-term coverage.

Suggestions

Replace generic verbs with concrete Zoho Assist capabilities, e.g. 'Start and join remote support sessions, manage unattended computers, and schedule sessions'.

Expand the 'Use when...' clause with natural trigger phrases users actually say, such as 'remote support', 'unattended access', 'screen sharing', or 'manage technician sessions'.

Add file-extension or product-specific tokens (e.g. '.zoho', 'Zoho Assist sessions') to strengthen trigger-term distinctiveness.

Dimension	Reasoning	Score
Specificity	Names the domain (Zoho Assist) plus a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete like 'extract text' or 'fill forms', fitting the '1-2 concrete actions but not comprehensive' anchor.	3 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Zoho Assist data') are present, but the 'when' clause is generic rather than packed with concrete trigger phrases, so it sits at 'both present, when could be more specific' rather than a 5.	4 / 5
Trigger Term Quality	'Zoho Assist' and 'interact with Zoho Assist data' are relevant keywords, but common natural variations users would say (sessions, computers, remote support, technicians) are missing, matching 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product 'Zoho Assist' in both the what and when clauses gives it a clear niche with low conflict risk, but the generic action phrasing ('manage data, records, automate workflows') keeps it just short of the minimal-conflict 5 anchor.	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-assist/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.