loket-nl
Loket.nl 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 Loket.nl. Routes through Apideck with serviceId "loket-nl".
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 (Loket.nl via Apideck HRIS), lists concrete data entities it handles, and provides an explicit 'Use when' clause with natural trigger terms. The description is concise, uses third-person voice, and is highly distinctive with minimal conflict risk.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'read or sync employees, departments, payrolls, and time-off records' and specifies the integration mechanism (Apideck's HRIS unified API, serviceId). Also mentions switching connectors by changing serviceId. | 3 / 3 |
Completeness | Clearly answers both 'what' (Loket.nl integration via Apideck HRIS unified API for reading/syncing employees, departments, payrolls, time-off) and 'when' (explicit 'Use when the user wants to read or sync employees, departments, payrolls, and time-off records in Loket.nl'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Loket.nl', 'employees', 'departments', 'payrolls', 'time-off records', 'HRIS', 'Apideck', 'sync', and the specific serviceId 'loket-nl'. Good coverage of domain-specific and natural terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a specific service (Loket.nl) via a specific platform (Apideck) with a specific serviceId. Unlikely to conflict with other skills unless there are other Loket.nl integrations, and the Apideck/serviceId detail further narrows the niche. | 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 progressive disclosure and actionable code examples. Its main weaknesses are some promotional/marketing verbosity that doesn't serve Claude's needs, and a lack of explicit workflow sequencing with validation checkpoints for the multi-step process of connecting, verifying coverage, and making API calls.
Suggestions
Remove the promotional paragraph in 'Portable across 58 HRIS connectors' ('This is the compounding advantage...') — Claude doesn't need to be sold on the architecture.
Add an explicit numbered workflow: 1. Verify connection state → 2. Check coverage → 3. Call unified API → 4. If UnsupportedOperationError, use proxy fallback, with validation at each step.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary verbosity — the 'Portable across 58 HRIS connectors' section repeats the marketing pitch from the intro, and phrases like 'This is the compounding advantage of using Apideck over integrating Loket.nl directly' are promotional filler Claude doesn't need. The 'When to use this skill' section also over-explains. However, the code examples and quick facts are lean. | 2 / 3 |
Actionability | Provides fully executable TypeScript code for listing employees, a concrete curl command for verifying coverage, and a concrete curl command for the proxy escape hatch. The serviceId, auth type, and SDK references are all specific and copy-paste ready. | 3 / 3 |
Workflow Clarity | There's an implicit workflow (connect → verify coverage → call API → fall back to proxy if needed), but it's not explicitly sequenced with numbered steps or validation checkpoints. The coverage verification step is mentioned but not integrated into a clear workflow with error handling feedback loops. | 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 official docs. Content is appropriately split between this overview and referenced 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.