bamboohr
BambooHR 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 BambooHR. Routes through Apideck with serviceId "bamboohr".
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 (BambooHR via Apideck HRIS unified API), lists concrete data entities it handles, and provides explicit trigger guidance. The description is concise, uses third person voice, and includes enough technical detail (serviceId) to distinguish it from similar HRIS integration skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'read or sync employees, departments, payrolls, and time-off records in BambooHR.' Also mentions the integration mechanism (Apideck's HRIS unified API) and the serviceId pattern. | 3 / 3 |
Completeness | Clearly answers both 'what' (BambooHR integration via Apideck's HRIS unified API for reading/syncing employees, departments, payrolls, time-off records) and 'when' (explicit 'Use when the user wants to read or sync employees, departments, payrolls, and time-off records in BambooHR'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'BambooHR', 'employees', 'departments', 'payrolls', 'time-off records', 'HRIS', 'Apideck'. These cover the main terms a user would naturally use when requesting BambooHR-related tasks. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically targets BambooHR via Apideck with serviceId 'bamboohr'. The mention of the specific connector and serviceId pattern makes it very unlikely to conflict with other skills, even other HRIS 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 through executable code examples and excellent progressive disclosure via clear cross-references to SDK skills and specs. Its main weaknesses are moderate verbosity from repeated marketing messaging about Apideck's unified API advantage, and missing error-handling/validation guidance for operations that could fail (especially around the documented permission issues with sensitive fields).
Suggestions
Remove or condense the 'Portable across 58 HRIS connectors' section — the intro already explains portability, and the code example showing serviceId swaps could be folded into the minimal example as a one-line comment.
Add error handling to the pagination sync example showing how to detect and handle 403s from insufficient API key permissions, since this is called out as a known BambooHR quirk.
| 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 BambooHR directly' are sales copy Claude doesn't need. The entity mapping table and coverage highlights are valuable, but the 'When to use this skill' section over-explains activation context. | 2 / 3 |
Actionability | Provides fully executable TypeScript examples for listing employees, paginated sync with custom fields, approving time-off requests, and a curl-based proxy escape hatch. Code is copy-paste ready with real parameter names and environment variable references. | 3 / 3 |
Workflow Clarity | The skill covers multiple operations but lacks explicit validation checkpoints — there's no guidance on verifying API responses, handling 403s from insufficient permissions (mentioned as a known issue but no error-handling code), or retry logic. The pagination example is clear but doesn't handle errors mid-sync. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a concise overview, clear references to SDK-specific skills (apideck-node, apideck-python, etc.), links to OpenAPI specs, sibling connectors, and a well-organized 'See also' section. All references are one level deep and clearly signaled. | 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.