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.mdSecurity
1 medium severity finding. This skill can be installed but you should review these findings before use.
W011: Third-party content exposure detected (indirect prompt injection risk)
What this means
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Why it was flagged
Third-party content exposure detected (high risk: 0.80). The skill's SKILL.md explicitly instructs the agent to list, export, download, and proxy-call Google Drive files via Apideck (e.g., apideck.fileStorage.files.list, /file-storage/files/{id}/export, and the Proxy with x-apideck-downstream-url), which means the agent will fetch and read user-generated/untrusted Drive content that could contain instructions influencing its actions.
- Repository
- apideck-libraries/api-skills
- Commit
9e04d86
- Audited
- Security analysis
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.