Recipe Watch Drive Changes
CheckedThis skill monitors Google Drive for recipe files and notifies you of any updates or changes to your recipes, streamlining your cooking workflow.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add googleworkspace/cli --skill recipe-watch-drive-changes -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
googleworkspace
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned googleworkspace/cli at a3768d0e82.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- a3768d0e82
- Scanned
- 1 file, 28 lines
About this skill
What it does
This skill enables AI agents to monitor Google Drive for specific file changes, allowing automated workflows to trigger based on document updates. It provides a reactive mechanism to detect when files are created, modified, or deleted within designated folders.
When to use it
- Automatically notify team members whenever a critical project document is updated in a shared folder.
- Trigger backup processes immediately after a specific file is modified to ensure data safety.
- Start an analysis workflow only when a new report file appears in the "Inbox" directory.
- Halt a deployment pipeline if a configuration file in Drive has been unexpectedly altered.
Key capabilities
- Monitors Google Drive for real-time or scheduled change events.
- Detects specific actions such as file creation, modification, and deletion.
- Filters monitoring scope to specific folders or entire drives.
- Integrates directly with the Google Workspace CLI environment.
Example prompts
- "Set up a watcher on my 'Q4 Reports' folder to alert me whenever a new spreadsheet is added."
- "Configure an agent to scan Drive for any changes to files named 'config.json' and log the event."
- "Create a workflow that automatically archives documents in the 'Archives' folder if they are modified after today."
Tips & gotchas
Ensure your AI agent has the necessary OAuth scopes granted to access Google Drive on your behalf. This skill relies on the underlying Google Workspace CLI, so verify your local environment is properly configured before attempting remote monitoring tasks.