paylocity
Paylocity 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 Paylocity. Routes through Apideck with serviceId "paylocity".
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 (Paylocity 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 differentiation helps distinguish it from other potential HRIS connector skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: read or sync employees, departments, payrolls, and time-off records. Also specifies the integration mechanism (Apideck's HRIS unified API) and the serviceId parameter. | 3 / 3 |
Completeness | Clearly answers both 'what' (Paylocity integration via Apideck's HRIS unified API for reading/syncing employees, departments, payrolls, time-off records) and 'when' (explicit 'Use when the user wants to read or sync employees, departments, payrolls, and time-off records in Paylocity'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Paylocity', 'employees', 'departments', 'payrolls', 'time-off records', 'HRIS', 'Apideck', 'serviceId'. These cover the domain well and match what users would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — specifically targets Paylocity via Apideck with serviceId 'paylocity'. The mention that the same methods work across HRIS connectors but are distinguished by serviceId makes it clear when this skill applies versus other HRIS connector 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 weakness is verbosity — marketing-style explanations about Apideck's unified API advantages and redundant portability sections inflate the token count without adding instructional value. The workflow could benefit from an explicit sequence showing connection verification before API calls.
Suggestions
Remove or drastically shorten the 'Portable across 58 HRIS connectors' section — the intro already explains portability, and the code comparison is redundant with the minimal example.
Trim the 'When to use this skill' section to just the activation trigger and SDK references; the numbered list explaining what the skill teaches is meta-commentary Claude doesn't need.
Add a brief inline workflow sequence: 1) verify connection is callable, 2) make API call, 3) handle UnsupportedOperationError → fall back to proxy, rather than deferring all error handling to external skills.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary verbosity — the 'Portable across 58 HRIS connectors' section repeats the marketing pitch from the intro, and phrases like 'This is the compounding advantage of using Apideck over integrating Paylocity directly' are sales copy that Claude doesn't need. The 'When to use this skill' section also over-explains. However, the code examples and quick facts are lean. | 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 specific and copy-paste ready. | 3 / 3 |
Workflow Clarity | The skill covers multiple operations (list employees, verify coverage, proxy fallback) but doesn't present them as a sequenced workflow with validation checkpoints. There's no explicit 'verify connection state before calling' step or error-handling feedback loop — it defers to external skills for that. For operations involving API calls that could fail, missing inline validation caps this at 2. | 2 / 3 |
Progressive Disclosure | Excellent use of one-level-deep references to sibling skills (apideck-best-practices, apideck-connector-coverage, SDK skills) with clear signaling of what each contains. The main content stays as an overview with minimal examples, and detailed patterns are properly delegated to referenced files. | 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.