Name: zoho-creator
Rating: 58.4 (1 reviews)
Author: membranedev

zoho-creator

Zoho Creator integration. Manage Applications, Users, Roles. Use when the user wants to interact with Zoho Creator data.

Quality

67%

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

Quality

Content

68%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 highly actionable with concrete, copy-paste-ready CLI commands and a useful actions table, and it is reasonably well-structured. Its main weaknesses are a padded conceptual intro and the absence of validation/verification guidance for destructive and batch operations, which caps workflow clarity.

Suggestions

Trim the opening paragraph and filler lines (e.g., "When to use which actions: Use action names and parameters as needed.") that explain concepts Claude already knows.

Add explicit validation/verification steps before destructive or batch operations (e.g., confirm record counts or dry-run criteria before delete-records/update-records, and verify bulk-read job status before relying on results).

Consider moving the full actions table and proxy flag reference into a separate reference file, keeping SKILL.md a lean overview that links out.

Dimension	Reasoning	Score
Conciseness	Most of the body is efficient commands and tables, but the opening paragraph explains what Zoho Creator is ("Think of it as a rapid application development tool for citizen developers and IT professionals alike") and lines like "When to use which actions: Use action names and parameters as needed" are unnecessary padding, fitting anchor 3.	3 / 5
Actionability	It provides copy-paste-ready commands throughout (install, login, connection ensure/get with --wait, action list/run with --input, proxy with a full flag table) plus a 16-row actions table, fully covering common cases per anchor 5.	5 / 5
Workflow Clarity	The connection workflow is well-sequenced with state checks and a poll/clientAction feedback loop, but the skill exposes destructive and batch operations (delete-records, update-records, bulk read jobs of 100k-200k records) with no validation/verification steps, which per the rubric caps this dimension at 3.	3 / 5
Progressive Disclosure	The single SKILL.md is well-organized into clear sections with no nested references and an inline actions table that is reasonable for an overview, fitting anchor 4; it does not reach 5 because the catalog and flag tables could be split into separate reference files.	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 clearly identifies a distinct product niche and provides an explicit Use-when trigger, but its action vocabulary is generic ("Manage") and its trigger phrasing lacks synonyms or concrete variations. Strengthening the verb diversity and trigger specificity would lift it from good to excellent.

Suggestions

Replace the generic verb "Manage" with distinct concrete actions (e.g., "Create, update, and delete Applications, Users, and Roles") to improve specificity.

Expand the "Use when" clause with concrete trigger phrases users would say (e.g., "Use when the user mentions Zoho Creator apps, forms, reports, or records").

Add common synonyms or file/record extensions (e.g., forms, reports, records) to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	"Manage Applications, Users, Roles" names the domain plus three concrete entities, but the single generic verb "Manage" does not list multiple distinct concrete actions, matching anchor 3 rather than 4.	3 / 5
Completeness	It explicitly answers both "what" ("Manage Applications, Users, Roles") and "when" ("Use when the user wants to interact with Zoho Creator data."), but the trigger is slightly generic rather than listing concrete trigger phrases, so anchor 4 over 5.	4 / 5
Trigger Term Quality	It surfaces the product name "Zoho Creator" plus entity keywords (Applications, Users, Roles) and the phrase "interact with Zoho Creator data", but lacks common synonyms or variations a user might phrase, fitting anchor 3.	3 / 5
Distinctiveness Conflict Risk	"Zoho Creator integration" names a specific SaaS product with a distinct trigger, giving it a clear niche with minimal overlap risk, 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-creator/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.