employmenthero
Employment Hero integration via Apideck's HRIS unified API — same methods work across every connector in HRIS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in Employment Hero. Routes through Apideck with serviceId "employmenthero".
87
86%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly identifies the specific integration (Employment Hero via Apideck HRIS), lists concrete data entities it handles, and provides an explicit 'Use when' clause with natural trigger terms. The mention of serviceId switching adds helpful context for distinguishing it from sibling Apideck connector skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: read/sync employees, departments, payrolls, and time-off records. Also specifies the integration mechanism (Apideck's HRIS unified API) and the serviceId parameter. | 3 / 3 |
Completeness | Clearly answers both what (Employment Hero integration via Apideck HRIS API for reading/syncing employees, departments, payrolls, time-off) and when ('Use when the user wants to read or sync employees, departments, payrolls, and time-off records in Employment Hero'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Employment Hero', 'employees', 'departments', 'payrolls', 'time-off records', 'HRIS', 'Apideck', and 'employmenthero' as a serviceId. Good coverage of domain-specific terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with the specific 'Employment Hero' product name and 'serviceId employmenthero' identifier. While it shares the Apideck HRIS pattern with potential sibling skills, the explicit serviceId and product name make it clearly distinguishable. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured connector skill with strong actionability (executable code examples, concrete curl commands) and excellent progressive disclosure to related skills and references. Its main weaknesses are moderate verbosity — particularly the repeated portability messaging and marketing-style language — and a workflow that could be more explicitly sequenced with validation checkpoints, especially given the beta status and partial coverage caveats.
Suggestions
Consolidate the portability message into a single brief mention (intro or the code example, not both) and remove marketing language like 'compounding advantage'.
Add an explicit numbered workflow: 1) Verify coverage via connector API, 2) If supported → use unified API, 3) If UnsupportedOperationError → use Proxy API, with a clear decision checkpoint between steps.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary verbosity — the 'Portable across 58 HRIS connectors' section repeats the portability point already made in the intro, and the marketing-style language ('compounding advantage') adds no actionable value. The 'When to use this skill' section explains things Claude can infer. However, the quick facts and code examples are reasonably tight. | 2 / 3 |
Actionability | Provides fully executable TypeScript code for listing employees, a concrete curl command for verifying coverage, and a complete proxy API escape hatch with all required headers. The serviceId, auth setup, and fallback patterns are all copy-paste ready. | 3 / 3 |
Workflow Clarity | There's an implicit workflow (check coverage → use unified API → fall back to proxy if unsupported), but it's not presented as a clear sequential process with explicit validation checkpoints. The beta status warning mentions verifying coverage but doesn't integrate this into a structured decision flow with error handling feedback loops. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a concise overview and well-signaled one-level-deep references to SDK skills, best practices, connector coverage, OpenAPI specs, and sibling connectors. Navigation is clear and references are consistently formatted with links. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- apideck-libraries/api-skills
- Commit
9e04d86
- 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.