homerun-hr
Homerun HR 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 Homerun HR. Routes through Apideck with serviceId "homerun-hr".
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 (Homerun HR via Apideck HRIS unified API), lists concrete data entities it handles (employees, departments, payrolls, time-off records), and includes an explicit 'Use when' clause with natural trigger terms. The description is concise, uses third-person voice, and is well-differentiated from other potential HRIS connector skills by naming the specific service and serviceId.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'read or sync employees, departments, payrolls, and time-off records in Homerun HR.' Also mentions the technical 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 Homerun HR'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'employees', 'departments', 'payrolls', 'time-off records', 'Homerun HR', 'HRIS', 'Apideck', 'sync'. Good coverage of domain-specific terms a user would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — specifically targets 'Homerun HR' with serviceId 'homerun-hr' via Apideck, clearly distinguishing it from other HRIS connectors or HR tools. The mention of switching by serviceId further clarifies its niche within a family of similar 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 moderate verbosity (marketing language and repeated portability messaging) and a lack of explicit workflow sequencing for the coverage-check-then-call-or-fallback pattern. Trimming the sales pitch and adding a numbered workflow would meaningfully improve it.
Suggestions
Remove or condense the 'Portable across 58 HRIS connectors' section — the portability point is already made in the intro and the code example speaks for itself.
Add an explicit numbered workflow: 1. Verify coverage → 2. Call unified API → 3. Handle UnsupportedOperationError → 4. Fall back to Proxy API, with validation at each step.
Trim the 'When to use this skill' section to 1-2 lines — Claude doesn't need to be told when to activate a skill in this much detail.
| 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 Homerun HR directly' are sales copy that wastes tokens. 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 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 an explicit sequence with validation checkpoints. The beta status warning mentions verifying coverage but doesn't integrate this into a clear step-by-step process with error handling feedback loops. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure — concise overview with well-signaled one-level-deep references to SDK skills, best practices, connector coverage, OpenAPI specs, and sibling connectors. Content is appropriately split between this skill 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.