google-docs-read-documentAtomic node skill to read a Google Doc using the gog CLI.
Install via ClawdBot CLI:
clawdbot install zvirb/google-docs-read-documentGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated Jul 17, 2026
A legal firm uses the skill to automatically fetch and review the text of Google Docs contracts. This streamlines the review process by allowing AI agents to analyze clauses without manual downloads.
A marketing agency needs to migrate blog posts from Google Docs to a CMS. The skill extracts plain text from dozens of documents, enabling bulk processing and formatting.
A project management team stores meeting notes in Google Docs. The skill reads these documents to populate a central knowledge base, making action items searchable.
Researchers store interview transcripts in Google Docs. The skill extracts text for natural language processing, such as sentiment analysis or thematic coding.
A regulated company maintains policy documents in Google Docs. The skill reads these documents periodically to check for updates and flag changes to compliance officers.
Offer automated document reading as a subscription for enterprises needing to process large volumes of Google Docs. Revenue is generated through monthly fees based on the number of documents processed.
Build a platform that connects this skill with other tools (e.g., CRM, analytics). Charge per API call or provide tiered pricing for usage levels.
Provide consulting services to optimize clients' document workflows using this skill. Revenue comes from project-based fees and ongoing support contracts.
💬 Integration Tip
Combine with a document parser or NLP tool to automatically classify and extract key information from the read content.
Scored Jul 17, 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).