connector-googledrive
Build Google Drive Integrations in Motoko
Google Drive integrations require careful OAuth, permissions, and Internet Computer outcall configuration. This skill provides a focused Motoko recipe for metadata, organization, sharing, and synchronization.
安裝前請停止並請求確認。
請審查安裝計畫，並在變更檔案前取得使用者明確同意。
使用我的智慧代理安裝
將此請求複製給你的智慧代理，其中包含權威 Skill 頁面和清單。
Review the Skillstore skill "connector-googledrive" from https://skillstore.io/skills/caffeinelabs-connector-googledrive.md and its manifest at https://skillstore.io/api/skills/caffeinelabs-connector-googledrive/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.你的智慧代理仍應顯示其計畫，並依安全政策請求必要確認。
Agent 可讀資源
當 AI Agent、爬蟲或腳本需要乾淨脈絡、而不是讀取完整頁面時，請使用這些連結。
測試它
正在使用「connector-googledrive」。 List my Google Drive files with read-only access.
預期結果:
A Motoko implementation plan covering OAuth consent, token exchange, client configuration, file listing, pagination, and token refresh.
正在使用「connector-googledrive」。 Create a project folder and share it with an editor.
預期結果:
A workflow that creates folder metadata, applies an editor permission, checks each result, and avoids duplicate writes.
正在使用「connector-googledrive」。 Synchronize metadata from a shared drive.
預期結果:
A synchronization design using shared-drive parameters, start page tokens, change pagination, retry handling, and durable checkpoints.
安全審計
高風險All 60 static findings are false positives caused by Markdown backticks, OAuth scope notation, and ellipsis shorthand; SKILL.md contains no executable implementation. Semantic review found dependency-installation exposure and incomplete guidance for OAuth callback binding and long-lived refresh-token protection.
已確認的安全問題 (3)
風險因素
⚙️ 外部命令 (50)
🌐 網路存取 (1)
📁 檔案系統存取 (4)
分享與引用此報告
分享版本化評估報告、中性徽章、嵌入卡片與引用。Skillstore 只報告證據，不判斷該 Skill 是否安全。
複製報告連結
https://skillstore.io/skills/caffeinelabs-connector-googledrive/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown 徽章
[](https://skillstore.io/skills/caffeinelabs-connector-googledrive?utm_source=security_passport_badge)HTML 徽章
<a href="https://skillstore.io/skills/caffeinelabs-connector-googledrive?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/caffeinelabs-connector-googledrive/security.svg" alt="Skillstore security assessment" loading="lazy"></a>嵌入卡片
<iframe src="https://skillstore.io/embed/skills/caffeinelabs-connector-googledrive.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>學術引用 (APA · BibTeX · CFF)
APA 引用
caffeinelabs. (2026). connector-googledrive security audit report (audit version 1) [Author version 0.1.0]. Skillstore. https://skillstore.io/skills/caffeinelabs-connector-googledrive/audits/1BibTeX 引用
@techreport{caffeinelabs-caffeinelabs-connector-googledrive-2026,
author = {caffeinelabs},
title = {connector-googledrive security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/caffeinelabs-connector-googledrive/audits/1},
note = {Author version 0.1.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "connector-googledrive security audit report (audit version 1)"
version: "0.1.0"
type: report
authors:
- name: "caffeinelabs"
date-released: "2026-09-11"
url: "https://skillstore.io/skills/caffeinelabs-connector-googledrive/audits/1"
identifiers:
- type: other
value: "skillstore:caffeinelabs-connector-googledrive:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore 評分
評分依據 證據置信度: 中你可以打造什麼
Create a Drive Organizer
Build a Motoko service that lists, creates, renames, moves, and trashes Google Drive metadata.
Add Controlled File Sharing
Implement permission management with narrow OAuth scopes and explicit user authorization.
Track Shared Drive Changes
Design metadata synchronization using shared drives, change tokens, and non-replicated outcalls.
試試這些提示
Add the required Google Drive and OAuth dependencies to my Motoko project, then explain each configuration step.
Plan a read-only Motoko flow that authenticates a user and lists their Google Drive file metadata.
Design a Motoko workflow that creates a Drive folder and grants one specified user access with the narrowest suitable scope.
Architect multi-user Drive change synchronization with PKCE binding, protected refresh tokens, retries, least privilege, and non-replicated outcalls.
最佳實務
- Request the narrowest Google Drive scope that satisfies the user task.
- Keep every Drive read and write non-replicated to prevent duplicate requests.
- Protect refresh tokens and bind OAuth callbacks to the initiating user session.
避免
- Do not call Google endpoints directly when the supported client covers the operation.
- Do not request full Drive access for metadata-only or per-file workflows.
- Do not use metadata methods for binary uploads or downloads.
常見問題
Can this connector upload file contents?
Which OAuth scope should I request?
Why must outcalls be non-replicated?
Does googledrive-client manage OAuth?
Can I use the flat API modules?
Does this skill execute Google Drive operations?
開發者詳細資訊
作者
caffeinelabs授權
MIT
作者版本
v0.1.0
Skillstore 修訂
r1
引用
25385eb0325d3e0ae62e9720ba8894c2ddb3d998
維護新鮮度
2026/9/11
使用量
0 次下載 · 0 次瀏覽
檔案結構
📄 SKILL.md