google-drive
Use connected Google Drive as the single entrypoint for Drive, Docs, Sheets, Slides, and Forms work. Use when the user wants to find, fetch, organize, share, export, copy, or delete Drive files, or summarize and edit Google Docs, Google Sheets, Google Slides, and Google Forms through one unified Google Drive plugin.
- License 许可
- Apache-2.0
- 所属仓库
- Aeven-AI/Aeven
- 最近更新
- 2026-11-15
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- google-drive
- description
- Use connected Google Drive as the single entrypoint for Drive, Docs, Sheets, Slides, and Forms work. Use when the user wants to find, fetch, organize, share, export, copy, or delete Drive files, or summarize and edit Google Docs, Google Sheets, Google Slides, and Google Forms through one unified Google Drive plugin.
02 资源文件 9
- 参考文档agents/openai.yaml528 B
- 资产文件assets/app-icon.png56.8 KB
- 资产文件assets/google-drive-small.svg1.4 KB
- 资产文件assets/google-drive.png56.8 KB
- 资产文件assets/google-drive.svg1.4 KB
- 参考文档references/slides/chart-refresh-workflows.md5.2 KB
- 参考文档references/slides/deck-scope-verification.md1.7 KB
- 参考文档references/slides/sheets-chart-replacement.md3.5 KB
- 参考文档references/slides/visual-change-loop.md6.0 KB
03 SKILL.md 正文
Google Drive
Aeven connector tools
The connected Drive account exposes Drive, Docs, Sheets, Slides and Forms operations together. Discover its exact mcp__google-drive_<id>__ namespace in the tool catalog. Use the named tools for common operations and workspace_schema followed by workspace_raw for native Google API operations referenced below. Upstream mcp__codex_apps__google_drive names identify the equivalent operation, not an Aeven tool name. Do not call unavailable OpenAI runtime helpers; perform their read, mutation and verification steps through these tools.
Use the named tools exactly as discovered: drive_search accepts {q, max, orderBy} (for the latest file: {q: "trashed = false", max: 1, orderBy: "modifiedTime desc"}); drive_get_file accepts {fileId}. Their arguments are at the top level. Native fields and pageSize belong to workspace_raw API params, not to drive_search. Never copy upstream tool names or snake_case argument names into these calls.
Use the named tools exactly as discovered: drive_search accepts {q, max, orderBy} (for the latest file: {q: "trashed = false", max: 1, orderBy: "modifiedTime desc"}); drive_get_file accepts {fileId}. Their arguments are at the top level. Native fields and pageSize belong to workspace_raw API params, not to drive_search. Never copy upstream tool names or snake_case argument names into these calls.
For comments and replies, use Drive comments and replies methods. For sharing and file moves, use Drive permissions and files.update. For structured Docs edits, Sheets formatting/formulas/charts and Slides layout/images, use the corresponding service’s batchUpdate method. Obtain parameter and request-body definitions with workspace_schema; pass the documented camelCase fields to workspace_raw as params and body. Example: service: "docs", path: ["documents", "batchUpdate"], params: {documentId}, body: {requests, writeControl}. Keep revisions, targeted edits and readback requirements from the upstream instructions below.
Use this as the top-level router for Google file work inside the unified Google Drive plugin. Do not route the user toward separate Google Docs, Google Sheets, or Google Slides plugins.
Start with Google Drive for file discovery and file lifecycle tasks, then route to narrower sibling skills only when the task becomes specific to Docs, Sheets, or Slides.
Workflow
- Ground the target file first.
- If the user did not provide an exact file URL or ID, use Google Drive search, recent files, folder listing, or metadata reads to identify the right file.
- If the request starts as "find X and then update it," do the Drive discovery step first instead of guessing the target.
- Stay in the base Google Drive workflow for Drive-native tasks.
- Use the base workflow for search, fetch, recent files, folders, sharing, copying, deleting, exporting, revision history, file moves, and other file-lifecycle work that is not primarily about editing Docs, Sheets, or Slides content.
- For version-history requests, including "previous version," "revision history," "what changed since the last version," or "compare to the prior revision," ground the file, fetch the current content, use
list_file_revisions, fetch the immediately previous revision or the user-named revision withfetch_file_revision, then compare the fetched revision against the current content. Do not say previous versions are unsupported until you have checked whether revision tools are available for the target file. - For file move requests, ground the source file and target folder, read the file metadata including its current parents, then use
update_filewithaddParentsfor the target folder andremoveParentsfor only the verified source parent or parents that should no longer contain it. Preserve unrelated parents, and verify the move by reading metadata or listing the target folder before the final response. - Before any export or raw-file fetch, read or reuse Drive metadata so the MIME type and Google Drive URL are known. Use
export_fileonly to convert a native Google Doc, Sheet, or Slide into an explicitly requested format; it returns an authenticated file reference, not inline bytes or base64. Google limitsfiles.exportresponses to 10 MB; oversized exports fail rather than returning truncated content. For a larger native PDF, usedownload_file(id=file_id, mime_type="application/pdf")when the streaming action is available. It calls Google'sfiles.downloadAPI and returns a top-level materializablefile_uri. Oncedownload_fileis unavailable and canonicalfetchuses that streamed download path, usefetch(url=google_drive_url, download_raw_file=True, raw_export_mime_type="application/pdf")instead. A native-filefetchthat still usesfiles.exportcannot bypass the 10 MB limit. For PDFs, images, ZIPs, Office files, recordings, and other stored, non-native files, usefetch(url=google_drive_url, download_raw_file=True). Use only the authenticated top-levelfile_urior materializedworkspace_path; never request inline base64 unless an existing caller explicitly opts into bounded legacy compatibility. Usefetchwithoutdownload_raw_filefor bounded, best-effort readable text. Do not retryexport_fileafter metadata shows a non-native MIME type.
- Route to the narrowest sibling skill that matches the file type and job.
- Drive, Docs, Sheets, or Slides comment creation, comment replies, comment resolution, or review-by-comments: use google-drive-comments.
- Google Docs net-new creation, content summary, revision planning, prose rewriting, or section edits: use google-docs.
- Google Sheets creation, local spreadsheet import, range inspection, table cleanup, data restructuring, formula design or repair, chart creation or repair, or batch updates: use google-sheets.
- Google Slides deck summary, content edits, new deck creation, local presentation import, visual cleanup, structural repair, or template migration: use google-slides.
Routing Rules
- If the request is ambiguous between Drive and a file-type surface, use the artifact itself as the tie-breaker:
- Doc -> Docs skill
- Sheet -> Sheets skill
- Deck -> Slides skill
- If the user wants to find a file and then edit it, do both in one flow: Drive for discovery, then the file-type skill for the edit.
- If the user wants a Google Workspace outcome but has not named a file type yet, start with Drive discovery instead of asking them to choose among separate Google plugins.
- If the user asks to create a new Google Doc, route to the Docs skill; it owns the mandatory local
.docx-> native Google Docs import workflow and the explicit-user-override boundary. Do not create a blank Google Doc directly from this router. - If the user asks to import a local
.docxinto Google Docs, route to the Docs skill and use its native conversion workflow. Preserve the source file type only when the user explicitly asks for that. - If the user asks to create a new Google Sheet, route to the Sheets skill. The Sheets skill should prefer the
[@spreadsheets](plugin://spreadsheets@openai-primary-runtime)plugin or$Excelskill to create a local.xlsx, then import it as native Google Sheets. - If the user asks to import a local
.xlsx,.xls,.ods,.csv, or.tsvinto Google Sheets, route to the Sheets skill and use native Google Sheets conversion by default. Preserve the source file type only when the user explicitly asks for that. - If the user asks to create a new Google Slides deck, route to the Slides skill; it owns the mandatory local
.pptx-> native Google Slides import workflow and the explicit-user-override boundary. Do not create a blank Google Slides deck directly from this router. - If the user asks to import a local
.ppt,.pptx, or.odpinto Google Slides, route to the Slides skill and use its native conversion workflow. Preserve the source file type only when the user explicitly asks for that. - If the user asks to export or download an existing Drive file, choose the action from metadata: native Google Docs, Sheets, and Slides files use
export_filefor explicit conversions within Google's 10 MB limit. For a larger native PDF, prefer the currently available streamingdownload_file(id=file_id, mime_type="application/pdf"); after canonicalfetchadopts the same streamed download path anddownload_fileis removed, usefetch(url=google_drive_url, download_raw_file=True, raw_export_mime_type="application/pdf"). Stored, non-native PDFs, images, ZIPs, CSVs, Office files, audio, and video usefetch(url=google_drive_url, download_raw_file=True). Use the returned top-levelfile_urior its authenticated, materializedworkspace_path; do not expose inline binary, base64, or a bearer URL. Base64 is available only when an existing compatibility caller explicitly requests the bounded legacy behavior.
Write Safety
-
Preserve the user's existing file organization, sharing state, and target artifact unless the request clearly asks to change them.
-
When a task can be satisfied by a file-level Drive operation alone, do not load heavier Docs, Sheets, or Slides skills.
-
For write-heavy Sheets or Slides work, read the specialized skill before the first large update so request shapes stay grounded.
-
For any file import or explicit direct create that returns a user-facing Google Workspace link, wait for the write action to complete and verify the created file with connector readback or Drive metadata readback before returning the URL. Use only a URL or id observed from the completed connector result or readback; never synthesize or predict the URL.
-
For creating or editing surveys, quizzes, registration forms, or reviewing form responses, load the Google Forms skill. Create Forms through the Forms API, then use Drive for file organization and sharing.
-
For creating or editing surveys, quizzes, registration forms, or reviewing form responses, load the Google Forms skill. Create Forms through the Forms API, then use Drive for file organization and sharing.
Related Skills
- Comments: google-drive-comments
- Docs: google-docs
- Sheets: google-sheets
- Slides: google-slides
- Forms: google-forms
- Forms: google-forms
04 同仓库更多 Skills
cv
Make a CV or résumé with the user in one of Aeven's forty templates, from bold portrait-cover designs (Black, Slate, Fresh) to classic one-page resumes (Harvard, Tang, Minimal Rule), and deliver it as PDF, Word (DOCX) and Pages. Use for any CV, résumé or curriculum vitae request, when the user picked a template on the Resumes page ("…with the Black resume template"), or when they want an existing CV rebuilt in a new design.
cv
暂无简介
user-only-skill
Prove model-disabled skills stay outside the model catalog.
snapshot-skill
Exercise project skill discovery and loading in snapshot tests.
model-only-skill
Prove user-disabled skills remain available to the model.
editing-cordis-compositions
Use when creating, changing, or validating a Cordis composition for this harness — writing or editing an agent preset, adding or removing a plugin row, deciding whether something belongs to the host composition or to one session, checking whether a preset you authored actually mounts, or diagnosing a row that mounted but contributed nothing.