hibob
Hibob 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 Hibob. Routes through Apideck with serviceId "hibob".
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 (Hibob via Apideck HRIS unified API), lists concrete data entities it handles (employees, departments, payrolls, time-off records), and provides an explicit 'Use when' clause with natural trigger terms. The mention of serviceId 'hibob' and the unified API pattern adds helpful technical context for disambiguation from similar Apideck HRIS skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'read or sync employees, departments, payrolls, and time-off records in Hibob.' Also mentions the technical mechanism (Apideck's HRIS unified API, serviceId). | 3 / 3 |
Completeness | Clearly answers both 'what' (Hibob 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 Hibob'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Hibob', 'employees', 'departments', 'payrolls', 'time-off records', 'HRIS', 'Apideck', and 'sync'. These cover the main terms a user working with Hibob HR data would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific mention of 'Hibob' and 'serviceId "hibob"' along with the Apideck HRIS context. This clearly distinguishes it from other HRIS connector skills that would use different serviceIds, and from general HR or document skills. | 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.
The skill is well-structured with good progressive disclosure and actionable code examples. Its main weaknesses are moderate verbosity from repeated marketing-style messaging about portability and some missing validation/error-handling guidance. Trimming redundant portability explanations and adding basic error handling patterns would meaningfully improve it.
Suggestions
Remove or consolidate the 'Portable across 58 HRIS connectors' section — the portability point is already made in the intro and the sibling connectors section; repeating it with marketing language wastes tokens.
Add a brief error handling or validation step (e.g., checking response status, handling auth failures) to improve workflow clarity for common failure modes.
Trim the 'When to use this skill' section — Claude can infer activation criteria from the skill description and context without being told when to activate.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary verbosity — the 'Portable across 58 HRIS connectors' section repeats the portability message already stated in the intro, and marketing-style language like 'compounding advantage' and 'deepest employee coverage in the catalog' adds no actionable value. The 'When to use this skill' section also over-explains activation criteria that Claude can infer. | 2 / 3 |
Actionability | Provides fully executable TypeScript examples for listing employees, switching connectors, and using the proxy escape hatch with a complete curl command. The entity mapping table and auth details give concrete, specific guidance for working with Hibob through Apideck. | 3 / 3 |
Workflow Clarity | The skill covers a relatively simple task (API calls) but lacks any validation or error-handling guidance. There are no checkpoints for verifying API responses, handling auth failures, or confirming that the connection is properly configured in Apideck Vault before making calls. | 2 / 3 |
Progressive Disclosure | Excellent structure with a concise overview, quick facts, minimal example up front, and well-signaled one-level-deep references to SDK skills, OpenAPI specs, best practices, and connector coverage. Navigation is clear and references are appropriately linked. | 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.