CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

zoho-crm-automation

Automate Zoho CRM tasks via Rube MCP (Composio): create/update records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.

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-crm-automation/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 a well-structured, domain-specific playbook with concrete tool names, parameters, and example criteria, and an accurate quick-reference table. Its main weaknesses are redundancy (duplicated operator and pitfall lists, a filler 'When to Use' section) and the absence of any validation or confirmation checkpoint before the irreversible lead-conversion operation, which caps workflow clarity.

Suggestions

Add a verification step to the Convert Leads workflow (e.g., confirm the found record with the user, or re-check the lead_id and warn that conversion is irreversible) before calling ZOHO_CONVERT_ZOHO_LEAD; similarly add a 429/backoff retry loop for bulk operations.

Deduplicate: keep the operator list, field-name rules, and data formats in one place (Common Patterns / Known Pitfalls) instead of repeating them per workflow, and delete the circular 'When to Use' section.

Show one concrete example `data` payload for ZOHO_CREATE_ZOHO_RECORD (e.g., {"Last_Name": "Doe", "Email": "..."}) to make the create/update path fully copy-paste ready.

DimensionReasoningScore

Conciseness

Mostly efficient and Zoho-specific, but noticeably redundant: search operators are listed twice (workflow 1 "Supported operators: equals, starts_with, contains..." and again under Search Criteria Syntax), pitfalls appear both per-workflow and again in Known Pitfalls, and the closing "## When to Use — This skill is applicable to execute the workflow or actions described in the overview" is pure filler. This matches 'Mostly efficient but includes some unnecessary explanation or could be tightened' rather than the minor-trim level of 4.

3 / 5

Actionability

Concrete tool sequences with exact tool names and roles ("1. ZOHO_SEARCH_ZOHO_RECORDS - Find the record to update [Prerequisite]"), example criteria ("'(Email:equals:john@example.com)'"), and precise pagination details ("Set per_page (max 200) and page starting at 1", "Check response info.more_records flag") are copy-paste-usable. Not 5 because the create/update workflows never show a sample `data` payload, leaving the most common write operation without a concrete example.

4 / 5

Workflow Clarity

Sequences are clear and prerequisites are tagged, and Setup does include a checkpoint ("Confirm connection status shows ACTIVE before running any workflows"). However, the Convert Leads workflow is explicitly destructive — "Lead conversion is irreversible; the lead record is removed from the Leads module" — yet has no verification or confirmation step before converting (search → convert only), and bulk tag operations note rate limits without a validate/retry loop. Per the rubric guideline, missing validation on destructive/batch operations caps workflow clarity at 3; it does not drop to 2 because sequencing and prerequisites are otherwise well defined.

3 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are all absent), so the skill is a self-contained single file; there are no dangling or nested references to verify. It is well organized with clear sections (Prerequisites, Setup, five Core Workflows, Common Patterns, Known Pitfalls, Quick Reference table) and no deep nesting, matching 'Good structure; most content is appropriately placed... minor organization gaps'. Not 5 because at ~200 lines the detailed pitfalls/rate-limit/format reference material could be split into a reference file, and the operator list duplication hurts organization.

4 / 5

Total

14

/

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 names a distinct niche (Zoho CRM via Rube MCP/Composio) and lists concrete, largely non-overlapping actions, but it omits any 'Use when...' trigger guidance, which both caps completeness and weakens its value for skill selection. It is concise and in third person, with no fluff or over-claims.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user mentions Zoho, Zoho CRM, or asks to create/update/search CRM records, contacts, leads, or deals.'

Replace the generic "manage leads" with the distinct capabilities the body actually covers (e.g., tags and related-record updates) and mention deals/accounts to broaden natural trigger terms.

Keep the operational note 'Always search tools first for current schemas' in the body's Prerequisites instead of spending description tokens on it.

DimensionReasoningScore

Specificity

Quotes several concrete actions — "create/update records, search contacts, manage leads, and convert leads" — closely matching the anchor 'Lists several specific actions; minor gaps in coverage'. It falls short of 5 because "manage leads" is generic and overlaps the other actions, and tags/related-records/deals coverage from the body is absent.

4 / 5

Completeness

The 'what' is clear ("Automate Zoho CRM tasks via Rube MCP (Composio): create/update records, search contacts, manage leads, and convert leads"), but there is no 'Use when...' clause or equivalent trigger guidance — the closing sentence "Always search tools first for current schemas" is an instruction, not a 'when'. Per the rubric guideline, a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Good natural keyword coverage: "Zoho CRM", "search contacts", "convert leads", "create/update records" — phrases a user would plausibly say. Not 5 because common variations like "deals", "accounts", "pipeline", or standalone "CRM" triggers are missing; not 3 because the core natural terms are present, not just jargon.

4 / 5

Distinctiveness Conflict Risk

"Zoho CRM" plus "via Rube MCP (Composio)" carves out a clear niche with a distinct trigger term, matching 'Mostly distinct; minor overlap risk with closely related skills' — the risk being other CRM automation skills (Salesforce, HubSpot) triggered by generic phrases like "manage leads". Not 5 because the generic lead/contact terms could collide with sibling CRM skills absent the Zoho qualifier.

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.

Validation — 15 / 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

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

skills/zoho-crm-automation/SKILL.md

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.