google-docs
Skill0 starsChanged 3 months agoMITView on GitHub
Use this skill when the requested artifact is a Google Doc, especially when the source material is agent-generated Markdown and the user cares about formatting. The tested best default is Drive import of Markdown as a native Google Doc: 1. Write clean Markdown locally. 2. Upload it to Drive with source MIME text/markdown and target MIME application/vnd.google-apps.document. 3. Verify by exporting the created Doc back to text/markdown or text/plain. This outperformed the older pandoc -> docx -> Google Doc path…
- Reads credentials
- Installs packages
17 other projects use a version of this.
Adopted by
Most recently taken up by
- JonnyCBB/claude-code-configtheir own version, first seen Nov 8, 2026
- AceDataCloud/Skillstheir own version, first seen Nov 8, 2026
- flopperj/dotfiles-coretheir own version, first seen Nov 5, 2026
- chnlich/charlie-bottheir own version, first seen Nov 1, 2026
- weininghui/skillstheir own version, first seen Oct 30, 2026
- 0mlkrizzz655335v/claude-skills-zhtheir own version, first seen Oct 15, 2026
Used with
Projects with it also use google-chat, google-calendar and 4 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
antoniolgSkillgoogle-chat
Read Google Chat spaces/threads via the Chat API, create/refresh OAuth tokens, parse Gmail Chat URLs, and list spaces. Use when asked to look up or verify messages in Google Chat or when you need API access to Chat from the CLI.
Also in 3 projects that use this
younghaiSkillgoogle-calendar
Google Calendar 일정 조회, 검색, 등록. "일정", "스케줄", "캘린더" 등을 언급하면 자동 실행. Daily Note 작성, Weekly Review에 사용.
Also in 7 projects that use this
refly-aiSkillgmail
Integrate with Gmail for email management and automation. Use when you need to: (1) send and compose emails with attachments, (2) read and search emails by criteria, (3) manage drafts and email labels, or (4) reply to email threads and conversations.
Also in 5 projects that use this
OpenAISkilllinear
Manage issues, projects & team workflows in Linear. Use when the user wants to read, create or updates tickets in Linear.
Also in 4 projects that use this
AnthropicSkillslack
Also in 3 projects that use this
ElasticSkillcreate-skill
Interactively create a new Claude Code skill and add it to the elastic-docs-skills catalog. Use when the user wants to generate a new skill, scaffold a slash command, or build automation for docs tasks.
Also in 3 projects that use this
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- openai/plugins★ 7.8ksame name
- Lilac-Labs/gini-agent★ 1.9ksame name
- Open-Curiosity/gini-agent★ 1.9ksame name
- gemini-cli-extensions/workspace★ 646same name
- sanjay3290/ai-skills★ 452same name
- refly-ai/refly-skills★ 204same name
- AceDataCloud/Skills★ 17same name
- danielkwapien/google-docs-skill★ 10same name
- pbc-os/smb-starter-kit★ 10same name
- chnlich/charlie-bot★ 9same name
7 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository36 other files it gives its agents.
- check-upstream-firstSkill
- data-verificationSkill
- deep-diveSkill
- delegation-handoffSkill
- grok-searchSkill
- is-it-really-brokenSkill
- keep-goingSkill
- learn-from-conversationsSkill
- memory-cleanupSkill
- moa-solveSkill
- mob-checkSkill
- multi-reviewSkill
- project-stewardSkill
- prove-the-setting-worksSkill
- recallSkill
- reportSkill
- robustify-doctorSkill
- skill-librarianSkill
- trust-frameworkSkill
- address-pr-commentsSkill
- diagram-renderingSkill
- find-the-real-bottleneckSkill
- live-database-maintenanceSkill
- mini-appSkill
- pr-review-sweepSkill
- scheduled-job-runnerSkill
- stop-the-noiseSkill
- upgrade-a-live-service-safelySkill
- vendor-switch-checkSkill
- writing-for-non-engineersSkill
- email-stewardSkill
- fieldySkill
- google-sheetsSkill
- google-slidesSkill
- imessage-bluebubblesSkill
- vapi-callsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
29 rules. 0 are common, 19 are distinctive, and 10 are very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
19
Distinctive
This author's own choices. Worth a look.
10
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
Use this skill when the requested artifact is a Google Doc, especially when the source material is agent-generated Markdown and the user …
- Distinctive: line 27
Write clean Markdown locally.
- Very specific: line 30
Verify by exporting the created Doc back to text/markdown or text/plain.
- Very specific: line 42
pandoc: only if you use the docx path below (brew install pandoc on macOS). - Very specific: line 64
Do not use this for Sheets or Slides.
- Distinctive: line 71
Use Drive convert-on-upload with Markdown:
- Distinctive: line 88
No extra Python packages.
- Very specific: line 95
If gog docs write --help exists on the machine, prefer newer gog for editing an existing Doc:
- Very specific: line 112
Use pandoc -> docx -> Google Doc only when the source document needs Word-specific features or the Markdown import path fails:
- Distinctive: line 125
Use the browser only for:
- Distinctive: line 131
Do not use the browser as the primary document creation backend.
- Distinctive: line 136
Write the source Markdown like a real source document, not like chat output.
- Distinctive: line 139
Use H2/H3 for structure.
- Distinctive: line 140
Use normal Markdown tables for tabular content.
- Distinctive: line 141
Use fenced code blocks with language tags.
- Distinctive: line 142
Use Markdown links, not bare URLs when the link text matters.
- Distinctive: line 143
Avoid clever HTML unless you have verified Google import preserves it.
- Distinctive: line 144
Keep long prose paragraphs readable.
- Distinctive: line 171
After creation, verify the Doc is native and formatting survived:
- Distinctive: line 185
If exact visual polish matters, open the link in the browser and inspect the first page, heading hierarchy, tables, and code blocks.
- Distinctive: line 190
Prefer a two-step pattern:
- Distinctive: line 202
Do not rewrite a human-edited Doc wholesale unless the user explicitly asks.
- Very specific: line 216
sharesends a real, externally-visible grant: Treat it like sending an email: confirm the recipient and role with the user first, and … - Distinctive: line 225
If the user explicitly asks "create a Google Doc", that is approval to create the new Drive file.
- Very specific: line 227
Ask before sharing, deleting, moving, or overwriting existing Docs.
- Distinctive: line 229
Ask before making broad edits to an existing human-owned Doc unless the requested edit is exact and scoped.
- Very specific: line 231
Prefer reversible actions: create/copy/export before destructive edits.
- Very specific: line 252
Credential lookup fails (
missing_credentials): If the helper can't find gog's token, pass credentials explicitly: export gog's refresh … - Very specific: line 263
If you accidentally uploaded a raw file (used --as raw), meta will show a non-Google MIME type.
“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Google Docs
Overview
Use this skill when the requested artifact is a Google Doc, especially when the source material is agent-generated Markdown and the user cares about formatting.
The tested best default is Drive import of Markdown as a native Google Doc:
- Write clean Markdown locally.
- Upload it to Drive with source MIME
text/markdownand target MIMEapplication/vnd.google-apps.document. - Verify by exporting the created Doc back to
text/markdownortext/plain.
This outperformed the older pandoc -> docx -> Google Doc path in testing: direct
Markdown import preserved headings, bold, italic, links, native tables, inline code, and
fenced code blocks more faithfully.
Prerequisites
gogCLI (steipete/gogcli) installed and authorized: rungog auth loginonce in the operating-system user's real$HOME. The bundledscripts/gworkspace.pyreuses gog's stored OAuth refresh token, so no separate Google Cloud setup is needed.python3onPATH(the helper is stdlib-only — nopip installrequired).pandoconly if you use the docx path below (brew install pandocon macOS).- The helper resolves credentials in this order: explicit
--refresh-token-file/--client-secret-file, thenGOOGLE_REFRESH_TOKEN/GOOGLE_CLIENT_ID/GOOGLE_CLIENT_SECRETenv vars, then gog's stored token. If lookup fails it exits with{"error": "missing_credentials"}— see Common Pitfalls for the manual escape hatch.
Run commands from the skill directory so
scripts/gworkspace.pyresolves relative to$PWD, or use the full pathskills/google-docs/scripts/gworkspace.pyfrom the repo root.
$HOME shadowing: some agent runtimes rewrite
$HOMEto a sandbox path where gog's auth doesn't exist. If credential lookup fails in that environment, pointHOMEat the real OS user home before invoking the helper.
When to Use
- User asks for a Google Doc, report, memo, proposal, brief, agenda, or notes document.
- User gives Markdown and wants it turned into a formatted Google Doc.
- User asks whether to use
gog, raw API, or browser for Docs. - User asks to export, inspect, copy, or verify a Google Doc.
Do not use this for Sheets or Slides; load google-sheets or google-slides
instead.
Decision Tree
Best default for new docs from Markdown
Use Drive convert-on-upload with Markdown:
python3 scripts/gworkspace.py upload report.md \
--as doc \
--name "Quarterly Report" \
--parent FOLDER_IDFOLDER_ID is optional; omit --parent to create in My Drive root. To target a
specific folder, copy the ID from its Drive URL
(https://drive.google.com/drive/folders/<FOLDER_ID>), list folders with
gog drive ls --json, or create one with
python3 scripts/gworkspace.py mkdir "Reports".
Why this is the default:
- No extra Python packages.
- Reuses existing
gogOAuth refresh token. - Produces a native Google Doc, not an uploaded
.mdor.docxfile. - Preserves Markdown formatting well, including code fences and tables.
When to use newer gog directly
If gog docs write --help exists on the machine, prefer newer gog for editing an
existing Doc:
# This path requires a newer gog with docs editing commands.
gog docs write --help >/dev/null 2>&1 || { echo "gog docs write not available; use Drive import instead"; exit 1; }
gog docs create "Draft Title" --parent FOLDER_ID --json
gog docs write DOC_ID --markdown --text "$(cat report.md)" --append --jsonNewer upstream gog versions include Docs editing primitives such as
docs write --markdown, docs format, docs insert-table, and raw Docs inspection.
Local v0.9.0 did not expose these commands during the one occasion test, so do not
assume they exist. Check help first.
When to use pandoc/docx
Use pandoc -> docx -> Google Doc only when the source document needs Word-specific
features or the Markdown import path fails:
pandoc report.md -o report.docx
python3 scripts/gworkspace.py upload report.docx --as doc --name "Quarterly Report"This path preserved headings, lists, tables, links, and basic text styling in testing, but degraded fenced code blocks compared with direct Markdown import.
When to use browser automation
Use the browser only for:
- visual QA after API creation,
- final manual polish that APIs cannot express quickly,
- one-off "File -> Save as Google Docs" conversion if API conversion is unavailable.
Do not use the browser as the primary document creation backend. It is slower, less repeatable, and more fragile than Drive import or Docs API calls.
Markdown Authoring Rules
Write the source Markdown like a real source document, not like chat output.
- One H1 title at the top.
- Use H2/H3 for structure.
- Use normal Markdown tables for tabular content.
- Use fenced code blocks with language tags.
- Use Markdown links, not bare URLs when the link text matters.
- Avoid clever HTML unless you have verified Google import preserves it.
- Keep long prose paragraphs readable; Google Docs import handles normal paragraphs well.
Good source (outer fence shown with ~~~ so the inner ``` code block renders
correctly):
# Quarterly Business Review
## Executive Summary
Revenue increased **18%** quarter-over-quarter.
## Metrics
| Metric | Q1 | Q2 |
| ------ | ----: | ----: |
| MRR | $420k | $496k |
```python
def churn_rate(lost, start):
return round(lost / start * 100, 2)
```Verification
After creation, verify the Doc is native and formatting survived:
python3 scripts/gworkspace.py meta DOC_ID
python3 scripts/gworkspace.py export DOC_ID --mime text/markdown --out /tmp/doc-roundtrip.mdCheck that:
mimeTypeisapplication/vnd.google-apps.document.- Round-trip Markdown still contains headings, tables, links, inline code, and fenced code blocks.
- The returned
webViewLinkopens as a Google Docs URL.
If exact visual polish matters, open the link in the browser and inspect the first page, heading hierarchy, tables, and code blocks.
Editing Existing Docs
Prefer a two-step pattern:
- Export or inspect the existing doc.
- Apply a targeted edit with the highest-level tool available.
Options in order:
- Newer
gog docs write/format/find-replaceif present. - Raw Docs API
documents.batchUpdatefor precise paragraph/text/table/image operations. - Browser for visual/manual edits only when the API path is too expensive for the task.
Do not rewrite a human-edited Doc wholesale unless the user explicitly asks. Export first, preserve structure, then apply a minimal diff.
Sharing and Drive Helpers
The bundled helper also exposes Drive operations the skills reference:
python3 scripts/gworkspace.py mkdir "Reports" # create a folder, returns its ID
python3 scripts/gworkspace.py meta DOC_ID # metadata + webViewLink
python3 scripts/gworkspace.py token # mint an access token for raw Docs API calls
python3 scripts/gworkspace.py share DOC_ID --email a@b.com --role reader # share — IRREVERSIBLEshare sends a real, externally-visible grant. Treat it like sending an email:
confirm the recipient and role with the user first, and never share without explicit
approval. --notify additionally emails the recipient.
For raw Docs API work (documents.batchUpdate), mint a token with gworkspace.py token
and call the REST endpoint directly.
Safety and Approval
- If the user explicitly asks "create a Google Doc", that is approval to create the new Drive file.
- Ask before sharing, deleting, moving, or overwriting existing Docs.
shareis irreversible — confirm recipient + role first. - Ask before making broad edits to an existing human-owned Doc unless the requested edit is exact and scoped.
- Prefer reversible actions: create/copy/export before destructive edits.
Common Pitfalls
- Using old local gog Docs commands for formatting. Local
gog v0.9.0created title-only Docs and did not supportdocs write --markdownduring testing. Checkgog docs --helpbefore relying on editing commands. - Uploading Markdown without conversion.
gog drive upload report.mdcreates a Drive file containing Markdown, not a native Google Doc. Use Drive API target MIMEapplication/vnd.google-apps.document, or a newer gog conversion flag if available. - Wrong source MIME. Markdown import needs source MIME
text/markdown; guessing as plain text can fail or degrade formatting. - Assuming docx is better. In testing, direct Markdown import preserved code fences
and inline code better than
pandoc -> docx -> Google Doc. - Skipping verification. A successful upload is not enough. Confirm native Google Doc MIME type and round-trip export.
- Credential lookup fails (
missing_credentials). If the helper can't find gog's token, pass credentials explicitly: export gog's refresh token to a 0600 file withgog auth tokens export <account> --output /tmp/tok.json --force, then run the helper with--refresh-token-file /tmp/tok.json --client-secret-file <gog credentials.json>. The helper refuses credential files that are group/world-readable or not owned by you —chmod 600them. These flags work before or after the subcommand. For a gog named client or a non-default gog home, use--gog-client <name>/--gog-home <dir>(or theGOG_CLIENT/GOG_HOMEenv vars). exportreturns 403. Drive's export endpoint only works on Google-native files. If you accidentally uploaded a raw file (used--as raw),metawill show a non-Google MIME type; re-upload with the correct--astarget.
One-Shot Recipe
mkdir -p /tmp/gdoc-build
cat > /tmp/gdoc-build/report.md <<'MD'
# Report Title
## Summary
Write the report here.
MD
python3 scripts/gworkspace.py upload /tmp/gdoc-build/report.md --as doc --name "Report Title"Return the resulting webViewLink to the user.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

