CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

59

Quality

69%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/zoho-crm-automation/SKILL.md

The canonical home for this skill is zoho-crm-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

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 well-structured, concise, and actionable with concrete tool sequences and syntax, but destructive workflows (lead conversion) and batch operations lack explicit validation/verification steps, capping workflow clarity at 3.

Suggestions

Add an explicit validation checkpoint before irreversible lead conversion (e.g., 'Confirm the matched lead_id with the user before calling ZOHO_CONVERT_ZOHO_LEAD') and a verify step afterward.

Add a verify/retry loop for bulk/batch operations (e.g., 'On 429 responses, back off using rate-limit headers and retry').

De-duplicate the search-operator list (workflow 1 pitfalls vs. Common Patterns) to resolve the inconsistency between greater_than/less_than and greater_equal/less_equal/between.

DimensionReasoningScore

Conciseness

Largely lean — tool sequences, parameter tables, and syntax examples assume Claude's competence — with minor redundancy (search operators listed in both workflow 1 pitfalls and Common Patterns, with slight inconsistency) and a vague closing 'When to Use' line; not verbose enough to drop to 3, but not perfectly tight enough for 5.

4 / 5

Actionability

Provides concrete tool slugs (e.g., ZOHO_SEARCH_ZOHO_RECORDS), explicit parameter lists, and copy-ready criteria syntax examples; minor gaps (no full sample record payloads) keep it just below 5, while it is well above the pseudocode/vague 3 anchor.

4 / 5

Workflow Clarity

Workflows are clearly sequenced with numbered tool steps, but destructive operations lack validation checkpoints — lead conversion is flagged as 'irreversible' yet has no confirm/verify step, and bulk tag operations note rate limits without a verify loop; the rubric caps workflow clarity at 3 for destructive/batch skills missing validation.

3 / 5

Progressive Disclosure

No bundle files exist, so all content is inline in a single SKILL.md organized under clear, navigable section headers (Prerequisites, Setup, Core Workflows, Common Patterns, Quick Reference); structure is good with only minor organization gaps, fitting the 4 anchor rather than 5 (no one-level-deep references to signal) or 3 (it is well-organized, not merely 'some structure').

4 / 5

Total

15

/

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 is specific, well-keyworded, and clearly distinct, but it lacks an explicit 'Use when...' trigger clause, capping completeness at 3.

Suggestions

Add an explicit trigger clause such as 'Use when the user wants to automate Zoho CRM operations — creating or updating records, searching contacts, managing leads, or converting leads.'

Replace the instructional 'Always search tools first for current schemas' (or keep it) with a trigger-oriented 'when' statement so the description answers both what and when.

Consider adding a synonym such as 'CRM records' to broaden natural-term coverage.

DimensionReasoningScore

Specificity

Names the domain and four concrete actions — 'create/update records, search contacts, manage leads, and convert leads' — with only minor coverage gaps; it is not a fully comprehensive list (no delete, no notes/tasks), so it falls below 5.

4 / 5

Completeness

Clearly states what it does, but the only 'when'-style clause is 'Always search tools first for current schemas', which is an instruction rather than explicit trigger guidance; per the rubric a missing 'Use when...' clause caps completeness at 3, and it is not below 3 because the 'what' is clear.

3 / 5

Trigger Term Quality

Includes natural terms users say ('search contacts', 'manage leads', 'convert leads', 'Zoho CRM') but misses common synonyms/variations; good coverage without being exhaustive, fitting the 4 anchor.

4 / 5

Distinctiveness Conflict Risk

'Zoho CRM via Rube MCP (Composio)' is a clear niche with distinct triggers and minimal overlap risk with other skills, matching the 5 anchor.

5 / 5

Total

16

/

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