deel
Deel 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 Deel. Routes through Apideck with serviceId "deel".
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 description that clearly identifies the integration (Deel via Apideck HRIS), lists specific data entities (employees, departments, payrolls, time-off records), and provides explicit trigger guidance. The technical context about serviceId and unified API adds useful disambiguation without being overly jargon-heavy. It uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'read or sync employees, departments, payrolls, and time-off records in Deel.' Also mentions the technical mechanism (Apideck's HRIS unified API, serviceId). | 3 / 3 |
Completeness | Clearly answers both what ('read or sync employees, departments, payrolls, and time-off records in Deel via Apideck HRIS unified API') and when ('Use when the user wants to read or sync employees, departments, payrolls, and time-off records in Deel'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Deel', 'employees', 'departments', 'payrolls', 'time-off records', 'HRIS', 'Apideck', 'sync'. Good coverage of domain-specific terms a user would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — specifically targets Deel via Apideck with serviceId 'deel'. The combination of Deel + Apideck + HRIS + specific entity types creates a clear niche unlikely to conflict with other skills. | 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 good actionability through executable examples and a clear entity mapping table. Its main weakness is verbosity — the portability value proposition is repeated multiple times and marketing-style language wastes tokens. The workflow could benefit from error handling guidance, especially around the Proxy API escape hatch.
Suggestions
Remove the redundant 'Portable across 58 HRIS connectors' section — the intro already establishes portability, and the sibling connectors section reinforces it. The code example showing serviceId swapping could be folded into the minimal example.
Add error handling or validation guidance for the Proxy API escape hatch (e.g., check response status, handle auth failures), since calling downstream APIs through a proxy is a fragile operation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary verbosity — the 'Portable across 58 HRIS connectors' section repeats the portability pitch already made in the intro, and the 'When to use this skill' section explains obvious activation triggers. The marketing-style language ('compounding advantage') wastes tokens. However, the entity mapping table and coverage highlights are efficient. | 2 / 3 |
Actionability | Provides fully executable TypeScript examples with proper imports, environment variable usage, and the correct serviceId. The Proxy API escape hatch includes a complete curl command with all required headers. The entity mapping table gives concrete guidance on what's supported vs. what requires fallback. | 3 / 3 |
Workflow Clarity | The skill covers a relatively simple task (API calls with a serviceId), but for the Proxy API fallback workflow there's no validation step — no guidance on checking response status, handling errors, or verifying that the proxy call succeeded. The 'When to use this skill' section lists steps but they're more about skill selection than operational workflow. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear one-level-deep references to SDK skills, OpenAPI specs, best practices, and connector coverage tools. The 'See also' section is well-organized. Content is appropriately split between this overview and referenced materials for full method surfaces and patterns. | 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.