google-drive-share-fileAtomic node skill to share a file in Google Drive using the gog CLI.
Install via ClawdBot CLI:
clawdbot install zvirb/google-drive-share-fileGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated Sep 29, 2026
An agency shares final deliverables such as design files or reports directly from Google Drive with clients, granting appropriate permissions via the gog CLI. This ensures clients get immediate access without manual link sharing. The agent can automate per-client email and role assignment.
HR or IT teams use the skill to automatically share onboarding documents, policy files, and training materials with new hires. Permissions are set to reader or writer based on the document type. This reduces manual steps and ensures consistent access.
Law firms share case-related documents with external counsel or clients while maintaining strict access controls. The skill allows precise role assignment (reader/writer) and user-specific sharing. It helps meet compliance and confidentiality requirements.
Teachers or administrators share lecture notes, assignments, and reading materials with students via Google Drive. The agent can batch-share files with individual students or entire groups using email addresses. This streamlines course preparation and updates.
Development teams share build artifacts, documentation, or configuration files with testers and stakeholders. The skill triggers sharing upon release creation, ensuring timely access. Permissions can be set to reader for external testers or writer for internal collaborators.
A cloud-based platform that integrates Google Drive sharing into its workflow automation for teams. It allows users to define sharing rules and triggers, reducing manual effort. The gog CLI skill powers the underlying sharing mechanism.
An IT service provider manages Google Drive permissions and file sharing for small businesses. They use the skill to automate routine sharing tasks and ensure security policies are followed. This is offered as part of a broader managed services contract.
A specialized tool for legal, healthcare, or finance firms that automates document sharing while logging access and enforcing compliance. The skill enables precise permission grants with audit trails. It helps organizations meet HIPAA, GDPR, or other regulations.
💬 Integration Tip
Ensure the gog CLI is installed and authenticated with appropriate Google Drive scopes. Use the --json flag for machine-readable output and handle errors gracefully.
Scored Sep 29, 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).