ciphr
CIPHR 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 CIPHR. Routes through Apideck with serviceId "ciphr".
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 (CIPHR via Apideck HRIS API), 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 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. Also mentions specific technical details like serviceId, Apideck unified API, and HRIS connectors. | 3 / 3 |
Completeness | Clearly answers both what ('read or sync employees, departments, payrolls, and time-off records in CIPHR via Apideck's HRIS unified API') and when ('Use when the user wants to read or sync employees, departments, payrolls, and time-off records in CIPHR'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'CIPHR', 'employees', 'departments', 'payrolls', 'time-off records', 'HRIS', 'Apideck', 'sync employees'. These cover the main terms a user working with CIPHR HR data would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific product name 'CIPHR', the specific serviceId 'ciphr', and the Apideck routing context. This is unlikely to conflict with other skills unless there are other CIPHR-specific skills, and the serviceId differentiator makes it clear. | 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 resources. Its main weaknesses are moderate verbosity (marketing-style language about Apideck's advantages, restating obvious context) and a lack of explicit workflow sequencing with validation checkpoints for the beta connector's coverage verification process.
Suggestions
Remove the 'compounding advantage' paragraph and the explanatory text in 'When to use this skill' section — Claude doesn't need to be sold on Apideck's value proposition or told when to activate the skill in such detail.
Add an explicit numbered workflow: 1) Verify coverage → 2) Handle UnsupportedOperationError → 3) Fall back to Proxy API, with a clear validation checkpoint after the coverage check.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary verbosity — e.g., explaining what Apideck does ('handles auth, pagination, rate limiting, and retries'), the 'compounding advantage' paragraph, and the 'When to use this skill' section which restates obvious context. However, it's not egregiously padded and the quick facts table is efficient. | 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 substitution. | 3 / 3 |
Workflow Clarity | There's an implicit workflow (connect → verify coverage → use unified API or fall back to proxy), but it's not presented as a clear sequence with validation checkpoints. The beta status warning mentions verifying coverage but doesn't integrate this into a step-by-step workflow with error handling feedback loops. | 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, OpenAPI specs, and sibling connectors. Content is appropriately split between this file and referenced materials. | 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.