google-drive
Google Drive 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 Google Drive. Routes through Apideck with serviceId "google-drive".
81
78%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./connectors/google-drive/SKILL.mdQuality
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 (Google Drive), the integration mechanism (Apideck File Storage unified API), concrete actions (read, write, upload, search), and explicit trigger conditions. The mention of serviceId switching adds useful context for distinguishing this from other Apideck connectors. The description uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'read, write, upload, or search files, folders, and drives.' Also specifies the integration mechanism (Apideck's File Storage unified API) and the serviceId parameter. | 3 / 3 |
Completeness | Clearly answers both 'what' (Google Drive integration via Apideck's File Storage unified API for reading, writing, uploading, searching files/folders/drives) and 'when' (explicit 'Use when the user wants to read, write, upload, or search files, folders, and drives in Google Drive'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Google Drive', 'read', 'write', 'upload', 'search', 'files', 'folders', 'drives'. Also includes technical terms like 'Apideck', 'serviceId', and 'google-drive' that would help distinguish it. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — specifies Google Drive specifically, the Apideck integration layer, the File Storage unified API, and the serviceId 'google-drive'. This clearly differentiates it from other file storage or drive skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
57%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 reference skill with good progressive disclosure and clear navigation to related resources. Its main weaknesses are some marketing-style verbosity (the portability pitch is repeated multiple times) and incomplete actionability — several operations are described conceptually rather than with executable code examples. The skill would benefit from trimming repetitive content and adding concrete code for the export and upload workflows.
Suggestions
Add executable code examples for the export operation (Google Doc → PDF) and file upload instead of just describing them textually.
Remove or consolidate the repeated portability messaging — the intro paragraph and the 'Portable across 5 File Storage connectors' section say the same thing; keep one concise version.
Add a brief workflow with validation for multi-step operations like resumable uploads (start session → upload chunks → verify completion).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary verbosity — the 'Portable across 5 File Storage connectors' section repeats the portability pitch already made in the intro, and the 'compounding advantage' paragraph is marketing copy that doesn't help Claude execute tasks. The entity mapping table and coverage highlights are useful but the surrounding prose could be tighter. | 2 / 3 |
Actionability | The minimal example is executable and copy-paste ready, and the proxy curl example is concrete. However, several operations are described but not shown with executable code — the export example says 'Use /file-storage/files/{id}/export with the target MIME type' without providing actual code, and upload/download operations are only mentioned in the coverage table without examples. | 2 / 3 |
Workflow Clarity | The skill provides a clear 'when to use' decision tree and entity mapping, but lacks explicit multi-step workflows with validation. For operations like uploading files or exporting documents, there are no step-by-step sequences with error handling or verification checkpoints. The proxy escape hatch is mentioned but without a workflow for deciding when to use it vs. the unified API. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure — the skill serves as a clear overview with well-signaled one-level-deep references to SDK skills, OpenAPI specs, best practices, and connector coverage. The 'See also' section and inline links to sibling connectors and language SDK skills are well-organized and easy to navigate. | 3 / 3 |
Total | 9 / 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.