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

zoho-analytics

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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/zoho-analytics/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 integration guide with concrete CLI commands, a clear state-driven connection workflow, and clean section organization. Its main weaknesses are explanatory padding in the intro, an undefined 'Step 2' reference, and a 'Popular actions' section that does not actually list popular actions.

Suggestions

Trim the opening paragraph that defines Zoho Analytics and its audience, and remove 'so you can focus on the integration logic rather than auth plumbing' padding to tighten conciseness.

Resolve the dangling 'Step 2' reference (e.g. relabel 'Searching for actions' as Step 2, or remove the skip-to-Step-2 phrasing) so the connection workflow sequence is unambiguous.

Either populate 'Popular actions' with the actual common actions (e.g. list workspaces, query table, create report) or remove the section to avoid the duplicated discovery command.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete command blocks, but opens by explaining what Zoho Analytics is and who uses it ('business intelligence and data analytics platform... used by business analysts and decision-makers'), and includes prose like 'so you can focus on the integration logic rather than auth plumbing' that Claude does not need. Not score 4 because several sentences are removable padding; not score 2 because the bulk is actionable commands.	3 / 5
Actionability	Provides concrete, copy-paste-ready commands for install, login, connection ensure, action list/run, and proxy, plus a flag table. Not score 5 because the 'Popular actions' section merely repeats the discovery command without listing any actual popular actions, leaving a gap in the common cases.	4 / 5
Workflow Clarity	The connection flow is a clear state-driven sequence with explicit checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-again feedback loop after user action. Not score 5 because the text references 'Step 2' which is never defined, breaking the sequence; not score 3 because validation checkpoints and the retry loop are present.	4 / 5
Progressive Disclosure	Well-organized into clear sections (Overview, Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no nested or buried references and no bundle files to navigate. Not score 5 because at ~145 lines it is monolithic with all content inline (e.g. the proxy flag table and best practices could live in referenced files); not score 3 because structure is clean and navigable.	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 well-formed with both a 'what' and an explicit 'Use when' trigger tied to a specific named product, keeping conflict risk low. Its weakness is generic action verbs and thin trigger-term coverage that omit the concrete entities (reports, dashboards, workspaces) users actually mention.

Suggestions

Replace generic verbs with concrete operations, e.g. 'Create reports and dashboards, query workspace tables, manage records, and automate workflows.'

Expand the trigger clause with the terms users actually say: 'Use when the user wants to work with Zoho Analytics reports, dashboards, workspaces, tables, or data.'

Consider noting .csv/data-source imports or specific Zoho Analytics objects to raise specificity and trigger coverage.

Dimension	Reasoning	Score
Specificity	It names the domain ('Zoho Analytics integration') and lists a few actions ('Manage data, records, and automate workflows'), but the verbs are generic ('manage', 'automate') rather than concrete operations. Not score 2 because multiple action areas are named; not score 4 because none are specific (e.g. no mention of reports, dashboards, tables, workspaces).	3 / 5
Completeness	Answers both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Zoho Analytics data') with an explicit trigger clause. Not score 5 because the 'when' is generic ('interact with data') rather than listing concrete trigger phrases; not score 3 because the Use-when clause is explicit.	4 / 5
Trigger Term Quality	Includes the natural keyword 'Zoho Analytics' and 'data' in the trigger 'Use when the user wants to interact with Zoho Analytics data', but misses common variations/synonyms users would say (reports, dashboards, workspaces, spreadsheets). Not score 4 because the natural-term coverage is thin beyond the product name.	3 / 5
Distinctiveness Conflict Risk	Names a specific product ('Zoho Analytics') with a distinct trigger, giving it a clear niche and minimal conflict risk with other skills. Matches the score-5 anchor of a clear niche with distinct triggers.	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-analytics/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.