onelogin
OneLogin 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 OneLogin. Routes through Apideck with serviceId "onelogin".
84
82%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
92%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 well-crafted description that clearly states what the skill does and when to use it, with good trigger terms specific to the OneLogin/Apideck HRIS domain. The main weakness is potential conflict with other Apideck HRIS connector skills that share the same entity types and methods, differentiated only by serviceId. The description mitigates this somewhat by explicitly naming 'OneLogin' and the specific serviceId.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: read or 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' (OneLogin 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 OneLogin'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'OneLogin', 'employees', 'departments', 'payrolls', 'time-off records', 'HRIS', 'Apideck', 'sync', and 'serviceId onelogin'. Good coverage of domain-specific terms. | 3 / 3 |
Distinctiveness Conflict Risk | While 'OneLogin' and 'serviceId onelogin' are distinctive, the description notes 'same methods work across every connector in HRIS', which means there are likely many similar Apideck HRIS skills differing only by serviceId. This creates overlap risk with other Apideck HRIS connector skills for the same entity types (employees, departments, etc.). | 2 / 3 |
Total | 11 / 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 progressive disclosure and actionable code examples. Its main weaknesses are moderate verbosity (marketing language, OAuth explanations Claude doesn't need) and a lack of explicit workflow sequencing that would help Claude guide users through the setup-verify-use pipeline. The escape hatch and coverage verification sections are valuable additions.
Suggestions
Remove promotional language ('compounding advantage', 'no rewrite, no new SDK') and OAuth concept explanations — Claude knows these. The 'Portable across 58 HRIS connectors' section could be reduced to just the code example.
Add an explicit numbered workflow: 1. Verify connection state → 2. Check coverage → 3. Call unified API → 4. If UnsupportedOperationError, use Proxy API — with validation at each step.
| 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 authentication section explains OAuth concepts Claude already knows, and phrases like 'This is the compounding advantage of using Apideck over integrating OneLogin directly' are promotional rather than instructional. However, the core content is reasonably focused. | 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. The serviceId, auth type, and setup links are all specific and copy-paste ready. | 3 / 3 |
Workflow Clarity | There's an implicit workflow (set up auth → verify coverage → call API → fall back to proxy if needed), but it's not explicitly sequenced with numbered steps or validation checkpoints. The coverage verification step is mentioned but not integrated into a clear workflow with error handling 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, OpenAPI specs, and the connection guide. Content is appropriately split between this skill 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.