← ClaudeAtlas

google-docslisted

Use when creating, importing, formatting, editing, exporting, or quality-checking Google Docs from agent-generated markdown or local files.
TechNickAI/hermes-skills · ★ 0 · Data & Documents · score 76
Install: claude install-skill TechNickAI/hermes-skills
# 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**: 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 in testing: direct Markdown import preserved headings, bold, italic, links, native tables, inline code, and fenced code blocks more faithfully. ## Prerequisites - **`gog` CLI** (steipete/gogcli) installed and authorized: run `gog auth login` once in the operating-system user's real `$HOME`. The bundled `scripts/gworkspace.py` reuses gog's stored OAuth refresh token, so no separate Google Cloud setup is needed. - **`python3`** on `PATH` (the helper is stdlib-only — no `pip install` required). - **`pandoc`** only if you use the docx path below (`brew install pandoc` on macOS). - The helper resolves credentials in this order: explicit `--refresh-token-file` / `--client-secret-file`, then `GOOGLE_REFRESH_TOKEN` / `GOOGLE_CLIENT_ID` / `GOOGLE_CLIENT_SECRET` env vars, then gog's stored token. If lookup fails it exits with `{"error": "missing_credentials"}` — see Common Pitfalls for the manual escape hatch. > **