CtrlK
BlogDocsLog inGet started
Tessl Logo

zoho-salesiq

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

62

Quality

74%

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

Quality

Content

78%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 executable CLI commands and a clear connection state-machine workflow. Its weaknesses are minor over-explanation and inlining of detailed reference material that progressive disclosure would move to a separate file.

Suggestions

Move the detailed connection state-machine (clientAction fields, state transitions) and the request-options table into a references/ file, leaving a concise overview with a clearly signaled link.

Trim the opening "Zoho SalesIQ is a customer engagement platform..." paragraph and the prose duplicating the bulleted state list to reduce token overhead.

DimensionReasoningScore

Conciseness

The body is mostly lean, executable commands with a useful options table, but the opening SalesIQ overview paragraph and the prose restating the bulleted connection state machine are minor over-explanation that could be trimmed. It is more efficient than anchor 3 yet not the every-token-earns-its-place lean of anchor 5.

4 / 5

Actionability

It provides fully executable, copy-paste-ready commands (install, login, connection ensure, action list/run, request proxy) complete with flags, JSON examples, and the common-case options table. This matches anchor 5's copy-paste-ready coverage of common cases.

5 / 5

Workflow Clarity

The connection flow is a clear state-machine sequence (READY / BUILDING / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) with a poll-after-action feedback loop for re-authentication. A few validation checkpoints are implicit rather than explicit, so it does not reach anchor 5's full feedback-loop rigor.

4 / 5

Progressive Disclosure

No bundle files exist and the content is a single SKILL.md; it is well-sectioned but the detailed connection state-machine reference and options table are inlined rather than split into a referenced file. This matches anchor 3 (structured but with content that could live in a separate file inlined), and it is below anchor 4 which expects appropriately split, clearly signaled references.

3 / 5

Total

16

/

20

Passed

Description

70%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 cleanly identifies a distinct product niche and includes an explicit "Use when" trigger, satisfying both what and when. Its main weakness is generic action language ("manage data, records") instead of concrete Zoho SalesIQ capabilities.

Suggestions

Replace generic verbs with concrete SalesIQ capabilities, e.g. "Manage chats, visitors, agents, and departments; run and automate workflows".

Expand the trigger phrase with natural terms users say, e.g. "Use when the user wants to manage live chats, website visitors, agents, or departments in Zoho SalesIQ".

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the Zoho SalesIQ domain plus a couple of action areas, but the actions are generic rather than concrete, so coverage is not comprehensive. It sits above anchor 2 (which only names the domain) but below anchor 4, which requires several specific actions.

3 / 5

Completeness

It states both the "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Zoho SalesIQ data"), satisfying the missing-trigger cap. The "when" could be more specific with enumerated concrete triggers, so it does not reach anchor 5.

4 / 5

Trigger Term Quality

"Zoho SalesIQ" is the natural product-name keyword a user would say, and "interact with Zoho SalesIQ data" is a usable trigger phrase, but common variations/synonyms (live chat, visitors, agents, departments) are missing. It clears anchor 3 yet falls short of the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The named Zoho SalesIQ product gives it a clear, distinct niche with minimal conflict risk. The generic "interact with ... data" framing leaves slight overlap risk versus other data-integration skills, keeping it just below the minimal-risk anchor 5.

4 / 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.