hr-works
HR Works 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 HR Works. Routes through Apideck with serviceId "hr-works".
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 (HR Works via Apideck), lists concrete data entities it handles, and provides explicit trigger guidance. The inclusion of the serviceId and the note about connector switching adds useful technical context without being overly verbose. It follows third-person voice and would be easily distinguishable from other HRIS connector skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: read or sync employees, departments, payrolls, and time-off records. Also mentions specific technical details like serviceId, unified API, and connector switching. | 3 / 3 |
Completeness | Clearly answers both what ('read or sync employees, departments, payrolls, and time-off records via Apideck's HRIS unified API') and when ('Use when the user wants to read or sync employees, departments, payrolls, and time-off records in HR Works'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'HR Works', 'employees', 'departments', 'payrolls', 'time-off records', 'HRIS', 'Apideck', and 'hr-works'. Good coverage of both product names and domain terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific product name 'HR Works', specific serviceId 'hr-works', and routing through Apideck. This clearly distinguishes it from other HRIS integrations by the specific connector/service. | 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 solid connector-specific skill with good actionability and excellent progressive disclosure to related skills and resources. Its main weaknesses are moderate verbosity (marketing language, OAuth explanations Claude doesn't need) and a workflow that could be more explicitly sequenced with validation checkpoints. The escape hatch and coverage verification sections are valuable additions.
Suggestions
Remove the promotional paragraph in 'Portable across 58 HRIS connectors' ('This is the compounding advantage...') and trim the OAuth explanation to just 'OAuth 2.0 managed by Apideck Vault — see best-practices skill for details.'
Add an explicit numbered workflow: 1. Verify coverage → 2. Call unified API → 3. If UnsupportedOperationError, use Proxy API → 4. Validate response, to make the multi-step process clearer with checkpoints.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary verbosity — the 'Portable across 58 HRIS connectors' section repeats the marketing pitch from the intro, the authentication section explains OAuth concepts Claude already knows, and phrases like 'This is the compounding advantage of using Apideck over integrating HR Works directly' are promotional filler. However, the core content is reasonably focused. | 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 real headers. The serviceId, auth type, and setup links are all specific and actionable. | 3 / 3 |
Workflow Clarity | The skill implicitly sequences a workflow (setup → verify coverage → call API → fall back to proxy), but it's not presented as an explicit numbered workflow with validation checkpoints. The coverage verification step is present but not integrated into a clear 'before you call, verify' feedback loop. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure — the skill provides a concise overview with well-signaled one-level-deep references to SDK skills, best practices, connector coverage, OpenAPI specs, and sibling connectors. Content is appropriately split between this file and referenced resources. | 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.