folks-hr
Folks 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 Folks HR. Routes through Apideck with serviceId "folks-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 (Folks HR via Apideck), lists concrete data entities it handles, and provides an explicit 'Use when' clause with natural trigger terms. The mention of serviceId and the Apideck routing mechanism adds technical precision that aids distinctiveness. Minor improvement could include mentioning write operations if supported, but overall this is well-crafted.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'read or sync employees, departments, payrolls, and time-off records' and mentions the integration mechanism (Apideck's HRIS unified API, serviceId). These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (Folks HR 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 Folks HR'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Folks HR', 'employees', 'departments', 'payrolls', 'time-off records', 'HRIS', 'Apideck', and 'folks-hr'. Good coverage of both the product name and the data entities a user would reference. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific product name 'Folks HR', the serviceId 'folks-hr', and the Apideck routing mechanism. Unlikely to conflict with other HR skills since it clearly scopes to a specific connector and service. | 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 moderate verbosity from marketing-style language about Apideck's portability advantages and a lack of explicit workflow sequencing 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 speaks for itself.
Add an explicit numbered workflow (e.g., 1. Verify connection state 2. Check coverage 3. Call unified API 4. If UnsupportedOperationError, use proxy) with validation checkpoints to improve workflow clarity.
| 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 Folks HR 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 escape hatch with real headers. All examples are copy-paste ready with clear variable placeholders. | 3 / 3 |
Workflow Clarity | The skill implicitly sequences a workflow (authenticate → verify coverage → call API → use proxy if needed) but doesn't present it as an explicit ordered workflow with validation checkpoints. The coverage verification step is mentioned but not integrated into a clear 'before you call, verify' feedback loop. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a concise overview and well-signaled one-level-deep references to SDK skills, best practices, connector coverage, and the OpenAPI spec. The 'See also' section provides clear navigation without nesting references more than one level 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.