justworks
Justworks 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 Justworks. Routes through Apideck with serviceId "justworks".
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 (Justworks via Apideck HRIS), lists concrete data entities (employees, departments, payrolls, time-off records), and provides an explicit 'Use when' clause with natural trigger terms. The mention of serviceId switching pattern adds useful context for distinguishing this from sibling connector skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'read or sync employees, departments, payrolls, and time-off records' and mentions the integration mechanism (Apideck's HRIS unified API, serviceId). Also explains the cross-connector pattern. | 3 / 3 |
Completeness | Clearly answers both 'what' (Justworks integration via Apideck HRIS unified API for 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 Justworks'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Justworks', 'employees', 'departments', 'payrolls', 'time-off records', 'HRIS', 'Apideck', and 'serviceId'. These cover the domain well and match what users would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific mention of 'Justworks' and 'serviceId "justworks"', clearly distinguishing it from other HRIS connector skills that would use different serviceIds. The Apideck/Justworks combination creates a clear 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 actionability and excellent progressive disclosure to related skills and specs. Its main weaknesses are some marketing-style verbosity (portability pitch repeated twice, unnecessary explanatory prose) and a lack of explicit workflow sequencing with validation checkpoints for the multi-step process of connecting to and using the Justworks API.
Suggestions
Remove the 'Portable across 58 HRIS connectors' section or collapse it into a single sentence in the intro — the portability point is already made in the opening paragraph and the code example speaks for itself.
Add an explicit numbered workflow (e.g., 1. Set up Vault connection → 2. Verify coverage → 3. Call unified API → 4. If UnsupportedOperationError, use Proxy) with validation checkpoints at each step.
Trim the 'When to use this skill' section to 1-2 lines — Claude doesn't need examples of user utterances or a numbered list explaining what the skill teaches.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary verbosity — the 'Portable across 58 HRIS connectors' section repeats the portability pitch already made in the intro, and phrases like 'This is the compounding advantage of using Apideck over integrating Justworks directly' are marketing copy that wastes tokens. The 'When to use this skill' section also over-explains when activation is appropriate. | 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, SDK import, and environment variables are all specified — copy-paste ready. | 3 / 3 |
Workflow Clarity | The skill implicitly sequences a workflow (authenticate → verify coverage → call API → use proxy if needed) but doesn't present it as an explicit ordered workflow with validation checkpoints. The coverage verification step is mentioned but not integrated into a clear 'do this before calling' sequence, and there's no error recovery loop for failed API calls. | 2 / 3 |
Progressive Disclosure | Excellent use of one-level-deep references to sibling skills (apideck-node, apideck-best-practices, apideck-connector-coverage) and external resources (OpenAPI spec, API Explorer). The main file stays as an overview with clear signposting to detailed materials, and no nested reference chains. | 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.