lucca-hr
Lucca 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 Lucca. Routes through Apideck with serviceId "lucca-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 (Lucca via Apideck HRIS), lists concrete data entities it handles (employees, departments, payrolls, time-off records), and provides an explicit 'Use when' clause with natural trigger terms. The mention of serviceId 'lucca-hr' and the Apideck routing mechanism adds technical precision that aids distinctiveness. Minor improvement could include mentioning file formats or specific API operations (create, update, delete) if supported.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'read or sync employees, departments, payrolls, and time-off records in Lucca' and mentions the unified API mechanism with serviceId. Also explains the Apideck routing pattern. | 3 / 3 |
Completeness | Clearly answers both 'what' (Lucca 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 Lucca'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Lucca', 'employees', 'departments', 'payrolls', 'time-off records', 'HRIS', 'Apideck', 'lucca-hr'. Good coverage of domain-specific terms a user would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — specifically targets Lucca via Apideck with serviceId 'lucca-hr'. The combination of the specific service (Lucca), the platform (Apideck), and the serviceId makes it very unlikely to conflict with 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 actionability (executable code examples) and excellent progressive disclosure to related skills and references. Its main weaknesses are moderate verbosity from marketing-style content about Apideck's portability advantage and missing inline validation/error-handling steps that would strengthen the workflow.
Suggestions
Remove or drastically shorten the 'Portable across 58 HRIS connectors' section — the portability point is already made in the intro and the code example speaks for itself.
Add inline guidance on what to check in the coverage response and how to handle UnsupportedOperationError, rather than fully deferring to another skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary verbosity — the 'Portable across 58 HRIS connectors' section repeats the marketing pitch from the intro, and the 'When to use this skill' section over-explains activation triggers. The 'compounding advantage' paragraph is pure 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 setup, and SDK import are all copy-paste ready. | 3 / 3 |
Workflow Clarity | The skill presents a reasonable sequence (authenticate → list employees → verify coverage → use proxy as escape hatch), but there are no explicit validation checkpoints or error-handling feedback loops. The 'Verifying coverage' section mentions checking before assuming but doesn't show what to do with the response or how to handle UnsupportedOperationError inline — it defers to another skill. | 2 / 3 |
Progressive Disclosure | Excellent structure with a concise overview, minimal inline content, 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 multiple levels 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.