google-docs-create-documentAtomic node skill to create a Google Doc using the gog CLI.
Install via ClawdBot CLI:
clawdbot install zvirb/google-docs-create-documentGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated Oct 5, 2026
An agency uses an AI agent to instantly spin up a branded Google Doc for every new client, pre-filled with kickoff checklist headers and project scope placeholders. The doc ID returned by the CLI is saved to the CRM, so the account manager can share it within minutes of the deal closing.
A product team's AI assistant creates a fresh Google Doc at the start of each recurring meeting, titled with the date and agenda topic. The shared link is posted into Slack so remote participants can collaboratively capture decisions in real time.
A sales operations agent creates a new Google Doc for each qualified opportunity, using the account name as the title before piping in pricing and scope content from a template library. Reps then review and customize instead of starting from a blank page.
An edtech platform auto-creates a Google Doc for every assignment submitted through its portal, naming it after the student and task ID. Teaching assistants receive the document IDs programmatically and grade directly inside the shared file.
A fintech back-office agent generates a dated Google Doc shell for each monthly regulatory report, establishing an audit-ready naming convention. Subsequent automated steps populate the sections, while the original creation timestamp is logged for traceability.
A document automation platform sells a Google Workspace integration that programmatically creates docs for end customers via the gog CLI. The skill acts as the atomic creation primitive inside a larger workflow builder, and customers pay per connected seat.
An automation consultancy builds custom agent pipelines for clients that need docs created on demand, such as onboarding packets or meeting notes. The atomic create-document skill is a reusable building block sold as part of a managed automation retainer.
A niche product for a specific vertical, like real estate or legal, where each transaction automatically triggers creation of a properly titled Google Doc. The app monetizes through transaction-based pricing as documents are spun up.
💬 Integration Tip
Because this is an atomic node, chain it directly with CLI commands that write content into the returned doc ID rather than adding extra abstraction layers. Always parse the --json output to capture the document ID, and handle non-zero exit codes so upstream agents can retry or alert on creation failures.
Scored Oct 5, 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).