gdoc-to-markdown

Google Docs & Sheets Fetcher

Internal module — invoked by /bedrock:teach Phase 1 and /bedrock:sync Phase 2, not user-invocable.

Fetches a Google Docs document or Google Sheets spreadsheet and converts it to a local Markdown file. Supports both document types with automatic detection. Three layers in fallback order: MCP (preferred) → API / Public Export → Browser DOM extraction.

Dependency: Browser fallback (Layer 3) requires scripts/extract.js (relative to this skill directory).

---

Step 1 — Parse URL and Detect Type

Parse the URL. Accept these formats:

Google Docs:

• https://docs.google.com/document/d/{docId}/edit
• https://docs.google.com/document/d/{docId}/edit#heading=...
• https://docs.google.com/document/d/{docId}/edit?tab=t.0
• https://docs.google.com/document/d/{docId}
• Raw document ID (no URL) — treat as Doc by default

Google Sheets:

• https://docs.google.com/spreadsheets/d/{docId}/edit
• https://docs.google.com/spreadsheets/d/{docId}/edit#gid=0
• https://docs.google.com/spreadsheets/d/{docId}
• Raw spreadsheet ID — only if the user explicitly mentions "sheet" or "spreadsheet"

Detect type:

• URL contains /spreadsheets/d/ → Sheet
• URL contains /document/d/ → Doc
• Raw ID with no URL → default to Doc unless user context indicates Sheet

Extract the {docId} — the string between /d/ and the next / or end of path.

---

Step 2 — Layer 1: MCP (Google Docs)

The preferred layer. Checks if a Google Docs/Drive MCP server is installed and authenticated.

2.1 Check MCP availability

Use ToolSearch to check if any Google Docs or Google Drive MCP tools are available:

ToolSearch(query: "google docs drive document", max_results: 5)

Evaluate the result:

• Google Docs/Drive MCP tools found and functional → proceed to 2.2 Fetch via MCP
• MCP tools found but not authenticated → proceed to 2.3 Guide authentication
• No Google Docs MCP tools found (this is the expected case today) → log and fall through: