namely
Namely 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 Namely. Routes through Apideck with serviceId "namely".
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 (Namely via Apideck), lists concrete data entities (employees, departments, payrolls, time-off records), and includes an explicit 'Use when' clause with natural trigger terms. The description is concise, uses third-person voice, and provides enough technical context (serviceId, unified API) to distinguish it from similar HRIS integrations.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'read or sync employees, departments, payrolls, and time-off records in Namely' and mentions the integration mechanism (Apideck's HRIS unified API, serviceId). | 3 / 3 |
Completeness | Clearly answers both 'what' (read/sync employees, departments, payrolls, time-off records via Apideck HRIS API) and 'when' (explicit 'Use when the user wants to read or sync employees, departments, payrolls, and time-off records in Namely'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Namely', 'employees', 'departments', 'payrolls', 'time-off records', 'HRIS', 'Apideck', 'sync'. These cover the domain well and match how users would phrase requests. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a specific service ('Namely') via a specific integration platform ('Apideck') with a specific serviceId. Unlikely to conflict with other skills unless there are multiple Namely integrations. | 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 Apideck skills. Its main weaknesses are marketing-style verbosity (portability pitch repeated multiple times) and a lack of explicit workflow sequencing for the connection verification → API call → error handling pipeline. Trimming the promotional content and adding a brief ordered workflow would significantly improve it.
Suggestions
Remove or consolidate the 'Portable across 58 HRIS connectors' section — the portability point is already made in the intro and the code example can be folded into the minimal example section.
Add a brief ordered workflow: 1) Verify connection state is 'callable', 2) Check coverage for needed operations, 3) Make API calls, 4) Handle UnsupportedOperationError with proxy fallback — with explicit validation checkpoints.
Trim the 'When to use this skill' section to just the serviceId and API surface info; Claude doesn't need activation trigger explanations.
| 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 Namely directly' are marketing copy that wastes tokens. 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. All examples are copy-paste ready with clear environment variable references. | 3 / 3 |
Workflow Clarity | The skill covers multiple operations (list employees, verify coverage, proxy fallback) but doesn't sequence them into a clear workflow with validation checkpoints. There's no explicit 'check connection state before calling' step or error handling flow — it defers to external skills for that. For operations involving API calls that could fail (coverage gaps, auth issues), inline validation steps are missing. | 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, and the OpenAPI spec. The 'See also' section provides clear navigation to related resources 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.