humaans-io
Humaans 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 Humaans. Routes through Apideck with serviceId "humaans-io".
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 platform (Humaans), the integration mechanism (Apideck HRIS unified API), concrete data entities (employees, departments, payrolls, time-off records), and explicit trigger guidance. The description is concise, uses third-person voice, and provides enough detail for Claude to distinguish it from other HRIS connector skills via the serviceId.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'read or sync employees, departments, payrolls, and time-off records' and mentions the integration mechanism (Apideck's HRIS unified API, serviceId). These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (Humaans integration via Apideck's HRIS unified API for reading/syncing employees, departments, payrolls, time-off records) and 'when' (explicit 'Use when the user wants to read or sync employees, departments, payrolls, and time-off records in Humaans'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Humaans', 'employees', 'departments', 'payrolls', 'time-off records', 'HRIS', 'Apideck', 'humaans-io'. Good coverage of both the platform name and the data entities a user would reference. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific platform name 'Humaans', the serviceId 'humaans-io', and the Apideck HRIS context. Unlikely to conflict with other skills unless there are other Humaans-specific integrations, and the serviceId differentiator makes it clear. | 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 and excellent progressive disclosure through cross-references to related skills and external documentation. Its main weaknesses are some promotional/marketing verbosity that doesn't serve Claude's needs, and a lack of an explicit step-by-step workflow tying together coverage verification, API calls, and proxy fallback into a clear sequence with validation checkpoints.
Suggestions
Consolidate the 'Portable across 58 HRIS connectors' section into a single sentence in the intro — the portability point is already made and the repeated code example adds little value.
Add an explicit numbered workflow (e.g., 1. Verify coverage → 2. Call unified API → 3. Handle UnsupportedOperationError → 4. Fall back to Proxy) with validation checkpoints to improve workflow clarity.
Remove the 'When to use this skill' section's explanatory bullets — Claude doesn't need to be told what the skill teaches it; the content itself demonstrates that.
| 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 'When to use this skill' section over-explains activation triggers, and phrases like 'This is the compounding advantage of using Apideck over integrating Humaans directly' are promotional rather than instructional. 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 setup, and SDK references are all specific and copy-paste ready. | 3 / 3 |
Workflow Clarity | There's an implicit workflow (set up auth → verify coverage → call unified API → fall back to proxy if unsupported), but it's not presented as a clear sequence with explicit validation checkpoints. The 'Verifying coverage' step is mentioned but not integrated into a numbered workflow with error handling feedback loops. | 2 / 3 |
Progressive Disclosure | Excellent use of one-level-deep references to sibling skills (apideck-best-practices, apideck-connector-coverage, SDK skills), external docs, and OpenAPI specs. The skill keeps its overview concise and clearly signals where to find detailed information for each concern. | 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.