cezannehr
Cezanne 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 Cezanne HR. Routes through Apideck with serviceId "cezannehr".
75
71%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./connectors/cezannehr/SKILL.mdQuality
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 (Cezanne HR), the integration mechanism (Apideck HRIS unified API), concrete data entities (employees, departments, payrolls, time-off records), and explicit trigger guidance. It uses third-person voice appropriately and is concise without unnecessary padding.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'read or sync employees, departments, payrolls, and time-off records in Cezanne HR.' Also mentions the technical mechanism (Apideck's HRIS unified API, serviceId). | 3 / 3 |
Completeness | Clearly answers both 'what' (Cezanne 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 Cezanne HR'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Cezanne HR', 'employees', 'departments', 'payrolls', 'time-off records', 'HRIS', 'Apideck', and 'sync'. These cover the domain well and match how users would phrase requests. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — specifically targets Cezanne HR via Apideck with serviceId 'cezannehr'. The combination of the specific HR platform name and the routing mechanism makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill excels at progressive disclosure and navigation to related resources, but suffers from significant verbosity — marketing language, repeated concepts, and explanations of things Claude already knows (OAuth flows, what unified APIs are). The actionable content (code examples, curl commands) is solid but the skill functions more as a connector overview/routing document than a hands-on guide, with most real implementation details delegated to other skills.
Suggestions
Cut the 'Portable across 58 HRIS connectors' section entirely — the intro already states portability, and the sibling connectors section reinforces it. This saves ~15 lines of redundant marketing copy.
Remove the 'When to use this skill' section — Claude can infer activation conditions from the skill description and content. Replace with a single line if needed.
Trim the Authentication section to just the essentials: 'OAuth 2.0 managed by Apideck Vault. Users authorize via Vault modal. See [connection guide](URL) for setup and [`apideck-best-practices`] for Vault lifecycle.'
Present the coverage-check → unified API → proxy fallback as an explicit numbered workflow with a decision point, rather than spreading it across separate sections.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Significant verbosity throughout. The 'Portable across 58 HRIS connectors' section repeats the portability concept already stated in the intro. The 'When to use this skill' section explains obvious things Claude can infer. Marketing-style language ('compounding advantage') wastes tokens. The authentication section explains OAuth concepts Claude already knows. Much of this content is promotional rather than instructional. | 1 / 3 |
Actionability | The TypeScript example is executable and copy-paste ready, and the curl commands for coverage verification and proxy API are concrete. However, the skill mostly points to other skills for actual implementation details (SDK skills, best-practices, connector-coverage), making it more of a routing document than a self-contained actionable guide. Key details like actual Cezanne HR downstream URLs for the proxy are left as placeholders. | 2 / 3 |
Workflow Clarity | There's an implicit workflow: check coverage → use unified API → fall back to proxy if unsupported. However, this is never presented as a clear sequential workflow with validation checkpoints. The coverage verification step exists but isn't integrated into a coherent decision flow with explicit error handling or feedback loops. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure structure. The skill provides a concise overview with well-signaled one-level-deep references to SDK skills, best-practices, connector-coverage, OpenAPI specs, and external docs. Content is appropriately split between this overview and referenced materials. Navigation is clear with descriptive link labels. | 3 / 3 |
Total | 8 / 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.