Automate Google Docs Operations
Lightweight Google Docs CLI automation via standalone OAuth - create, read, and edit docs, no MCP server.
Why it matters
Integrate Google Docs into your local automation scripts for seamless document creation, searching, reading, and editing. This skill enables direct manipulation of Workspace documents without requiring an MCP server.
Outcomes
What it gets done
Create new Google Docs with or without initial content.
Search for documents by title and extract their content.
Append, insert, or replace text within existing Google Docs.
Authenticate and manage tokens securely using system keyrings.
Install
Add it to your toolbox
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/ag-google-docs-automation | bash Overview
Google Docs
Provides lightweight Google Docs integration via standalone OAuth scripts with no MCP server: creating, finding, reading, and editing Workspace documents. Use it to create, search, read, or edit Google Docs from local automation scripts on a Google Workspace account without an MCP server.
What it does
Provides lightweight Google Docs integration via standalone OAuth scripts, with no MCP server required - though it requires a Google Workspace account. First-time setup authenticates via browser OAuth (python scripts/auth.py login), with status and logout subcommands. All operations run through scripts/docs.py, auto-authenticating on first use: creating a document (optionally with initial content), finding documents by title, getting a document's text content by ID or full URL, appending text to the end, inserting text at the beginning, and replacing specific text within a document. Document IDs can be passed directly or extracted automatically from a full Google Docs URL.
python scripts/docs.py create "Meeting Notes"
When to use - and when NOT to
Use it to create, search, read, or edit Google Docs from local automation scripts, for text extraction, append or insert operations, or content replacement in Workspace documents, without relying on an MCP server.
Inputs and outputs
Input: a document title (for create or find), a document ID or URL, and text content for append, insert, or replace operations. Output: a created document, extracted text content, or a confirmation that an append, insert, or replace operation completed.
Integrations
Stores OAuth tokens securely in the system keyring - macOS Keychain, Windows Credential Locker, or Linux Secret Service API - under the service name google-docs-skill-oauth, with access tokens automatically refreshed via Google's cloud function when expired.
Who it's for
Developers automating Google Docs workflows from local scripts on a Google Workspace account who want to avoid standing up an MCP server.
FAQ
Common questions
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.