fourth
Fourth 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 Fourth. Routes through Apideck with serviceId "fourth".
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 (Fourth 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 and the Apideck unified API pattern further aids distinctiveness among potentially many similar connector skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'read or sync employees, departments, payrolls, and time-off records in Fourth' 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 unified API) and 'when' (explicit 'Use when the user wants to read or sync employees, departments, payrolls, and time-off records in Fourth'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Fourth', '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 — specifically targets 'Fourth' as the HRIS provider via Apideck with serviceId 'fourth'. This clearly distinguishes it from other HRIS connector skills that would use different serviceIds, and from non-HRIS skills entirely. | 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 references. Its main weaknesses are some marketing-style verbosity (portability pitch repeated, 'compounding advantage' paragraph) and a workflow that could be more explicitly sequenced with validation checkpoints for the coverage-check-then-call pattern.
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 duplicates the minimal example with different serviceIds.
Restructure the implicit workflow (verify coverage → call unified API → handle errors → fall back to proxy) as an explicit numbered sequence with decision points, similar to: 1. Verify coverage 2. If supported, call unified API 3. If UnsupportedOperationError, use Proxy API.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary verbosity — the 'Portable across 58 HRIS connectors' section repeats the portability pitch already made in the intro, and the 'When to use this skill' section explains obvious activation triggers. The 'compounding advantage' paragraph is marketing copy, not actionable guidance. However, the quick facts table and code examples are efficient. | 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 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 not presented as a clear numbered sequence with validation checkpoints. The coverage verification step exists but isn't integrated into a cohesive workflow with explicit decision points or error handling feedback loops. | 2 / 3 |
Progressive Disclosure | Excellent use of one-level-deep references: SDK skills, best practices, connector coverage, and OpenAPI specs are all clearly signaled with links. The skill serves as a concise overview that points to detailed materials 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.