CtrlK
BlogDocsLog inGet started
Tessl Logo

hr-cloud

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

56

Quality

63%

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/hr-cloud/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 content is highly actionable with copy-paste commands and a strong connection workflow, but it carries a background-fluff intro, lacks verification steps around destructive write actions, and inlines reference bulk that would benefit from a separate file. It lands above average but with clear trim and structure opportunities.

Suggestions

Remove the introductory 'HR Cloud is a human resources management platform...' paragraph; assume Claude knows what an HR platform is.

Add a verify step after create/update/upsert actions, e.g. re-fetch the record with get-employee to confirm the change applied.

Move the popular-actions table and clientAction state reference into a references/ file and link to it from SKILL.md so the overview stays lean.

DimensionReasoningScore

Conciseness

Most of the body is efficient, executable command reference, but the opening paragraph ('HR Cloud is a human resources management platform that helps businesses streamline their HR processes...') explains background Claude already knows and could be trimmed.

3 / 5

Actionability

Copy-paste-ready commands cover the common cases end to end: install, login (including headless), connection ensure, action list/run with --input JSON, and request proxy with full flag table, plus a 20-row action key reference.

5 / 5

Workflow Clarity

The connection setup is well sequenced with explicit state checkpoints (READY, CLIENT_ACTION_REQUIRED, polling with --wait), but write operations (create-/update-/upsert-employee) have no post-action verification step, so the destructive-operation validation cap applies.

3 / 5

Progressive Disclosure

Sections are clearly headed and there are no nested references, but bulk reference-like material (the 20-row popular-actions table and the nested clientAction state spec) is inlined in SKILL.md with no bundle files to split it into, so it is only moderately organized.

3 / 5

Total

14

/

20

Passed

Description

62%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 distinct product-specific trigger, but its action language stays generic and it omits the concrete HR entities (employees, applicants, tasks) that would sharpen trigger matching. It is solid but not exemplary.

Suggestions

Replace generic verbs with concrete capabilities, e.g. 'List, create, and update employees, applicants, tasks, and departments in HR Cloud.'

Expand the trigger clause to name natural user phrases: 'Use when the user wants to manage HR Cloud employees, applicants, time-off requests, or departments.'

Add entity/file-style keywords (employees, applicants, tasks, locations) so the trigger matches a wider range of natural requests.

DimensionReasoningScore

Specificity

Names the HR Cloud domain plus three actions ('Manage data, records, and automate workflows'), but the verbs are generic rather than concrete operations like 'list employees' or 'create tasks', so coverage is not comprehensive.

3 / 5

Completeness

Both 'what' (HR Cloud integration that manages data, records, and workflows) and an explicit 'when' ('Use when the user wants to interact with HR Cloud data') are present, though the 'what' is generic and the trigger could name more concrete use cases.

4 / 5

Trigger Term Quality

The natural keyword 'HR Cloud' appears and 'interact with HR Cloud data' is a plausible user phrase, but common variations, synonyms, and concrete entity terms (employees, applicants, tasks) are missing.

3 / 5

Distinctiveness Conflict Risk

The named product 'HR Cloud' gives a clear, distinct niche with low conflict risk, but the generic action verbs ('manage data, records, automate workflows') leave minor overlap with other integration skills.

4 / 5

Total

14

/

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.