How do I install the Google Docs skill?

Run npx skillmds@latest add acedatacloud/google-docs in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Google Docs safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Google Docs?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Google Docs free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Google Docs?

acedatacloud (@acedatacloud) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Google Docs by acedatacloud — Agent Skill

Name: Google Docs
Rating: 4.5 (4 reviews)
Author: acedatacloud

File contents

Drive Google Docs via curl + jq. The user's OAuth bearer token is in $GOOGLE_DOCS_TOKEN; every call needs Authorization: Bearer $GOOGLE_DOCS_TOKEN. Base URL: https://docs.googleapis.com/v1/documents. The token carries documents.readonly (+ identity); writes need documents.

Failures are {"error":{"code","message","status"}} — show verbatim. 401 = re-install. 403 PERMISSION_DENIED on a write = read-only scope.

The doc id is the …/document/d/<ID>/edit segment of the URL.

D="https://docs.googleapis.com/v1/documents"; AUTH="Authorization: Bearer $GOOGLE_DOCS_TOKEN"
# Read the document. The body is a tree of structural elements; pull plain text:
curl -sS -H "$AUTH" "$D/DOC_ID" \
  | jq -r '.title, ([.body.content[]?.paragraph?.elements[]?.textRun?.content] | join(""))'

Create & edit

# Create an empty doc
curl -sS -X POST -H "$AUTH" -H "Content-Type: application/json" \
  -d '{"title":"Meeting notes 2026-06-21"}' "$D" | jq '{documentId, title}'

# Insert text at the start (index 1) via batchUpdate (confirm first)
curl -sS -X POST -H "$AUTH" -H "Content-Type: application/json" \
  -d '{"requests":[{"insertText":{"location":{"index":1},"text":"Hello\n"}}]}' \
  "$D/DOC_ID:batchUpdate" | jq '.documentId'

# Replace all occurrences of a placeholder
curl -sS -X POST -H "$AUTH" -H "Content-Type: application/json" \
  -d '{"requests":[{"replaceAllText":{"containsText":{"text":"{{name}}","matchCase":true},"replaceText":"Alex"}}]}' \
  "$D/DOC_ID:batchUpdate" | jq '.replies'

Gotchas

The document model is index-based: text edits target character indices, and every insert shifts later indices — for multiple inserts, apply them back-to-front or recompute indices between calls.
To get clean Markdown/plain text, walk body.content[].paragraph.elements[] .textRun.content (the jq above). Tables / lists need deeper traversal.
Creating a doc puts it in the user's Drive root; use the google-drive skill to move/share it.

---name: google-docsdescription: Read and edit Google Docs via the Docs v1 REST API. Use when the user mentions a Google Doc, reading a document's text, creating a doc, inserting or replacing text, or exporting a doc's content.license: Apache-2.0--- Drive **Google Docs** via `curl + jq`. The user's OAuth bearer token is in `$GOOGLE_DOCS_TOKEN`; every call needs `Authorization: Bearer $GOOGLE_DOCS_TOKEN`. Base URL: `https://docs.googleapis.com/v1/documents`. The token carries `documents.readonly` (+ identity); writes need `documents`. Failures are `{"error":{"code","message","status"}}` — show verbatim. `401` = re-install. `403 PERMISSION_DENIED` on a write = read-only scope. The doc id is the `…/document/d/<ID>/edit` segment of the URL. ```bash D="https://docs.googleapis.com/v1/documents"; AUTH="Authorization: Bearer $GOOGLE_DOCS_TOKEN" # Read the document. The body is a tree of structural elements; pull plain text: curl -sS -H "$AUTH" "$D/DOC_ID" \ | jq -r '.title, ([.body.content[]?.paragraph?.elements[]?.textRun?.content] | join(""))' ``` ## Create & edit ```bash # Create an empty doc curl -sS -X POST -H "$AUTH" -H "Content-Type: application/json" \ -d '{"title":"Meeting notes 2026-06-21"}' "$D" | jq '{documentId, title}' # Insert text at the start (index 1) via batchUpdate (confirm first) curl -sS -X POST -H "$AUTH" -H "Content-Type: application/json" \ -d '{"requests":[{"insertText":{"location":{"index":1},"text":"Hello\n"}}]}' \ "$D/DOC_ID:batchUpdate" | jq '.documentId' # Replace all occurrences of a placeholder curl -sS -X POST -H "$AUTH" -H "Content-Type: application/json" \ -d '{"requests":[{"replaceAllText":{"containsText":{"text":"{{name}}","matchCase":true},"replaceText":"Alex"}}]}' \ "$D/DOC_ID:batchUpdate" | jq '.replies' ``` ## Gotchas - The document model is **index-based**: text edits target character indices, and every insert shifts later indices — for multiple inserts, apply them back-to-front or recompute indices between calls. - To get clean Markdown/plain text, walk `body.content[].paragraph.elements[] .textRun.content` (the jq above). Tables / lists need deeper traversal. - Creating a doc puts it in the user's Drive root; use the `google-drive` skill to move/share it.

Frequently asked questions

Google Docs