google-drive-delete-fileAtomic node skill to delete a file in Google Drive using the gog CLI.
Install via ClawdBot CLI:
clawdbot install zvirb/google-drive-delete-fileGrade Limited — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated Oct 5, 2026
A marketing agency manages shared Google Drive folders for multiple clients and needs to regularly remove outdated logos, campaign creatives, and old briefs to keep client folders tidy. An agent using this skill can automatically trash files flagged by a content audit, reducing manual cleanup hours.
A law firm must comply with retention schedules that require deleting client case files after a specified period. This skill lets an agent move expired documents to trash in Google Drive as part of a standardized, auditable workflow.
A SaaS platform stores user-generated files in Google Drive and needs to delete files when a user account is closed or a subscription is canceled. The agent can invoke this skill to trash files programmatically, ensuring data hygiene and compliance.
A university department collects student assignments in Google Drive and must remove them after grades are finalized and the appeal period ends. This skill enables an automated process to trash old submissions, freeing storage and protecting student privacy.
A healthcare clinic uses Google Drive for temporary storage of scanned intake forms before transferring them to an EHR system. After transfer, an agent can delete the temporary files using this skill, minimizing the risk of unprotected patient data lingering.
An MSP offers ongoing Google Workspace administration, including regular file cleanup and policy enforcement, to small and medium businesses. By automating deletion tasks with this skill, the MSP reduces labor costs and offers a scalable, subscription-based service.
A platform provides automated data lifecycle management for Google Drive, helping enterprises classify and delete files according to retention policies. Integrating this skill enables the platform to execute deletion actions directly, enhancing its value proposition.
Independent consultants build custom automation workflows for clients using tools like this skill, streamlining repetitive file management tasks. They charge for implementation and ongoing maintenance of these workflows.
💬 Integration Tip
Ensure the gog CLI is installed and authenticated with appropriate Google Drive scopes; test the skill in a non-production folder to verify the file ID format and error handling.
Scored Apr 27, 2026
Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.
Registra contrato de locação via Google Forms.
Google Sheets integration. Manage analytics data, records, and workflows. Use when the user wants to interact with Google Sheets data.
Google Drive integration. Manage Drives, Users, Permissions. Use when the user wants to interact with Google Drive data.
Query Google Places for text search, place details, resolve, reviews, or scriptable JSON via goplaces.
Google Contacts API integration with managed OAuth. Manage contacts, contact groups, and search your address book. Use this skill when users want to create, read, update, or delete contacts, manage contact groups, or search for people in their Google account. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Google Contacts connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Google Contacts action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Google Contacts examples; they add no Google Contacts capability - Google Contacts is not an event source, a trigger cannot read Google Contacts data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).