Name: zoho-recruit
Rating: 60 (1 reviews)
Author: membranedev

zoho-recruit

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

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/zoho-recruit/SKILL.md

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 executable commands and a strong connection-state feedback loop, organized into clear sections. Its main weaknesses are a padded intro paragraph explaining the product and inline reference-style content that could be split out.

Suggestions

Trim the introductory paragraph that explains what Zoho Recruit is and who uses it; Claude can infer this from the product name.

Move the detailed clientAction state handling and the 18-item entity list into a separate reference file linked from the body to improve progressive disclosure.

Re-number the end-to-end flow as an explicit ordered sequence with validation checkpoints (1. Install, 2. Authenticate, 3. Connect, 4. Verify READY, 5. Search actions, 6. Run) so the workflow reads as a single coherent checklist.

Dimension	Reasoning	Score
Conciseness	Most of the body is efficient, executable commands and a flag table, but the intro paragraph ('Zoho Recruit is a cloud-based recruiting platform... Recruiters and HR professionals use it to streamline their talent acquisition efforts.') and phrases like 'so you can focus on the integration logic rather than auth plumbing' are unnecessary padding. It matches 'mostly efficient but includes some unnecessary explanation' and is not 4 due to those padded passages.	3 / 5
Actionability	The body is packed with copy-paste ready, fully executable commands (npm install, membrane login, connection ensure, action list/run, request) plus a concrete flags table covering the common cases. It matches 'fully executable; copy-paste ready code or commands; specific examples cover the common cases'.	5 / 5
Workflow Clarity	The connection flow (install -> authenticate -> connect -> poll until READY -> search actions -> run) has explicit state-based checkpoints and error-recovery feedback loops for CLIENT_ACTION_REQUIRED and CONFIGURATION_ERROR. It is not 5 because the overall sequence numbering is loose ('skip to Step 2', '1b') rather than a fully numbered, checkpoint-anchored list.	4 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections (Overview, Working with Zoho Recruit, Popular actions, Best practices) with no nested or buried references, and no bundle files are used. It is not 5 because content that could live in a separate file (the long clientAction state explanation, the 18-item entity list) is inlined, leaving minor organization gaps.	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 answers both what and when with a distinctive product name, but relies on generic action verbs and a single thin trigger phrase. Strengthening it with concrete operations and broader trigger terms would raise specificity and trigger quality.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete operations such as 'search candidates, create job openings, track applications, and run automation workflows'.

Broaden trigger terms to include natural phrasings users say, e.g. 'Use when the user wants to manage candidates, job openings, interviews, or recruiting workflows in Zoho Recruit'.

Add domain synonyms (recruiting, ATS, applicants) to reduce reliance on the single product-name trigger.

Dimension	Reasoning	Score
Specificity	Names the Zoho Recruit domain with a couple of actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete, matching the 'names domain and 1-2 concrete actions, not comprehensive' anchor. It does not reach 4 because no specific operations (e.g., list candidates, create job openings) are enumerated, and stays above 2 because multiple actions are listed.	3 / 5
Completeness	Both 'what' ('Zoho Recruit integration. Manage data, records, and automate workflows.') and 'when' ('Use when the user wants to interact with Zoho Recruit data.') are explicitly present in third person. It is not 5 because the trigger phrases are thin and could be more specific, matching the 'has both what and when; when could be more explicit' anchor.	4 / 5
Trigger Term Quality	The only natural trigger term is 'Zoho Recruit' / 'interact with Zoho Recruit data', which is relevant but lacks synonyms or common variations users might say. It fits 'some relevant keywords but missing common variations or synonyms' and is not 4 since natural phrases like 'recruiting', 'candidates', or 'job applications' are absent.	3 / 5
Distinctiveness Conflict Risk	Naming the specific SaaS product 'Zoho Recruit' gives a clear niche with distinct triggers and minimal conflict risk with other skills. It clearly matches the 'clear niche with distinct triggers; minimal conflict risk' anchor.	5 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/zoho-recruit/SKILL.md
Commit: f484c82

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.