CtrlK
BlogDocsLog inGet started
Tessl Logo

zoho-books

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

54

Quality

61%

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

Quality

Content

57%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 actionable and has a genuinely well-sequenced connection state machine, but it is padded by a non-actionable entity list and an introductory overview Claude largely already knows, and it lacks validation steps for destructive accounting operations. No reference files are provided despite content that would benefit from being split out.

Suggestions

Add explicit validation/verification steps before and after destructive or batch accounting operations (e.g. confirm an invoice was created by re-fetching it, dry-run before posting journal entries).

Cut the opening "Zoho Books is a cloud-based accounting software..." paragraph and the marketing phrasing; assume Claude knows what Zoho Books is.

Move the 40-line entity list into a separate reference file (e.g. references/entities.md) and link to it, or replace it with a short note that action discovery is via `membrane action list`.

DimensionReasoningScore

Conciseness

Mostly efficient command examples and a flag table, but the introductory "what is Zoho Books" paragraph, light marketing phrasing, and the 40-line flat entity list add unnecessary bulk.

3 / 5

Actionability

Provides concrete, copy-paste-ready CLI commands (install, login, connection ensure, action run) and a flag table, with only minor gaps (placeholders and the non-actionable entity list).

4 / 5

Workflow Clarity

Connection setup is well sequenced with a state-machine feedback loop, but destructive/batch-capable financial operations (invoices, bills, journal entries) run with no validation checkpoints, which caps workflow clarity at 3.

3 / 5

Progressive Disclosure

Sections are reasonably organized, but no bundle files exist and the 40-line entity list is inlined bulk that should live in a separate reference; for a 175-line non-simple skill this is not well split.

3 / 5

Total

13

/

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 third-person, answers both what and when, and is clearly scoped to a distinct product niche. Its main weakness is generic action wording and limited trigger-term breadth, which keep specificity and trigger quality at the midpoint.

Suggestions

Replace generic verbs with concrete Zoho Books actions, e.g. "Create and send invoices, record expenses, reconcile transactions, manage contacts and bills".

Broaden the when-clause with natural trigger phrases users actually say, e.g. "Use when the user wants to create invoices, track expenses, manage bills, or work with Zoho Books accounting data".

Keep the explicit third-person voice and the existing product-name trigger, which are already strong.

DimensionReasoningScore

Specificity

Names the domain ("Zoho Books", accounting) and a couple of actions ("Manage accounting data, records, and workflows"), but the actions are generic rather than a comprehensive specific list.

3 / 5

Completeness

Explicitly answers both what ("Manage accounting data, records, and workflows") and when ("Use when the user wants to interact with Zoho Books data"), though the when-clause is somewhat generic.

4 / 5

Trigger Term Quality

Includes the natural product term "Zoho Books" and "accounting data", but misses common variations and synonyms a user might say (e.g. invoices, expenses, books).

3 / 5

Distinctiveness Conflict Risk

Targets a distinct named product (Zoho Books) with clear niche triggers and minimal overlap risk with other 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.