Name: zoho-sign
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

zoho-sign

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

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

67%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 strong, actionable Membrane CLI reference with a genuine validation feedback loop for connection setup, but it is padded with promotional prose, has a redundant actions section, and never grounds its examples in concrete Zoho Sign operations.

Suggestions

Trim the promotional intro ("businesses of all sizes... eliminate the need for paper-based signatures") and the "so you can focus on the integration logic rather than auth plumbing" aside — Claude does not need Zoho Sign's marketing.

Fix the broken step numbering: the text references "Step 2" and a "1b" with no labeled "1a" or "Step 2" section, making the connection flow hard to follow; label steps consistently.

Remove the redundant "Popular actions" section, which restates the `action list` command already shown under "Searching for actions", and ground at least one example in a real Zoho Sign action (e.g. an intent query like "send document for signature" with a sample input).

Dimension	Reasoning	Score
Conciseness	The core is a tight CLI command reference, but it carries unnecessary prose — a promotional intro ("businesses of all sizes... eliminate the need for paper-based signatures"), the "so you can focus on the integration logic rather than auth plumbing" aside, and a redundant "Popular actions" section that restates the earlier command.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands throughout (install, login, connection ensure/get, action list/run, request) with clearly marked placeholders, but examples stay generic to Membrane — no real Zoho Sign action name, intent query, or sample payload/output is shown.	4 / 5
Workflow Clarity	The connection flow has an explicit state-based feedback loop (poll with --wait, handle CLIENT_ACTION_REQUIRED, re-poll until READY), but step numbering is inconsistent — it references "Step 2" and labels a "1b" with no matching "1a" or labeled "Step 2" — and running actions has no output validation.	4 / 5
Progressive Disclosure	A single ~143-line file with clear section headers and no bundle files; content is appropriately organized in one place, with minor gaps from the overlapping "Searching for actions" / "Popular actions" sections.	4 / 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 is distinctive and answers both what and when, but its action language is generic and it omits the natural trigger terms (documents, signatures, templates) a user would actually say for a digital-signature app.

Suggestions

Replace the generic verbs with concrete Zoho Sign actions, e.g. "send documents for signature, request signatures from recipients, and manage templates and signed records."

Add natural trigger terms users say for an e-signature app — "signatures", "documents", "e-sign", "templates", "signed records" — alongside "data" and "records".

Tighten the "when" clause to reference concrete intents (e.g. "Use when the user wants to send or sign documents, manage templates, or track signature status in Zoho Sign.") instead of the circular "interact with Zoho Sign data".

Dimension	Reasoning	Score
Specificity	Names the domain plus several actions ("Manage data, records, and automate workflows"), but the verbs are generic rather than concrete Zoho Sign actions such as signing/sending documents, managing templates, or requesting signatures.	3 / 5
Completeness	Both a "what" ("Zoho Sign integration. Manage data, records, and automate workflows.") and an explicit "when" ("Use when the user wants to interact with Zoho Sign data.") are present; the "when" is somewhat circular and could be more specific.	4 / 5
Trigger Term Quality	"Zoho Sign" is a strong natural keyword and "Use when the user wants to interact with Zoho Sign data" gives a trigger, but it misses common variations users say for a signature app ("documents", "signatures", "e-sign", "templates").	3 / 5
Distinctiveness Conflict Risk	It names a specific product (Zoho Sign) and ties the trigger to that product, giving it a clear niche with minimal risk of triggering for an unrelated skill.	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-sign/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.