onedrive
OneDrive integration via Apideck's File Storage unified API — same methods work across every connector in File Storage, switch by changing `serviceId`. Use when the user wants to read, write, upload, or search files, folders, and drives in OneDrive. Routes through Apideck with serviceId "onedrive".
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 strong description that clearly communicates what the skill does and when to use it, with good natural trigger terms. The main weakness is potential overlap with other Apideck File Storage connector skills, since the description itself acknowledges the methods are shared across connectors — differentiation relies primarily on the 'OneDrive' keyword and serviceId.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: read, write, upload, search files, folders, and drives. Also specifies the integration mechanism (Apideck's File Storage unified API) and the serviceId configuration detail. | 3 / 3 |
Completeness | Clearly answers both 'what' (OneDrive integration via Apideck for file storage operations) and 'when' (explicit 'Use when the user wants to read, write, upload, or search files, folders, and drives in OneDrive'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'OneDrive', 'read', 'write', 'upload', 'search', 'files', 'folders', 'drives'. Also includes technical identifiers like 'serviceId', 'onedrive', and 'Apideck' that help with precise matching. | 3 / 3 |
Distinctiveness Conflict Risk | While 'OneDrive' and 'serviceId onedrive' are distinctive, the description mentions generic file operations (read, write, upload, search files/folders) that could overlap with other file storage connectors using the same Apideck unified API. The mention of 'same methods work across every connector' actually highlights potential conflict with sibling skills. | 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 solid connector skill that provides actionable code examples, good entity mapping, and excellent progressive disclosure to related resources. Its main weaknesses are moderate verbosity (marketing-style portability explanations, over-explained activation criteria) and missing workflow detail for multi-step operations like resumable uploads. Trimming the promotional language and adding a concrete upload workflow would significantly improve it.
Suggestions
Remove or significantly condense the 'Portable across 5 File Storage connectors' section — the portability point is already made in the intro and the sibling connectors section.
Add a concrete multi-step example for resumable upload sessions, since this is called out as required for large files but never demonstrated.
Trim the 'When to use this skill' section — Claude doesn't need to be told when to activate a skill in this much detail; a single sentence suffices.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanatory content — e.g., the 'Portable across 5 File Storage connectors' section repeats the portability concept multiple times with marketing-style language ('compounding advantage'), and the 'When to use this skill' section over-explains when Claude should activate it. The entity mapping table and coverage highlights are useful, but the overall document could be tightened by ~30%. | 2 / 3 |
Actionability | Provides fully executable TypeScript code examples for listing files, demonstrates the proxy escape hatch with a complete curl command, and includes concrete serviceId values. The entity mapping table and coverage highlights give Claude specific, actionable knowledge about what's supported and what isn't. | 3 / 3 |
Workflow Clarity | The skill covers individual operations well but doesn't provide a clear multi-step workflow for common tasks like uploading large files via resumable sessions (mentioned but not demonstrated). There are no validation checkpoints or error handling steps shown. For a connector skill this is somewhat acceptable, but the upload session workflow gap is notable. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure — the skill provides a concise overview with clear, well-signaled references to SDK skills, OpenAPI specs, best practices, and sibling connectors. All references are one level deep and clearly labeled. The 'See also' section is well-organized for discovery. | 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.