holded
Holded 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 Holded. Routes through Apideck with serviceId "holded".
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 (Holded), the integration layer (Apideck HRIS unified API), concrete data entities (employees, departments, payrolls, time-off records), and explicit trigger conditions. It uses proper third-person voice and provides enough technical context (serviceId) for disambiguation while remaining accessible to users who would naturally mention these terms.
| 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 Holded'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Holded', 'employees', 'departments', 'payrolls', 'time-off records', 'HRIS', 'Apideck', 'sync'. These cover the main terms a user working with Holded HR data would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically targets Holded integration via Apideck with serviceId 'holded'. The combination of the specific platform (Holded), the API layer (Apideck), and the domain (HRIS) makes it very unlikely to conflict with other 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.
This is a well-structured connector skill with strong actionability and excellent progressive disclosure to related skills and references. Its main weaknesses are moderate verbosity (repeating the portability concept multiple times and including marketing-style language) and a lack of explicit workflow sequencing that would help Claude navigate the connect → verify → call → fallback path more reliably.
Suggestions
Consolidate the portability message into a single brief mention rather than repeating it in the intro, the 'Portable across 58 HRIS connectors' section, and the 'Sibling connectors' section.
Add an explicit numbered workflow (e.g., 1. Verify connection exists, 2. Check coverage for needed operation, 3. Call unified API, 4. If UnsupportedOperationError → use proxy) with validation checkpoints at each step.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary verbosity — e.g., the 'Portable across 58 HRIS connectors' section repeats the serviceId-switching concept already shown in the example and intro, and the marketing-style language ('compounding advantage') adds no actionable value. The 'When to use this skill' section also over-explains activation triggers Claude can infer. | 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 (connect → verify coverage → call API → fallback to proxy), but it's not presented as a clear sequence with validation checkpoints. The coverage verification step is mentioned but not integrated into a numbered workflow with explicit decision points or error handling. | 2 / 3 |
Progressive Disclosure | Excellent use of one-level-deep references to sibling skills (apideck-node, apideck-best-practices, apideck-connector-coverage), SDK skills, OpenAPI specs, and connection guides. The SKILL.md serves as a clear overview with well-signaled pointers to detailed materials. | 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.