payfit
PayFit 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 PayFit. Routes through Apideck with serviceId "payfit".
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 (PayFit via Apideck HRIS), lists concrete data entities it handles, and provides an explicit 'Use when' clause with natural trigger terms. The inclusion of the serviceId and the note about the unified API pattern further aids distinctiveness and practical understanding.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'read or sync employees, departments, payrolls, and time-off records in PayFit.' Also mentions the technical mechanism (Apideck's HRIS unified API, serviceId). | 3 / 3 |
Completeness | Clearly answers both what ('read or sync employees, departments, payrolls, and time-off records in PayFit via Apideck HRIS unified API') and when ('Use when the user wants to read or sync employees, departments, payrolls, and time-off records in PayFit'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'PayFit', 'employees', 'departments', 'payrolls', 'time-off records', 'HRIS', 'Apideck', 'sync'. Good coverage of domain-specific terms a user would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — specifically targets PayFit via Apideck with serviceId 'payfit'. The mention that 'same methods work across every connector in HRIS, switch by changing serviceId' clarifies its niche relative to other HRIS connectors, making it clearly distinguishable. | 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-specific skill with strong actionability and excellent progressive disclosure to related skills. Its main weaknesses are redundant marketing-style content about portability (stated three times in different ways) and a lack of explicit workflow sequencing for the verify-then-call-then-fallback pattern. Trimming the repeated portability messaging and adding a concise 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 paragraph and the sibling connectors section. The code example showing serviceId switching is redundant with the minimal example.
Add a concise numbered workflow: 1. Verify connection state is 'callable', 2. Check coverage for the target method, 3. Call the unified API, 4. If UnsupportedOperationError → use proxy API fallback.
Trim the 'When to use this skill' section to just the numbered list — Claude doesn't need example trigger phrases like 'sync employees in PayFit'.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary verbosity — the 'Portable across 58 HRIS connectors' section repeats the portability point already made in the intro and the code example is redundant. The 'compounding advantage' paragraph is marketing copy that wastes tokens. The 'When to use this skill' section 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 curl example with all required headers. The serviceId, auth type, and SDK references are all specific and actionable. | 3 / 3 |
Workflow Clarity | The skill implicitly describes a workflow (authenticate → verify coverage → call API → fallback to proxy), but it's not presented as a clear sequence with validation checkpoints. There's no explicit step-by-step process for handling UnsupportedOperationError or verifying connection state before making calls — these are deferred to other skills. | 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 'See also' section provides well-organized navigation. Content is appropriately split between this connector-specific skill and the shared pattern skills. | 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.