CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

clayhr

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

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/clayhr/SKILL.md
SKILL.md
Quality
Evals
Security

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 a well-organized, mostly executable CLI guide: concrete commands, a clear connection-state workflow with polling checkpoints, and a useful proxy fallback with documented flags. Weaknesses are minor — a dangling "Step 2" reference, an empty "Popular actions" section, a marketing-flavored intro, and no error-handling guidance for failed action runs.

Suggestions

Label the post-connection sections as numbered steps (or fix the two "skip to Step 2" references) so the connection flow is unambiguous.

Either populate "Popular actions" with a few named ClayHR actions (e.g. list employees, request time off) or remove the empty heading.

Trim the product intro and add a short error-handling note for failed `action run` / proxy calls (check the `error` field, re-check connection state).

DimensionReasoningScore

Conciseness

The body is dominated by lean, executable CLI commands with minimal prose, but a few trimmable bits remain: the marketing-style intro ("designed to streamline HR processes... small to medium-sized businesses"), the awkward "Agent Types" note, and a "Popular actions" section that contains no actions.

4 / 5

Actionability

Nearly every section gives copy-paste-ready commands (npm install, membrane login, connection ensure with --json, action run with --input JSON, proxy flags table). Minor gaps: the "Popular actions" heading lists no actual actions, and `membrane login --tenant` shows the flag without its value syntax.

4 / 5

Workflow Clarity

The install → login → connect → search → run sequence is clear with explicit state-branch handling (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and polling feedback loops. Minor gaps: the text says "skip to Step 2" twice but no section is labeled Step 2, and there is no error-handling guidance for failed `action run` calls.

4 / 5

Progressive Disclosure

The skill has no bundle files (no references/, scripts/, or assets/), and the body is a well-sectioned, self-contained overview of reasonable length — good structure with minor organization gaps, e.g. the proxy flag table and entity list could live in a reference file if the skill grows.

4 / 5

Total

16

/

20

Passed

Description

48%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 the capability statement relies on generic verbs (manage, automate workflows) with no concrete ClayHR operations and no HR-domain synonyms. It is functional for users who already name ClayHR, but will not surface the skill for HR-task phrasings.

Suggestions

Replace the generic verbs with concrete ClayHR operations, e.g. "Manage employees, time off, payroll, and work shifts in ClayHR".

Broaden the trigger clause beyond the app name, e.g. "Use when the user mentions ClayHR or asks about employee records, time-off policies, or HR data".

Mention 1-2 natural synonyms (HRMS, employee data) so the skill triggers for HR-shaped requests that never say "ClayHR".

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the ClayHR domain but the actions are generic verbs — no concrete HR operations like employee records, payroll, or time-off management are stated, matching anchor 2 rather than anchor 3's 1-2 concrete actions.

2 / 5

Completeness

An explicit "Use when the user wants to interact with ClayHR data" clause is present, but the 'what' ("Manage data, records, and automate workflows") is vague and the 'when' is circular — it only fires on ClayHR mentions rather than concrete triggers — placing it between anchors 3 and 4 with the weak 'what' pulling it down.

3 / 5

Trigger Term Quality

"ClayHR" is a natural keyword users would say, but "data" and "records" are generic; common variations like HR, HRMS, employee, payroll, or time off are missing, matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The distinctive "ClayHR" app name establishes a clear niche with minimal conflict risk, but the generic "Manage data, records, and automate workflows" phrasing overlaps with broad data-management skills, matching anchor 4 rather than anchor 5.

4 / 5

Total

12

/

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

membranedev/application-skills

Path

skills/clayhr/SKILL.md

Revision

f484c82

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill