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

zoho-campaigns

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

Quality

74%

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-campaigns/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 executable commands and a clear, checkpointed workflow. Its main gaps are a few verbose passages and an inconsistent step-labeling scheme ('Step 2', '1b') that slightly weakens workflow clarity and conciseness.

Suggestions

Fix the broken step references: either label an explicit 'Step 2' section or reword 'skip to Step 2' to point at a real heading, and rename '1b' to align with a consistent step numbering.

Trim explanatory padding such as 'so you can focus on the integration logic rather than auth plumbing' and condense the Overview bullet tree to keep the body lean.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient — concrete commands with brief context — but includes minor padding like 'so you can focus on the integration logic rather than auth plumbing' and a long Overview tree, fitting 'efficient; minor instances of over-explanation that could be trimmed' rather than the fully lean anchor 5.	4 / 5
Actionability	It provides copy-paste-ready, fully executable commands throughout (install, login, connection ensure, action list/run, request proxy) plus a flag table and JSON parameter example, matching 'fully executable; copy-paste ready code or commands; specific examples cover the common cases'.	5 / 5
Workflow Clarity	The install→auth→connect→poll→search→run sequence is clear with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-again feedback loop, but it references a 'Step 2' that is never labeled and uses a '1b' heading without a '1a', leaving minor sequence gaps that cap it at 4 rather than 5.	4 / 5
Progressive Disclosure	No bundle files exist, so all content is inline, but it is organized into well-labeled sections (Install, Authentication, Connecting, Searching, Popular actions, Best practices) with no nested or broken references; the inlined Overview tree and flag tables are reasonable inline content, fitting 'good structure; most content appropriately placed' rather than the fully split anchor 5.	4 / 5
	Total	17 / 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 answers both what the skill does and when to use it, and naming the specific app keeps it distinctive. Its weakness is generic verb choice and limited natural-language trigger coverage, which cap specificity and trigger quality.

Suggestions

Replace generic verbs with concrete Zoho Campaigns actions, e.g. 'Create and send email/SMS campaigns, manage subscriber lists, and pull campaign reports.'

Expand the trigger clause with natural phrases users say, e.g. 'Use when the user wants to create or send email campaigns, manage subscribers or lists, or review campaign reports in Zoho Campaigns.'

Dimension	Reasoning	Score
Specificity	Phrases like 'Manage data, records, and automate workflows' name the domain and a couple of actions, but the verbs are generic ('manage', 'automate') rather than comprehensive concrete actions, matching the 'names domain and 1-2 concrete actions but not comprehensive' anchor.	3 / 5
Completeness	It states both a clear 'what' ('Zoho Campaigns integration. Manage data, records, and automate workflows.') and an explicit 'when' ('Use when the user wants to interact with Zoho Campaigns data.'), but the 'when' is somewhat generic, matching anchor 4 rather than 5's concrete trigger phrases.	4 / 5
Trigger Term Quality	'Use when the user wants to interact with Zoho Campaigns data' surfaces the app name and 'data', but it omits common natural variations users would say (campaigns, email marketing, subscribers, lists), fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product ('Zoho Campaigns integration', 'interact with Zoho Campaigns data') gives it a clear niche with distinct triggers and minimal conflict risk with other skills, matching anchor 5.	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-campaigns/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.