adp-ihcm
ADP iHCM 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 ADP iHCM. Routes through Apideck with serviceId "adp-ihcm".
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 (ADP iHCM via Apideck), lists concrete data entities it handles, and provides explicit 'Use when' guidance. The description is concise, uses third person voice, and includes enough domain-specific terms to be both discoverable and distinguishable from other HRIS connector skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'read or sync employees, departments, payrolls, and time-off records in ADP iHCM'. Also mentions the unified API pattern and serviceId switching mechanism. | 3 / 3 |
Completeness | Clearly answers both what ('read or sync employees, departments, payrolls, and time-off records via Apideck's HRIS unified API') and when ('Use when the user wants to read or sync employees, departments, payrolls, and time-off records in ADP iHCM') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'ADP iHCM', 'employees', 'departments', 'payrolls', 'time-off records', 'Apideck', 'HRIS', 'sync'. These cover the domain well and match how users would phrase requests. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific triggers: 'ADP iHCM', 'serviceId adp-ihcm', and 'Apideck HRIS unified API'. The mention of the specific connector and serviceId makes it clearly distinguishable from other HRIS integration skills. | 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 marketing-style verbosity (the portability pitch is repeated multiple times) and a lack of explicit workflow sequencing for the verify-coverage-then-call-or-fallback pattern, which is especially important given the beta status of this connector.
Suggestions
Remove or condense the 'Portable across 58 HRIS connectors' section — the intro already explains portability, and the code example showing serviceId swapping could be folded into the minimal example as a one-line comment.
Add an explicit numbered workflow: 1. Verify coverage → 2. Call unified API → 3. Handle UnsupportedOperationError → 4. Fall back to Proxy API, with a validation checkpoint after step 1.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes 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 factual sections are reasonably tight. | 2 / 3 |
Actionability | Provides fully executable TypeScript code for listing employees, a concrete curl command for verifying coverage, and a complete proxy API curl example with all required headers. The serviceId, auth type, and SDK references are all specific and copy-paste ready. | 3 / 3 |
Workflow Clarity | There's an implicit workflow (check coverage → use unified API → fall back to proxy if unsupported), but it's never presented as a clear numbered sequence with validation checkpoints. The connection lifecycle states are mentioned but not sequenced into actionable steps. For a beta connector where coverage gaps are expected, a clearer verify-then-act workflow with error handling would be important. | 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 patterns, OpenAPI specs, and sibling connectors. 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.