breathehr
Breathe 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 Breathe HR. Routes through Apideck with serviceId "breathehr".
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 (Breathe HR via Apideck), 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 without sacrificing clarity.
| 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). These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (Breathe 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 Breathe HR'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Breathe HR', 'employees', 'departments', 'payrolls', 'time-off records', 'HRIS', 'Apideck', 'breathehr'. Good coverage of both product names and domain terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific product name 'Breathe HR' and the serviceId 'breathehr'. The description also clarifies the Apideck/HRIS unified API context and how it differs from other connectors (by changing serviceId), making it clearly distinguishable. | 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. Its main weaknesses are verbosity from marketing-style content (portability pitch repeated multiple times) and a lack of explicit error handling or validation checkpoints in the workflow. Trimming the promotional language and adding a brief error handling pattern would significantly improve it.
Suggestions
Remove or consolidate the repeated portability pitch — the 'Portable across 58 HRIS connectors' section largely duplicates the intro paragraph and the code example could be folded into the minimal example section.
Add a brief error handling example showing how to handle common failures (e.g., UnsupportedOperationError, auth failures) inline rather than only deferring to other skills.
Trim the 'When to use this skill' section — Claude doesn't need to be told when to activate a skill in this much detail; a single sentence suffices.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary verbosity — the 'Portable across 58 HRIS connectors' section repeats the marketing pitch from the intro, the 'When to use this skill' section over-explains activation triggers, and phrases like 'This is the compounding advantage of using Apideck over integrating Breathe HR directly' are sales copy that wastes tokens. However, the core technical content is reasonably 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 patterns. | 3 / 3 |
Workflow Clarity | The skill presents a reasonable sequence (authenticate → call unified API → verify coverage → use proxy if needed), but lacks explicit validation checkpoints. There's no guidance on what to do when calls fail, no error handling examples, and the coverage verification step is presented as a separate section rather than integrated into a workflow with 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, and the OpenAPI spec. The 'See also' section provides clear navigation, and references are consistently formatted with relative links. | 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.