azure-active-directory
Microsoft Entra 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 Microsoft Entra. Routes through Apideck with serviceId "azure-active-directory".
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 (Microsoft Entra via Apideck HRIS), lists concrete data entities (employees, departments, payrolls, time-off records), and provides explicit 'Use when' guidance with natural trigger terms. The inclusion of the serviceId and the note about switching connectors adds useful 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 specifies the integration mechanism (Apideck's HRIS unified API, serviceId). Also mentions switching connectors by changing serviceId. | 3 / 3 |
Completeness | Clearly answers both what ('read or sync employees, departments, payrolls, and time-off records in Microsoft Entra via Apideck HRIS unified API') and when ('Use when the user wants to read or sync employees, departments, payrolls, and time-off records in Microsoft Entra') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Microsoft Entra', 'employees', 'departments', 'payrolls', 'time-off records', 'HRIS', 'Apideck', 'azure-active-directory', 'sync'. Good coverage of both product names and domain terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive: targets a specific connector (Microsoft Entra / Azure Active Directory) through a specific platform (Apideck) with a specific serviceId. Unlikely to conflict with other skills unless there are other Entra-specific 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 solid connector-specific skill with excellent progressive disclosure and actionable code examples. Its main weaknesses are moderate verbosity from repeated marketing-style portability messaging and a workflow that could be more explicitly sequenced with validation checkpoints, especially given the beta status and partial coverage caveats.
Suggestions
Consolidate the portability messaging — the intro paragraph already covers it, so the 'Portable across 58 HRIS connectors' section could be reduced to just the code comparison example without the explanatory paragraphs.
Add an explicit numbered workflow: 1) Verify coverage via curl, 2) If supported → use unified API, 3) If UnsupportedOperationError → use Proxy API, with a validation checkpoint after each step.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes 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 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 concrete curl command for the Proxy API escape hatch. The serviceId, auth setup, and SDK imports are all copy-paste ready. | 3 / 3 |
Workflow Clarity | There's an implicit workflow (check coverage → use unified API → fall back to proxy if unsupported), but it's not presented as a clear sequential process with explicit validation checkpoints. The beta status warning mentions verifying coverage but doesn't integrate it into a step-by-step workflow with error handling feedback loops. | 2 / 3 |
Progressive Disclosure | Excellent use of one-level-deep references to sibling skills (apideck-best-practices, apideck-connector-coverage, SDK skills) with clear signaling of what each contains. The SKILL.md stays as an overview and delegates detailed content appropriately. Navigation links are well-organized in 'See also' and inline. | 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.