keka
Keka 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 Keka HR. Routes through Apideck with serviceId "keka".
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 platform (Keka HR), the integration mechanism (Apideck HRIS unified API), concrete actions (read/sync employees, departments, payrolls, time-off records), and explicit trigger guidance. The description is concise, uses third person voice, and provides enough technical detail (serviceId) to distinguish it from similar HRIS integration skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'read or sync employees, departments, payrolls, and time-off records in Keka HR.' Also mentions technical details like unified API, serviceId, and Apideck routing. | 3 / 3 |
Completeness | Clearly answers both 'what' (Keka HR integration via Apideck's HRIS unified API for reading/syncing employees, departments, payrolls, time-off) and 'when' (explicit 'Use when the user wants to read or sync employees, departments, payrolls, and time-off records in Keka HR'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Keka HR', 'employees', 'departments', 'payrolls', 'time-off records', 'HRIS', 'Apideck', 'sync'. These cover the main terms a user working with Keka HR would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — specifically targets Keka HR via Apideck with serviceId 'keka'. The mention of the specific connector and serviceId makes it clearly distinguishable from other HRIS integrations or general HR 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 actionability and excellent progressive disclosure to related skills and documentation. Its main weaknesses are moderate verbosity (marketing-style portability explanations, unnecessary 'when to use' section) and a workflow that could be more explicitly sequenced with validation checkpoints for the coverage-check-then-call pattern.
Suggestions
Trim the 'Portable across 58 HRIS connectors' section — the portability point is already made in the intro and the code example alone suffices.
Remove or drastically shorten the 'When to use this skill' section — Claude can infer activation context from the skill description and content.
Present the coverage-check → unified-API-call → proxy-fallback flow as an explicit numbered workflow with validation steps (e.g., 'If coverage check shows unsupported, use Proxy API').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary verbosity — the 'Portable across 58 HRIS connectors' section is marketing-like and repeats the portability point already made in the intro. The 'When to use this skill' section explains things Claude can infer. However, the quick facts and code examples are reasonably tight. | 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. The serviceId, auth type, and setup steps 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 sequenced process with explicit validation checkpoints. The coverage verification step exists but isn't integrated into a numbered workflow with error recovery. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a concise overview in the skill itself 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 to related resources. | 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.