CtrlK
BlogDocsLog inGet started
Tessl Logo

zoho-people

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

52

Quality

59%

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-people/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, command-driven integration guide with executable examples and a solid connection-state feedback loop. Its weaknesses are some introductory over-explanation and the absence of validation steps before destructive data-mutating actions.

Suggestions

Add a validation/verification checkpoint before and after destructive actions (e.g. confirm the employee record with get-employee-by-id before running update-employee, and re-fetch to verify the change applied).

Trim the introductory "Zoho People is a cloud-based HR management system..." paragraph and the "Use action names and parameters as needed" filler, since Claude already knows what an HR system is.

For high-stakes actions like apply-leave and update-employee, show a concrete run example with a sample --input JSON payload rather than only the generic placeholder form.

DimensionReasoningScore

Conciseness

The opening paragraph ("Zoho People is a cloud-based HR management system...") explains concepts Claude already knows and "Use action names and parameters as needed" is filler, though the bulk is efficient executable commands, matching the mostly-efficient-but-could-be-tightened anchor.

3 / 5

Actionability

It provides many copy-paste-ready commands with real flags (login, connection ensure, action list/run, request) plus a populated actions table, with only minor gaps such as placeholders for CONNECTION_ID and omitted full input schemas, matching the mostly-executable anchor.

4 / 5

Workflow Clarity

The install→auth→connect→poll→search→run sequence is clear and includes a feedback loop on connection state (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but destructive operations like create-employee, update-employee, and apply-leave run with no validation checkpoint, which caps this score at 3.

3 / 5

Progressive Disclosure

No bundle files exist, and the ~160-line body is organized into clear sections (Overview, Auth, Connecting, Searching, Popular actions, Proxy, Best practices) with content appropriately inline, matching the good-structure anchor with minor organization gaps.

4 / 5

Total

14

/

20

Passed

Description

57%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 correctly names the target app and includes an explicit "Use when" trigger, but its action verbs are generic rather than concrete and its supporting keywords lack synonyms. It is distinct and complete enough but could be sharpened.

Suggestions

Replace generic verbs ("manage", "automate") with concrete actions such as "look up leave balances", "log time", "apply leave", or "sync employee records".

Add natural synonyms and trigger phrases a user might say, e.g. "Zoho People, HR records, leave requests, timesheets, attendance".

Tighten the "Use when" clause to specific intents, e.g. "Use when the user wants to query or update employee, leave, timesheet, or attendance data in Zoho People."

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the Zoho People domain but relies on generic verbs ("manage", "automate") rather than concrete actions like extract, fill, or merge, matching the anchor where actions are minimal or generic.

2 / 5

Completeness

It provides both a "what" (manage data, records, automate workflows) and an explicit "when" ("Use when the user wants to interact with Zoho People data"), though the trigger clause is somewhat generic, matching the anchor where both are present but "when" could be more specific.

4 / 5

Trigger Term Quality

The specific term "Zoho People" is a strong natural keyword, but supporting terms ("data", "records", "workflows") are generic and lack common synonyms or variations, matching the anchor for some relevant keywords with missing variations.

3 / 5

Distinctiveness Conflict Risk

Naming the specific HR app "Zoho People" gives it a clear niche with minimal conflict risk, though there is minor overlap potential with other HR/payroll skills, matching the mostly-distinct anchor.

4 / 5

Total

13

/

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.