okta
Okta 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 Okta. Routes through Apideck with serviceId "okta".
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 platform (Okta), the integration mechanism (Apideck HRIS unified API), concrete data entities (employees, departments, payrolls, time-off records), and explicit trigger guidance. It uses proper third-person voice and is concise without being vague. The only minor note is that it could mention additional trigger terms like 'HR' or 'human resources' for broader coverage, but overall it's well-crafted.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: read/sync employees, departments, payrolls, and time-off records. Also specifies the integration mechanism (Apideck's HRIS unified API) and the serviceId parameter. | 3 / 3 |
Completeness | Clearly answers both 'what' (Okta integration via Apideck 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 Okta'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Okta', 'employees', 'departments', 'payrolls', 'time-off records', 'HRIS', 'Apideck', 'serviceId'. Covers both the platform name and the data entities a user would reference. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — specifically targets Okta via Apideck with serviceId 'okta'. The combination of the specific platform (Okta), the API layer (Apideck), and the domain (HRIS) makes it very 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 strong actionability and excellent progressive disclosure to related skills and references. Its main weaknesses are moderate verbosity (marketing-style repetition about portability and the unified API advantage) and a workflow that could be more explicitly sequenced, especially given the beta status and the need to verify coverage before making calls.
Suggestions
Remove or condense the 'Portable across 58 HRIS connectors' section — the portability point is already made in the intro and the code example speaks for itself.
Add an explicit numbered workflow: 1) Verify coverage → 2) Call unified API → 3) Handle UnsupportedOperationError → 4) Fall back to Proxy API, with validation at each step.
Trim the 'When to use this skill' section to just the activation triggers — Claude doesn't need to be told what the skill teaches it.
| 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 'compounding advantage' paragraph is filler Claude doesn't need, and the 'When to use this skill' section over-explains activation triggers. However, the code examples and factual sections are reasonably tight. | 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 placeholders. | 3 / 3 |
Workflow Clarity | There's an implicit workflow (check coverage → use unified API → fall back to proxy if unsupported), but it's never presented as a clear numbered sequence with validation checkpoints. The beta status warning mentions verifying coverage but doesn't integrate it into a step-by-step decision flow with explicit error handling. | 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, OpenAPI specs, and sibling connectors. Content is appropriately split between this overview and referenced materials. | 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.