Name: employment-hero
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

employment-hero

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

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/employment-hero/SKILL.md

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 skill is highly actionable with copy-paste CLI commands and a sensible connection workflow, but it pads the opening with background Claude already knows, inlines a large actions table that belongs in a reference file, and lacks verification steps and a defined 'Step 2' for write operations. Strengthening validation and splitting reference material would notably improve it.

Suggestions

Add a verification step after write/create actions (e.g. re-run `membrane action run get-employee` or `list-employees` to confirm the change took effect).

Define the dangling 'Step 2' reference (label the 'Searching for actions' / 'Running actions' sections as Step 2 and Step 3) so the workflow is unambiguous.

Move the Popular actions table to a separate reference file (e.g. ACTIONS.md) and link to it from the body to improve progressive disclosure and token efficiency.

Dimension	Reasoning	Score
Conciseness	Most sections are efficient with copy-paste commands, but the opening paragraph explaining what Employment Hero is and who uses it, plus phrasing like 'so you can focus on the integration logic rather than auth plumbing', is padding Claude does not need, matching the 'mostly efficient but some unnecessary explanation' anchor.	3 / 5
Actionability	Commands are fully executable and copy-paste ready (install, login, connection ensure, action list/run, request proxy) and the popular-actions table gives concrete keys covering the common cases, matching the 'fully executable; specific examples cover common cases' anchor.	5 / 5
Workflow Clarity	A clear install→login→connect→search→run sequence exists with a connection-state polling loop, but write/batch actions (update-personal-details, quick-add-employee) have no verification step and 'Step 2' is referenced but never defined, so the destructive/batch validation cap of 3 applies.	3 / 5
Progressive Disclosure	The body is organized into clear sections, but the 16-row Popular actions table is bulk reference content inlined in SKILL.md with no external reference files, matching the 'content that should be separate is inline' anchor; at 175 lines it does not qualify for the small-skill exception.	3 / 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 includes an explicit 'Use when' trigger and ties the skill to a distinct named product, but its capability verbs are generic and it omits the natural synonyms (HR, payroll, employees) users would actually say. It is functional but could be sharper and more concrete.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete operations, e.g. 'List and update employees, submit leave requests, run payroll, and manage timesheets'.

Add natural trigger synonyms users say, e.g. 'Use when the user wants to manage HR data, employees, payroll, leave, or timesheets in Employment Hero.'

Mention file/API surface or key entities (employees, leave, payrun, expense claims) to boost specificity and distinctiveness.

Dimension	Reasoning	Score
Specificity	It names the domain (Employment Hero) but the actions — 'Manage data, records, and automate workflows' — are generic verbs rather than concrete operations, fitting the 'actions are minimal or generic' anchor and falling short of naming 1-2 truly concrete actions.	2 / 5
Completeness	It states both what ('Employment Hero integration. Manage data, records, and automate workflows.') and when ('Use when the user wants to interact with Employment Hero data.'), but the 'when' clause is generic rather than tied to concrete trigger phrases, matching the 'both present, when could be more explicit' anchor.	4 / 5
Trigger Term Quality	'Employment Hero' and 'Employment Hero data' are relevant natural keywords, but common synonyms a user might say (HR, payroll, employees, leave) are missing, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Tying the skill to the named product 'Employment Hero' gives it a clear niche with low conflict risk, but the generic 'manage data, records' phrasing leaves minor overlap with other HR/data skills, so it sits above the midpoint rather than at the fully-distinct anchor.	4 / 5
	Total	13 / 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/employment-hero/SKILL.md
Commit: f484c82

Reviewed: 4 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.