liantis
Liantis 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 Liantis. Routes through Apideck with serviceId "liantis".
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 integration target (Liantis via Apideck HRIS), lists specific data entities (employees, departments, payrolls, time-off records), and provides an explicit 'Use when' clause with natural trigger terms. The mention of serviceId and the unified API pattern adds helpful technical context for disambiguation.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'read or sync employees, departments, payrolls, and time-off records' and explains the integration mechanism (Apideck's HRIS unified API, serviceId switching). | 3 / 3 |
Completeness | Clearly answers both 'what' (Liantis integration via Apideck HRIS unified API for 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 Liantis'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Liantis', 'employees', 'departments', 'payrolls', 'time-off records', 'HRIS', 'Apideck', 'serviceId'. Covers both the platform name and the data entities a user would reference. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific platform name 'Liantis' and the serviceId 'liantis', plus the Apideck HRIS context. Unlikely to conflict with other skills unless there are other Liantis-specific integrations. | 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 (marketing-style content about portability and the 'compounding advantage' of Apideck) and a workflow that could be more explicitly sequenced, especially given the beta status and the need to verify coverage before making calls.
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 an explicit numbered workflow: 1. Verify coverage → 2. Call unified API → 3. Handle UnsupportedOperationError → 4. Fall back to Proxy API, with a clear decision checkpoint after step 1.
Trim the 'When to use this skill' section to just the serviceId and API references — Claude doesn't need to be told when to activate a skill in this much detail.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary verbosity — the 'Portable across 58 HRIS connectors' section repeats the marketing pitch already stated in the intro, and the 'When to use this skill' section over-explains activation triggers Claude doesn't need. The 'compounding advantage' paragraph is pure sales copy. 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. All examples are copy-paste ready with clear environment variable references. | 3 / 3 |
Workflow Clarity | There's an implicit workflow (check coverage → use unified API → fall back to proxy), 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 decision flow with error handling feedback loops. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure — the skill provides a concise overview with well-signaled one-level-deep references to SDK skills, best practices, connector coverage, and the OpenAPI spec. Content is appropriately split between this overview and linked 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.