cascade-hr
IRIS Cascade 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 IRIS Cascade HR. Routes through Apideck with serviceId "cascade-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 system (IRIS Cascade HR), the integration platform (Apideck HRIS unified API), concrete actions (read/sync employees, departments, payrolls, time-off records), and explicit trigger conditions. The serviceId detail further aids disambiguation from other similar Apideck HRIS skills. Minor improvement could be made by listing file formats or API endpoints, but overall this is well-crafted.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'read or sync employees, departments, payrolls, and time-off records' and mentions the integration mechanism (Apideck's HRIS unified API, serviceId). Very concrete about what it does. | 3 / 3 |
Completeness | Clearly answers both 'what' (IRIS Cascade HR integration via Apideck for reading/syncing employees, departments, payrolls, time-off) and 'when' ('Use when the user wants to read or sync employees, departments, payrolls, and time-off records in IRIS Cascade HR'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'IRIS Cascade HR', 'employees', 'departments', 'payrolls', 'time-off records', 'HRIS', 'Apideck', 'cascade-hr'. Good coverage of both product names and domain terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a specific HR system (IRIS Cascade HR) with a specific serviceId ('cascade-hr') and specific API platform (Apideck). The mention that 'same methods work across every connector' and switching by 'serviceId' helps distinguish it from other Apideck HRIS connectors. | 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 progressive disclosure and actionable code examples. Its main weaknesses are some promotional/marketing verbosity that doesn't serve Claude's needs, and a lack of explicit workflow sequencing with validation checkpoints for the connect-verify-call pattern. The skill effectively serves as a routing document pointing to deeper resources.
Suggestions
Remove the promotional paragraph in 'Portable across 58 HRIS connectors' ('This is the compounding advantage...') and trim the intro's marketing language — Claude doesn't need to be sold on Apideck.
Add an explicit numbered workflow: 1. Verify connection state is 'callable', 2. Check coverage for needed operations, 3. Call unified API, 4. If UnsupportedOperationError → use proxy escape hatch, with clear validation at each step.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary verbosity — the 'Portable across 58 HRIS connectors' section repeats the marketing pitch from the intro, and phrases like 'This is the compounding advantage of using Apideck over integrating IRIS Cascade HR directly' are promotional filler Claude doesn't need. The 'When to use this skill' section also over-explains. 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 escape hatch with real headers. The serviceId, auth type, and SDK references are all specific and copy-paste ready. | 3 / 3 |
Workflow Clarity | There's an implicit workflow (connect → verify coverage → call API → use proxy if needed) but it's not explicitly sequenced with numbered steps or validation checkpoints. The coverage verification step is mentioned but not integrated into a clear workflow with error handling feedback loops (e.g., what to do if coverage check fails before making calls). | 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.