google-drive

Coordinate Google Drive file discovery, sharing, and lifecycle tasks.

Updated Dec 17, 2024
One-click install
npx skills add https://github.com/LAF-US/IDAHO-VAULT --skill google-drive-laf-us
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: google-drive
Source: https://github.com/LAF-US/IDAHO-VAULT/tree/main/.codex/plugins/cache/openai-curated/google-drive/314574a046f21938025ae443f9c6dbbd0c2c9b7a/skills/google-drive
Command: npx skills add https://github.com/LAF-US/IDAHO-VAULT --skill google-drive-laf-us

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

Centralizes Google Drive actions by providing a single entrypoint to discover, organize, share, export, copy, or delete Drive files while enabling unified editing and summarization of Docs, Sheets, and Slides through one integrated workflow.

Core Features & Use Cases

  • Ground target file first (URL, ID, or recent activity) to anchor the task, then route to the most specific sibling skill for Docs, Sheets, or Slides content manipulation.
  • Use the base Drive workflow for file lifecycle tasks (search, fetch, recent files, sharing, copying, deleting, exporting, and revision history) while preserving permissions and structure.
  • Route to narrow skills: google-drive-comments for comments, google-docs for Docs content, google-sheets for Sheets data, google-slides for Slides decks.
  • Maintain permissions and file organization; avoid unnecessary moves and respect existing ownership when handing off to narrower skills.

Quick Start

Ground the target Drive file (via URL, ID, or recent activity) and route the task to the most specific sibling skill (Docs, Sheets, or Slides) for editing, summarization, or lifecycle actions.

Frequently Asked Questions about google-drive

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage Google Drive file lifecycle tasks like searching and exporting?

Google Drive file lifecycle tasks like searching, fetching, copying, and exporting are managed through a unified workflow that preserves permissions and structure. It grounds target files via URL, ID, or recent activity to anchor the task.

What's the best way to edit Google Docs, Sheets, and Slides content from one place?

Editing Google Docs, Sheets, and Slides from one place is achieved by grounding the target Drive file first, then routing the task to the most specific sibling skill for content-specific editing and summarization.

Can I change Google Drive sharing permissions without breaking existing ownership?

Google Drive sharing permissions and existing ownership are preserved during collaboration workflows. The base Drive workflow handles permission changes while respecting file organization and avoiding unnecessary moves.

Does Google Drive workflow routing handle comments differently than document content?

Google Drive workflow routing handles comments by directing them to a dedicated sibling skill for comments, while document content routing goes to separate skills for Docs, Sheets, or Slides manipulation.

How do I export or summarize Google Drive files across different formats?

Exporting and summarizing Google Drive files across formats is handled by routing grounded files to content-specific contexts. This workflow coordinates export, copy, and revision history actions while enforcing a minimal governance stack.

When should I use the base Google Drive workflow instead of content-specific routing?

The base Google Drive workflow is used for general file operations like search, fetch, sharing, and deletion. Content-specific routing to Docs, Sheets, or Slides skills is reserved for editing, summarization, and content manipulation.