CtrlK
BlogDocsLog inGet started
Tessl Logo

zoho-survey

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

52

Quality

59%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/zoho-survey/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 action-oriented and well-structured with executable membrane CLI examples and a solid connection-readiness state machine, but it carries some unnecessary explanatory padding and leaves the action-execution workflow without validation checkpoints. Fixing the dangling "Step 2" reference and trimming the product overview would improve it.

Suggestions

Remove or shrink the opening paragraph defining Zoho Survey; Claude does not need a market overview to use the CLI.

Label the post-connection steps explicitly (e.g. "## Step 2: Discover and run actions") so the "skip to Step 2" reference resolves.

Add a verification checkpoint after running actions or proxy requests, e.g. checking the response status/error field before reporting success to the user.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete CLI commands, but the opening paragraph explaining what Zoho Survey is and phrases like "so you can focus on the integration logic rather than auth plumbing" add unnecessary padding Claude does not need.

3 / 5

Actionability

It provides many copy-paste-ready membrane commands with flags (login, connection ensure, action list/run, request), with minor gaps such as the literal --intent "QUERY" placeholder and a thin Popular actions section.

4 / 5

Workflow Clarity

The connection state machine (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) provides real checkpoints, but the action-execution workflow lacks any verification step and "skip to Step 2" references a step that is never labeled.

3 / 5

Progressive Disclosure

Content is organized into clear, well-labeled sections with no external bundle files required; the proxy options table and connection state handling are reasonably placed inline with only minor organization gaps.

4 / 5

Total

14

/

20

Passed

Description

57%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 covers both what the skill does and when to use it and is anchored to a distinct product niche, but its capability list is generic and it lacks richer trigger-term synonyms. Tightening the action verbs and adding natural terms like "surveys" or "questionnaires" would raise it.

Suggestions

Replace generic verbs with concrete Zoho Survey actions, e.g. "create and distribute surveys, collect responses, and generate reports".

Add natural trigger terms and synonyms such as "surveys", "polls", "questionnaires", or "feedback" alongside "Zoho Survey data".

Make the "Use when" clause more specific, e.g. "Use when the user wants to create surveys, gather responses, or analyze Zoho Survey results."

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the Zoho Survey domain but the actions are generic and abstract rather than concrete (no mention of creating surveys, collecting responses, or generating reports).

2 / 5

Completeness

Both a what ("Manage data, records, and automate workflows") and a when ("Use when the user wants to interact with Zoho Survey data") are present, but the when clause is somewhat generic.

4 / 5

Trigger Term Quality

"Zoho Survey" and "survey data" are relevant keywords, but common variations and synonyms (surveys, polls, questionnaires, feedback) are missing.

3 / 5

Distinctiveness Conflict Risk

Naming the specific Zoho Survey product gives a clear niche with minimal conflict risk, though the generic data/records/workflow phrasing could overlap with other Zoho or CRM-style skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.