gdoc

Read, write, and comment on Google Docs with tab-aware Markdown synchronization.

8|1|Updated Jan 21, 2024
One-click install
npx skills add https://github.com/azigler/dotfiles --skill gdoc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gdoc
Source: https://github.com/azigler/dotfiles/tree/main/agents/skills/gdoc
Command: npx skills add https://github.com/azigler/dotfiles --skill gdoc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you reliably read and update Google Docs through an automated, tab-aware workflow while ensuring every agent-produced document follows a shared formatting contract.

Core Features & Use Cases

  • Read & inspect docs: Fetch document content as Markdown and list available tabs to understand where content lives.
  • Write & replace content: Update whole-document Markdown (with optional tab targeting) while supporting Google Docs rich-text output paths.
  • Collaborate with comments: List existing comments and post replies under the service account identity.

Quick Start

Create and symlink the shim for your project by running ln -sf ~/.claude/skills/gdoc/gdoc.sh scripts/gdoc.sh.

Frequently Asked Questions about gdoc

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate writing Markdown content to Google Docs with consistent formatting?

You can write Markdown content to Google Docs by using a connector runtime and a service account key. The workflow enforces a canonical styling contract, applying specific rules like Arial 11pt for body text and defined point sizes for headings.

Can I manage multi-tab Google Docs editing through an automated workflow?

Yes, the workflow supports tab-aware operations via a shell script. You can target single-tab or multi-tab editing workflows, allowing you to read, write, and replace content on specific tabs within a single Google Doc.

What do I need to set up to automate reading and commenting on Google Docs?

You need a Google service account key for authentication and the bun runtime to execute the connector. You must also symlink the provided shell script into your project's scripts directory to start automating document interactions.

Does this Google Docs automation approach support rich-text formatting from Markdown?

Yes, the automation supports Google Docs rich-text output paths via the Docs API. It converts Markdown content while strictly enforcing formatting rules such as Arial 11pt for body text, 20pt for H1, 16pt for H2, and 13pt for H3.

How can I post replies to Google Docs comments using a service account?

You can list existing comments and post replies under the service account identity through the automated connector. This allows programmatic collaboration and interaction with document comments without manual login.

What are the limitations of using a service account for Google Docs document automation?

Using a service account means comments and edits are posted under that specific identity rather than a personal user account. Additionally, the workflow enforces a strict styling contract, so any pre-existing manual formatting may be overwritten during synchronization.