jumpcloud
JumpCloud 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 JumpCloud. Routes through Apideck with serviceId "jumpcloud".
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 (JumpCloud via Apideck HRIS), lists concrete data entities it handles, and provides an explicit 'Use when' clause with natural trigger terms. The mention of serviceId and the unified API pattern adds helpful technical context for disambiguation from other Apideck HRIS connectors.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: read/sync employees, departments, payrolls, and time-off records. Also specifies the integration mechanism (Apideck's HRIS unified API) and the serviceId parameter. | 3 / 3 |
Completeness | Clearly answers both 'what' (JumpCloud integration via Apideck 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 JumpCloud'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'JumpCloud', 'employees', 'departments', 'payrolls', 'time-off records', 'HRIS', 'Apideck', 'sync'. These cover the main terms a user working with JumpCloud HR data would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific combination of JumpCloud + Apideck + serviceId 'jumpcloud'. The mention of switching by serviceId also clarifies its niche within a family of similar Apideck HRIS skills, reducing conflict risk. | 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 solid connector-specific skill with good actionability (executable code examples, concrete curl commands) and excellent progressive disclosure (clear references to SDK skills, best practices, and specs). Its main weaknesses are moderate verbosity from marketing-style content about Apideck's portability advantages and a lack of explicit workflow sequencing with validation checkpoints for the setup-to-usage flow.
Suggestions
Remove or significantly trim the 'Portable across 58 HRIS connectors' section — the portability point is already made in the intro and the code example speaks for itself.
Restructure the implicit workflow (auth setup → verify coverage → call API → handle errors/proxy fallback) into an explicit numbered sequence with decision points, e.g., 'If coverage check shows unsupported → use Proxy API'.
Trim the 'When to use this skill' section to 1-2 lines — Claude doesn't need detailed activation trigger explanations.
| 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 JumpCloud directly' are sales copy rather than actionable instruction. However, the quick facts table and code examples are reasonably tight. | 2 / 3 |
Actionability | The skill provides fully executable TypeScript code for listing employees, a concrete curl command for verifying coverage, and a complete proxy API escape hatch with all required headers. The serviceId, auth type, and SDK imports are all copy-paste ready. | 3 / 3 |
Workflow Clarity | There's an implicit workflow (configure auth → verify coverage → call unified API → fall back to proxy if needed), 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 feedback loops. | 2 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-signaled one-level-deep references to SDK skills, best practices, connector coverage, and the OpenAPI spec. Content is appropriately split — detailed SDK patterns, Vault setup, and coverage checking are delegated to separate skill files with clear links. | 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.