google-drive

What This Skill Does

The Google Drive skill for OpenClaw provides a robust interface for interacting with the Google Drive API. It enables users to perform comprehensive file operations directly through their AI agent. This includes searching for files, metadata retrieval, downloading documents, creating new folders to organize digital spaces, and managing file permissions for collaborative workflows. By handling authentication via standard bearer tokens, this skill acts as a secure conduit for programmatic file management in cloud environments.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal:

clawhub install openclaw/skills/skills/mrgoodb/google-drive

After installation, ensure that your environment is configured with the required GOOGLE_ACCESS_TOKEN variable to grant the agent authorized access to your Drive instance.

Use Cases

This skill is highly versatile for automation-heavy workflows. Use it to automatically archive email attachments, consolidate report generation, or synchronize local documentation with shared cloud repositories. It is particularly useful for teams that need to programmatically share project assets, organize messy drive structures using automated naming conventions, or perform bulk metadata audits across large file libraries.

Example Prompts

1. "Search my drive for all files containing the word 'Budget' and share the most recent one with [email protected] with reader access."
2. "Download the file with ID 1A2B3C4D5E6F to my local machine and rename it to 'project_archive_final.pdf'."
3. "Create a new folder named 'Q4 Reports' and move all files with 'Q4' in their name into that folder."

Tips & Limitations

To maximize effectiveness, always ensure your OAuth scope is correctly defined within the Google Cloud Console for the project. Note that while this skill excels at file manipulation, it is limited by the standard API rate limits imposed by Google. For high-volume tasks, implement a delay between requests to avoid 429 status codes. Additionally, always verify file IDs before running destructive commands like moving or deleting files, as the AI operates based on the metadata it can see in its current context window.