CtrlK
BlogDocsLog inGet started
Tessl Logo

zoho-sheet

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

60

Quality

70%

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-sheet/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 copy-paste-ready CLI commands, a clear connect-then-act workflow with state-based checkpoints, and clean section structure. Its main weakness is an unnecessary introductory paragraph explaining what Zoho Sheet is, plus a dangling "Step 2" reference and no validation of action results.

Suggestions

Delete the opening conceptual paragraph ("Zoho Sheet is an online spreadsheet application, similar to Google Sheets...") since Claude already knows this; lead directly with the integration workflow.

Fix the dangling "Skip to Step 2" / "1b" numbering by labeling an explicit Step 2 section so the cross-references resolve.

Add a brief validation/verification step after running actions or proxy requests (e.g. check the `output`/error fields before proceeding), since proxy requests include destructive methods like DELETE.

DimensionReasoningScore

Conciseness

The body is mostly efficient commands, but opens with unnecessary conceptual padding Claude already knows ("Zoho Sheet is an online spreadsheet application, similar to Google Sheets or Microsoft Excel. It's used by businesses and individuals to create, edit, and collaborate...") plus lines like "so you can focus on the integration logic rather than auth plumbing", matching score 3 of mostly efficient with some unnecessary explanation; it is not 4 because the introductory paragraph is clearly trimmable, and not 2 because the bulk is concrete and unpadded.

3 / 5

Actionability

The content is fully executable with copy-paste-ready commands throughout (install, login, connection ensure, action list/run with --input JSON, proxy requests) and a complete flag table for proxy requests, matching score 5; it is not 4 because specific examples cover the common cases with real flags rather than minor gaps.

5 / 5

Workflow Clarity

There is a clear sequence (install CLI -> authenticate -> ensure connection -> poll until READY -> search actions -> run/proxy) with explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a feedback loop (poll again after the user completes the action), matching score 4; it is not 5 because references to an unlabeled "Step 2" and absent output-validation for run/proxy results leave minor gaps, and not 3 because checkpoints and an error-recovery loop are present.

4 / 5

Progressive Disclosure

The body is well-organized into clear sections (Overview, Working with Zoho Sheet, Searching for actions, Popular actions, Best practices) with no nested references and no bundle files, matching score 4 of good structure with minor organization gaps; it is not 5 because the ~140-line body is fully inline with no one-level-deep references to offload reference material, and not 3 because sectioning is clean and navigable rather than poorly organized.

4 / 5

Total

16

/

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 an explicit Use-when clause and a clearly distinct product niche, but its action verbs are generic and it lacks natural synonyms like "spreadsheets" or "sheets" that users would actually say. Strengthening trigger term coverage and listing more concrete operations would raise it.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete operations such as create/edit worksheets, read/write cell ranges, add/update records, and trigger workflows.

Add natural synonyms and file extensions users would say, e.g. "spreadsheets", "sheets", ".xlsx", alongside "Zoho Sheet".

Make the Use-when clause more specific, e.g. "Use when the user wants to read, edit, or automate Zoho Sheet spreadsheets or tabular data."

DimensionReasoningScore

Specificity

The description names the domain ("Zoho Sheet integration") and a few actions ("Manage data, records, and automate workflows"), but those verbs are generic rather than concrete, matching the score-3 anchor of domain plus 1-2 non-comprehensive actions; it is not score 2 because it does list multiple actions, and not score 4 because none are specific operations like create/edit/import.

3 / 5

Completeness

Both a clear "what" ("Zoho Sheet integration. Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Zoho Sheet data") are present, matching score 4 where both exist but the "when" could be more specific; it is not 3 because "when" is explicit rather than missing, and not 5 because the trigger phrasing is generic rather than concrete trigger phrases.

4 / 5

Trigger Term Quality

Relevant terms ("Zoho Sheet", "data", "records", "workflows") appear, but common synonyms users would naturally say ("spreadsheets", "sheets", ".xlsx") are missing, matching the score-3 anchor of some keywords lacking common variations; it is not 2 because more than generic jargon is present, and not 4 because natural synonyms are absent.

3 / 5

Distinctiveness Conflict Risk

"Zoho Sheet integration" carves a clear, product-specific niche with distinct triggers and minimal conflict risk with other skills, matching the score-5 anchor; it is not 4 because the named product is specific enough to avoid meaningful overlap with related skills.

5 / 5

Total

15

/

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.