acerta
Acerta 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 Acerta. Routes through Apideck with serviceId "acerta".
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 (Acerta via Apideck HRIS), lists concrete data entities it handles, and provides an explicit 'Use when' clause with natural trigger terms. The mention of serviceId switching and the specific connector name make it highly distinguishable from similar HRIS integration skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'read or sync employees, departments, payrolls, and time-off records in Acerta' and mentions the unified API mechanism with serviceId switching. | 3 / 3 |
Completeness | Clearly answers both 'what' (Acerta integration via Apideck's 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 Acerta'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Acerta', 'employees', 'departments', 'payrolls', 'time-off records', 'HRIS', 'Apideck', 'serviceId'. These cover the domain well and match what users working with Acerta/HRIS would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive by specifying 'Acerta' as the target system and 'serviceId "acerta"' as the routing mechanism. This clearly differentiates it from other Apideck HRIS connectors that would use different serviceIds. | 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 and excellent progressive disclosure to related skills. Its main weaknesses are verbosity from marketing-style content (portability pitch repeated multiple times) and a lack of explicit workflow sequencing for what is a beta connector requiring coverage verification before use. Trimming the sales copy and adding a clear numbered 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 an explicit numbered workflow: 1. Ensure Vault connection is authorized → 2. Verify coverage for the target resource → 3. Call unified API → 4. Handle UnsupportedOperationError by falling back to Proxy API. This is especially important given the beta status.
Trim the 'When to use this skill' section — Claude doesn't need to be told when to activate a skill in this much detail; the description metadata already covers this.
| 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 Acerta directly' are sales copy rather than actionable guidance. 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 curl example for the Proxy API escape hatch. All examples include proper headers, environment variables, and the correct serviceId. These are copy-paste ready. | 3 / 3 |
Workflow Clarity | There's an implicit workflow (authenticate → verify coverage → call unified API → fall back to proxy if unsupported), but it's never presented as a clear sequence with validation checkpoints. The coverage verification step is mentioned but not integrated into a numbered workflow. For a connector marked as beta with 'partial resource coverage and occasional mapping gaps,' a clearer workflow with error handling steps 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, the OpenAPI spec, 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.