nmbrs
Visma Nmbrs 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 Visma Nmbrs. Routes through Apideck with serviceId "nmbrs".
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 (Visma Nmbrs via Apideck HRIS), lists concrete data entities it handles, and provides explicit trigger guidance with a 'Use when' clause. The description is concise, uses third person voice, and includes enough distinctive terms to avoid conflicts with other skills.
| 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' (Visma Nmbrs 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 Visma Nmbrs'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Visma Nmbrs', 'employees', 'departments', 'payrolls', 'time-off records', 'HRIS', 'Apideck', 'sync', and the technical identifier 'nmbrs'. Good coverage of both product names and domain terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific product names (Visma Nmbrs, Apideck), a specific serviceId ('nmbrs'), and a clear niche (HRIS integration). Very unlikely to conflict with other skills unless there are other Apideck HRIS connector skills, but the Visma Nmbrs specificity differentiates it. | 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 integration skill with strong actionability and excellent progressive disclosure to related skills and references. Its main weaknesses are moderate verbosity (marketing-style content about portability that Claude doesn't need) and a workflow that could be more explicitly sequenced with validation checkpoints, particularly around verifying coverage before making API calls.
Suggestions
Remove or drastically shorten the 'Portable across 58 HRIS connectors' section — the intro already explains portability, and the comparison code example adds little value beyond what's already shown.
Add an explicit numbered workflow: 1. Initialize SDK, 2. Verify coverage for target operation, 3. Call unified API, 4. If UnsupportedOperationError → use Proxy API 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 the 'When to use this skill' section over-explains activation triggers. The 'compounding advantage' paragraph is pure sales copy that wastes tokens. 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 coverage verification, and a complete proxy API curl example with all required headers. The serviceId, auth setup, and SDK initialization are all copy-paste ready. | 3 / 3 |
Workflow Clarity | There's an implicit workflow (set up auth → verify coverage → call API → use proxy as fallback) 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 for when operations are unsupported. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a concise overview and well-signaled one-level-deep references to SDK skills, best practices, connector coverage, OpenAPI specs, and sibling connectors. The 'See also' section provides clear navigation without nesting references multiple levels deep. | 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.