Guide · Agent skill
How to use the Organize Google Drive Folders agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The Organize Google Drive Folders skill (recipe-organize-drive-folder) gives an AI agent a step-by-step recipe for tidying Google Drive: create a project folder, add sub-folders, move existing files into the right place and list the result to check it. This guide explains what an agent skill is, how to install this one, how to ask for it in plain language, and what to watch for before letting it touch your files. It is written for readers who have not used agent skills before, but the skill assumes you already have the gws command-line tool and Google authentication working.
Organize Google Drive Foldersgoogleworkspace/cli · Apache-2.0 Download the skill Quick start
- 1Set up gws and authentication. Install the gws command-line tool and authorise a Google account with access to Google Drive.
- 2Download the skill ZIP. Get the recipe-organize-drive-folder ZIP from this page.
- 3Install the skill. Unzip into ~/.claude/skills/ or a project's .claude/skills/ folder, or upload the ZIP under Settings → Capabilities → Skills in the Claude apps.
- 4Install the gws-drive skill. The recipe requires gws-drive to be loaded before it runs.
- 5Ask for the outcome in plain language. Describe the project folder, the sub-folders and the files to move, naming them explicitly.
- 6Review the proposed commands. Check the gws commands and file IDs the agent plans to run before approving them.
- 7Verify the result. Ask the agent to list the folder contents and confirm the files are where you expected.
What is an agent skill and what does this one do?
An agent skill is a folder containing a SKILL.md file that gives an AI agent instructions for a specific task. When the task comes up, the agent reads those instructions and follows them. This skill is a recipe: it tells the agent how to organise Google Drive using commands from the gws command-line tool.
The recipe has four steps. The agent creates a top-level project folder, creates sub-folders inside it, moves existing files into the correct folder by updating their parent folder, and then lists the folder contents so you can check the result.
Install the Organize Google Drive Folders skill
Download the ZIP file for the skill from this page. You can install it in one of three ways.
For Claude Code, unzip it into your personal skills folder at ~/.claude/skills/ for use across all projects, or into a project's .claude/skills/ folder to limit it to that project.
In the Claude apps, upload the ZIP under Settings → Capabilities → Skills.
- Personal use: unzip into ~/.claude/skills/
- Single project: unzip into the project's .claude/skills/ folder
- Claude apps: Settings → Capabilities → Skills, then upload the ZIP
Install the required dependencies
The recipe cannot run on its own. It needs the gws command-line tool (Google Workspace CLI), the gws-drive skill, and a Google account authorised for Google Drive access through gws. The skill's instructions say to load gws-drive before running the recipe.
Set up gws and Google authentication first. If you skip this, the recipe will fail at its first Drive command.
- gws command-line tool (Google Workspace CLI)
- gws-drive skill, loaded before this recipe
- A Google account authorised for Google Drive through gws
How to trigger the skill with natural requests
You do not need to type a command to use the skill. Describe the outcome in plain language and mention Google Drive, and the agent should pick up the recipe when it matches. Be specific about the folder names and the files involved, since the agent builds its commands from what you tell it.
Good requests name the project, the sub-folders you want and the files to move. Vague requests such as 'clean up my Drive' are risky because the agent has to guess what goes where.
- "Create a Q2 Project folder in Google Drive with Documents and Reports sub-folders."
- "Move the file with ID 1abc... into the Documents folder of the Q2 Project and remove it from its old folder."
- "Set up a folder structure for the new client onboarding project and check that it looks right."
What the commands look like
The skill uses gws drive files create to make folders, gws drive files update with addParents and removeParents to move files, and gws drive files list to check the result. Knowing these commands helps you review what the agent is about to run.
The skill's steps use placeholders such as PARENT_FOLDER_ID, FILE_ID, FOLDER_ID and OLD_PARENT_ID. The agent needs real IDs for these, so it will need to find them through Drive first or be given them by you.
gws drive files create --json '{"name": "Q2 Project", "mimeType": "application/vnd.google-apps.folder"}'Safety notes before you run it
This skill runs scripts and uses the network, because it sends commands to Google Drive through gws. Moving files changes where they live in your Drive, and the skill has no undo or dry-run step. A file moved with the wrong ID can end up in an unexpected folder.
Review the commands the agent proposes before approving them, and avoid pointing the skill at large parts of your Drive without checking first. Test on a small folder you do not mind changing.
- The skill runs scripts and uses the network
- There is no built-in undo or dry-run
- Check file IDs and folder IDs before approving a move
- Start with a small test folder
Tips for better results
Give the agent exact folder and file names, and the IDs if you have them. Ask it to list the folder at the end so you can confirm the layout. For a recurring structure, such as a folder layout for each quarter, describe the layout once and reuse the same request each time.
If the agent's first command fails, check that gws is installed and authorised for your account before changing the request.
- Name folders and sub-folders explicitly
- Supply file IDs when you can
- Ask for a list at the end to verify
- Confirm gws authentication if commands fail
What people use it for
- Creating a Q2 project folder with Documents and Reports sub-folders at the start of a quarter.
- Setting up a consistent folder layout for a new client or project.
- Moving a set of existing files into the correct shared Drive folder.
- Listing a folder's contents after a move to confirm the structure.
Frequently asked questions
How do I install the recipe-organize-drive-folder skill?
Download the ZIP from this page and unzip it into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder. In the Claude apps, upload the ZIP under Settings → Capabilities → Skills.
What do I need before this skill will work?
You need the gws command-line tool (Google Workspace CLI), the gws-drive skill loaded, and a Google account authorised for Google Drive access through gws. The recipe cannot run without these.
Is the Organize Google Drive Folders skill free?
The source is licensed under Apache-2.0. Check the licence in the repository for the terms that apply to your use.
Does the skill run scripts or use the network?
Yes on both counts. The skill runs scripts and uses the network because it sends commands to Google Drive through the gws tool.
Can I undo a move if the agent puts a file in the wrong place?
The skill has no undo or dry-run step. You would need to move the file back manually in Drive, so review file and folder IDs before approving any move.
Should I use this skill to reorganise a large Drive library?
Not without review. The skill is best for setting up a project layout or filing a limited set of documents, and bulk reorganisation without checking can put files in unexpected places.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
This skill suits people who already run the gws command-line tool and want an agent to create consistent project folder layouts and file documents into shared Drive folders. It is a poor fit for anyone without gws and Google authentication set up, or for bulk reorganisation of a large Drive library without a review step. Pick it for small, reviewed changes; use the Drive interface directly if you want a visual, undoable workflow.
Download the skill