Agent skill

Gdoc To Markdown

by iurykrieger in iurykrieger/claude-bedrock

Internal fetcher module for Google Docs and Sheets. An agent skill from iurykrieger/claude-bedrock.

MITAuto-check: notesDocuments & Office

Install Gdoc To Markdown

skills CLI
$ npx skills add iurykrieger/claude-bedrock --skill gdoc-to-markdown -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install iurykrieger/claude-bedrock gdoc-to-markdown --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/iurykrieger/claude-bedrock.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/gdoc-to-markdown .claude/skills/gdoc-to-markdown && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
gdoc-to-markdown
GitHub stars
105
Used in
1 other repo
Token cost
~3.8k tokens
SKILL.md length
1,762 words
Files
2 (incl. scripts)
Skills in repo
10
Repo updated
First seen
Licence
MIT

At a glance

Internal fetcher module for Google Docs and Sheets. An agent skill from iurykrieger/claude-bedrock.

  • Works in 4 steps: Parse URL and Detect Type → Layer 1: MCP (Google Docs) → Layer 2: API → …
  • Tasks that involve Cloud office suites
  • SKILL.md covers Step 1 — Parse URL and Detect…, Step 2 — Layer 1: MCP (Google…, Step 3 — Layer 2: API and Step 4 — Layer 3: Browser…, plus 3 more sections
  • Runs JavaScript scripts from its folder; calls curl; reaches docs.google.com and googleapis.com; needs GOOGLE_ACCESS_TOKEN

What it does

Gdoc To Markdown is an agent skill from iurykrieger/claude-bedrock. Internal fetcher module for Google Docs and Sheets. Fetches content via MCP (preferred, when available), Google API with bearer token or public URL export (fallback), or browser DOM extraction via Claude in Chrome (last resort) and returns Markdown. Used by /bedrock:learn and /bedrock:sync — not intended for direct user invocation.

Its SKILL.md is about 3.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/extract.js`).

It sits in Documents & Office, covering Cloud office suites, Markdown and MCP servers. It works with Model Context Protocol, Google Docs, Google Sheets and Obsidian. The repository describes itself as: Second Brain automation for Obsidian vaults — entity management, ingestion, compression, and sync via Claude Code skills. The licence is MIT.

When your agent uses it

  • Tasks that involve Cloud office suites
  • Tasks that involve Markdown
  • Tasks that involve MCP servers

Example prompts

  • “/gdoc-to-markdown”

Requirements

  • Node.js
  • A credential in GOOGLE_ACCESS_TOKEN
  • Pre-approved tools (allowed-tools): Bash, Read, Write, WebFetch, ToolSearch, mcp__claude-in-chrome__*

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Parse URL and Detect Type
  2. Layer 1: MCP (Google Docs)
  3. Layer 2: API
  4. Layer 3: Browser (Claude in Chrome)

What it can do on your machine

Read from SKILL.md and the folder at commit 7cac16c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash
    • Read
    • Write
    • WebFetch
    • ToolSearch
    • mcp__claude-in-chrome__*

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (JavaScript), which the agent can run.

    Shell commands in SKILL.md call:

    • curl

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • docs.google.com
    • googleapis.com
    • sheets.googleapis.com

    Also links to:

    • developers.google.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • GOOGLE_ACCESS_TOKEN

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Gdoc To Markdown loads about 3.8k tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 1,762 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~88
When it runs · the whole SKILL.md, loaded when a task matches
~3.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Bash, Read, Write, WebFetch, ToolSearch, mcp__claude-in-chrome__*

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from iurykrieger/claude-bedrock at commit 7cac16c, republished under its MIT licence (© iurykrieger). 1,762 words, ~3,834 tokens.

Download SKILL.mdSave it as .claude/skills/gdoc-to-markdown/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
gdoc-to-markdown
description
Internal fetcher module for Google Docs and Sheets. Fetches content via MCP (preferred, when available), Google API with bearer token or public URL export (fallback), or browser DOM extraction via Claude in Chrome (last resort) and returns Markdown. Used by /bedrock:learn and /bedrock:sync — not intended for direct user invocation.
allowed-tools
Bash, Read, Write, WebFetch, ToolSearch, mcp__claude-in-chrome__*
user_invocable
false

Google Docs & Sheets Fetcher

Internal module — invoked by /bedrock:learn 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:

MCP not available: No Google Docs/Drive MCP server installed. When a Google Docs MCP becomes available, install it for direct document access. Falling back to API (Layer 2).

2.2 Fetch via MCP

Use the Google Docs MCP tools to fetch the document content. The specific tool depends on what the MCP exposes.

  • Success → convert content to Markdown if not already, proceed to Output Contract
  • Error → log the error and fall through to Layer 2:

MCP fetch failed: {error message}. Falling back to API (Layer 2).

2.3 Guide authentication

If an MCP is installed but not authenticated, guide the user:

MCP not authenticated: A Google Docs MCP server is installed but requires authentication. Complete the authentication flow as prompted by the MCP server. After authentication, Google documents can be fetched directly via MCP.

Ask the user: "Would you like to authenticate the Google Docs MCP now, or skip to API fallback (Layer 2)?"

  • User wants to authenticate → invoke the MCP authentication tool, wait for the user to complete the flow, then retry 2.2 Fetch via MCP
  • User declines → log "User declined MCP authentication, falling to Layer 2" → continue to Step 3

Step 3 — Layer 2: API

Uses the Google Drive/Sheets API with a bearer token or public URL export.

Strategy selection
  • If GOOGLE_ACCESS_TOKEN env var exists → use Strategy A (API with token)
  • If GOOGLE_ACCESS_TOKEN is NOT set → use Strategy B (Public Export)
  • If Strategy B fails (private document) → guide and fall through to Layer 3:

API not available: This document requires authentication and no GOOGLE_ACCESS_TOKEN is set. Generate a token at https://developers.google.com/oauthplayground/ with the https://www.googleapis.com/auth/drive.readonly scope. Export: export GOOGLE_ACCESS_TOKEN="your-token". Falling back to Browser extraction (Layer 3).

Inform the caller which strategy is being used and whether the document is a Doc or Sheet.


Google Docs — Strategy A (API with token)
A.1 Fetch as Markdown

Use WebFetch:

WebFetch(
  url: "https://www.googleapis.com/drive/v3/files/{docId}/export?mimeType=text/markdown",
  headers: { "Authorization": "Bearer {GOOGLE_ACCESS_TOKEN}" },
  prompt: "Return the COMPLETE raw content exactly as-is. Do not summarize or truncate."
)

If WebFetch cannot send the Authorization header, fall back to Bash:

bash
curl -sL -H "Authorization: Bearer ${GOOGLE_ACCESS_TOKEN}" \
  "https://www.googleapis.com/drive/v3/files/{docId}/export?mimeType=text/markdown"
A.2 Validate
  • Valid Markdown content → proceed to Output Contract
  • 401 → guide and fall through to Layer 3:

API authentication failed: Google API returned 401. The token may be expired or invalid. Refresh your token at https://developers.google.com/oauthplayground/. Falling back to Browser extraction (Layer 3).

  • 403 → abort (permissions issue, no fallback can bypass):

API access denied: Google API returned 403. You do not have access to this document. Verify document sharing permissions in Google Docs.

  • 404 → abort:

Document not found: Google API returned 404. The document ID may be incorrect. Verify the URL or document ID.

  • Empty response → guide and fall through to Layer 3:

API returned empty: The document appears to be empty or the export failed. Falling back to Browser extraction (Layer 3).

Do not post-process the Markdown — return Google's native output as-is.


Google Docs — Strategy B (Public Export)
B.1 Fetch via public endpoint
bash
curl -sL "https://docs.google.com/document/d/{docId}/export?format=md"

The -L flag follows the 307 redirect to *.googleusercontent.com.

B.2 Validate
  • Valid Markdown content → proceed to Output Contract
  • HTML error page or Google login page → document is private, fall through to Layer 3:

Public export not available: Document is private and requires authentication. Set GOOGLE_ACCESS_TOKEN for API access, or ensure you are logged into Google in Chrome. Falling back to Browser extraction (Layer 3).

  • Empty response → fall through to Layer 3:

Public export returned empty: The document appears to be empty or inaccessible. Falling back to Browser extraction (Layer 3).


Google Sheets — Strategy A (API with token)
A.1 List all sheet tabs
bash
curl -sL -H "Authorization: Bearer ${GOOGLE_ACCESS_TOKEN}" \
  "https://sheets.googleapis.com/v4/spreadsheets/{docId}?fields=sheets.properties"

Returns JSON with sheets[].properties.title (sheet name) and sheets[].properties.sheetId (gid).

A.2 Export each tab as CSV

For each tab:

bash
curl -sL -H "Authorization: Bearer ${GOOGLE_ACCESS_TOKEN}" \
  "https://docs.google.com/spreadsheets/d/{docId}/export?format=csv&gid={sheetGid}"

If the export endpoint fails for a specific tab, fall back to the Sheets API values endpoint:

bash
curl -sL -H "Authorization: Bearer ${GOOGLE_ACCESS_TOKEN}" \
  "https://sheets.googleapis.com/v4/spreadsheets/{docId}/values/{sheetName}!A:ZZ"

Convert the JSON values array rows to comma-separated values to produce CSV.

A.3 Convert CSV to Markdown tables

For each tab's CSV:

  1. Parse CSV correctly — respect quoted fields (fields containing commas, newlines, or double quotes wrapped in "..." are a single field)
  2. First row = header → | col1 | col2 | ... |
  3. Separator row → | --- | --- | ... |
  4. Data rows → | val1 | val2 | ... |
  5. Escape pipe characters | within cell values as \|
A.4 Concatenate all tabs

For each tab, prepend: ## {sheet_name} followed by a blank line, then the Markdown table, then a blank line. Tabs appear in the same order as returned by the Sheets API metadata.

A.5 Validate
  • At least one tab produced valid content → proceed to Output Contract
  • 401 → guide and fall through to Layer 3:

API authentication failed: Sheets API returned 401. The token may be expired or invalid. Refresh your token at https://developers.google.com/oauthplayground/. Falling back to Browser extraction (Layer 3).

  • 403 → abort:

API access denied: Sheets API returned 403. You do not have access to this spreadsheet. Verify spreadsheet sharing permissions or ensure token has drive.readonly scope.

  • 404 → abort:

Spreadsheet not found: Sheets API returned 404. The spreadsheet ID may be incorrect. Verify the URL.

  • All tabs empty → fall through to Layer 3:

API returned empty: The spreadsheet appears to be empty. Falling back to Browser extraction (Layer 3).


Google Sheets — Strategy B (Public Export)
B.1 Export first tab
bash
curl -sL "https://docs.google.com/spreadsheets/d/{docId}/gviz/tq?tqx=out:csv&gid=0"
Show full SKILL.md (708 more words)Show less
B.2 Validate and convert
  • Valid CSV → convert to Markdown table (same rules as Strategy A step A.3), proceed to Output Contract
  • HTML error page or Google login page → spreadsheet is private, fall through to Layer 3:

Public export not available: Spreadsheet is private and requires authentication. Set GOOGLE_ACCESS_TOKEN for API access, or ensure you are logged into Google in Chrome. Falling back to Browser extraction (Layer 3).

  • Empty response → fall through to Layer 3:

Public export returned empty: The spreadsheet appears to be empty or inaccessible. Falling back to Browser extraction (Layer 3).

B.3 Multi-sheet limitation

Inform the caller: "Public export can only retrieve the first sheet tab. To export all tabs, set GOOGLE_ACCESS_TOKEN."

Format the single tab with heading ## Sheet1 followed by the Markdown table.


Step 4 — Layer 3: Browser (Claude in Chrome)

Last resort. Opens the document in Chrome and extracts content via DOM scraping.

4.1 Load Chrome tools

Via ToolSearch:

select:mcp__claude-in-chrome__tabs_context_mcp,mcp__claude-in-chrome__tabs_create_mcp
select:mcp__claude-in-chrome__navigate
select:mcp__claude-in-chrome__javascript_tool

If Chrome MCP tools are not available, abort:

Browser not available: Claude in Chrome MCP is not installed or not running. Install the Claude in Chrome extension and ensure it is connected. No further fallback layers available — cannot fetch this document.

4.2 Get browser context
mcp__claude-in-chrome__tabs_context_mcp(createIfEmpty: true)
4.3 Navigate to the document
mcp__claude-in-chrome__tabs_create_mcp()
mcp__claude-in-chrome__navigate(url: "<full document URL>", tabId: <id>)
4.4 Execute extraction script

Read scripts/extract.js from this skill's directory using the Read tool. Then execute it:

mcp__claude-in-chrome__javascript_tool(
  action: "javascript_exec",
  text: <contents of extract.js>,
  tabId: <id>
)

The script returns JSON:

json
{
  "status": "ready",
  "totalLength": 31450,
  "totalChunks": 4,
  "chunkSize": 10000,
  "title": "Document Title",
  "docType": "doc",
  "instructions": "Run window.__gdoc.chunk(0), window.__gdoc.chunk(1), etc."
}

If the script returns an error field: handle accordingly (login page, empty content, wrong page).

4.5 Read chunks

For each chunk from 0 to totalChunks - 1:

mcp__claude-in-chrome__javascript_tool(
  action: "javascript_exec",
  text: "window.__gdoc.chunk(N)",
  tabId: <id>
)

Concatenate all chunks into a single Markdown string.

4.6 Validate

Check that the result is not empty and not a login page. If validation fails:

Browser extraction failed: Could not extract content from the document. Ensure you are logged into Google in Chrome and the document has loaded. No further fallback layers available — cannot fetch this document.


Output Contract

Save the file
  • Doc → save to /tmp/gdoc_{docId}.md
  • Sheet → save to /tmp/gsheet_{docId}.md

Write the Markdown content using the Write tool. Verify the file was written by reading the first few lines.

Return to caller

Return to /bedrock:learn or /bedrock:sync:

  • Output file path: /tmp/gdoc_{docId}.md or /tmp/gsheet_{docId}.md
  • Document type: Doc or Sheet
  • Layer used: MCP, API, Public Export, or Browser
  • Tabs exported (Sheets only): number of tabs

The caller copies the file to $TEACH_TMP/<slug>.md.


Hard Rules

RuleDetail
Read-onlyNever write back to Google Docs or Sheets.
No OAuth interactive flowsUse only existing MCP auth, static token from GOOGLE_ACCESS_TOKEN, or browser session.
Validate before savingDo not save empty files, HTML error pages, or Google login pages.
Layer order is sacredAlways try MCP → API → Browser, in that order. Never skip ahead unless a layer is unavailable or user declines.
Guide before falling throughIf a layer exists but is misconfigured, guide the user before moving to the next layer.
No Markdown post-processing for DocsReturn Google's native Markdown export as-is (API layer).
Export all sheet tabs (API)Do not skip tabs or allow selective export.
Respect CSV quoting rulesQuoted fields are single fields, even with commas or newlines inside.
Best-effortIf a layer fails, try the next. If all fail, report and abort — do not retry indefinitely.
403 is terminalPermission denied cannot be resolved by falling to another layer — abort immediately.

Troubleshooting

ProblemSolution
No Google Docs MCP availableExpected today — skip to API layer automatically
API returns 401Token expired — refresh at https://developers.google.com/oauthplayground/
API returns 403User lacks access to the document/spreadsheet
API returns 404Document ID is wrong — verify URL
Public export returns HTML login pageDocument is private — set GOOGLE_ACCESS_TOKEN or use browser
Content is truncatedGoogle Drive API limits exports to 10 MB — document may be too large
WebFetch fails to send Authorization headerFall back to curl -H "Authorization: Bearer {token}" -sL "<url>" via Bash
Sheets 403 for metadataToken may lack drive.readonly or spreadsheets.readonly scope
Sheets CSV export returns HTMLExport endpoint blocked — fall back to Sheets API values endpoint
Public Sheets export returns only first tabExpected limitation — multi-sheet export requires GOOGLE_ACCESS_TOKEN
Chrome extension disconnectedRefresh extension, call tabs_context_mcp(createIfEmpty: true)
Browser redirects to Google loginUser not authenticated — log into Google in Chrome, retry
extract.js returns emptyDocument may not have loaded — wait and retry, or check if document is empty

© iurykrieger, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (scripts) in skills/gdoc-to-markdown of iurykrieger/claude-bedrock.

  • SKILL.md
  • scripts/extract.js

Open the folder on GitHubat commit 7cac16c

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in iurykrieger/claude-bedrock, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Gdoc To Markdown next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Gdoc To Markdown compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Gdoc To Markdown this skilliurykrieger/claude-bedrock1051 repos~3.8kAutomated safety check: NotesMIT
Managing Google Workspacetaylorwilsdon/google_workspace_mcp3.3k—~2.9kAutomated safety check: PassMIT
Google Workspaceespennilsen/pi122—~3.4kAutomated safety check: PassMIT
Recipe Generate Report From Sheetgoogleworkspace/cli31k—~287Automated safety check: PassApache-2.0
Teachccplugins/awesome-claude-code-plugins970—~5.9kAutomated safety check: NotesApache-2.0
MineruNebutra/MinerU-Skill123—~1.4kAutomated safety check: PassMIT

Similar skills

  • Managing Google Workspace

    taylorwilsdon/google_workspace_mcp

    Manages Google Workspace operations across 12 services (Gmail, Drive, Calendar, Docs, Sheets, Slides, Forms, Tasks, Contacts, Chat, Apps Script, Custom Search).

    3.3k GitHub stars~2.9k tokensUpdated yesterday
    Documents & OfficeAuto-check passed
  • Google Workspace

    espennilsen/pi

    Manage Google Workspace via the gws CLI — Drive, Gmail, Sheets, Docs, Slides, People, Chat, Meet, Forms, and cross-service workflows.

    122 GitHub stars~3.4k tokensUpdated 19 days ago
    Documents & OfficeAuto-check passed
  • Read data from a Google Sheet and create a formatted Google Docs report.

    31k GitHub stars~287 tokensUpdated 4 days ago
    Documents & OfficeAuto-check passed
  • Teach

    ccplugins/awesome-claude-code-plugins

    Teaches the Second Brain to recognize a new external data source.

    970 GitHub stars~5.9k tokensUpdated 1 mo ago
    Documents & OfficeAuto-check: notes
  • Mineru

    Nebutra/MinerU-Skill

    An AI-Native skill for parsing PDF / Office / image files into clean Markdown with MinerU — a fast, zero-config document parser for AI agents.

    123 GitHub stars~1.4k tokensUpdated 16 days ago
    Documents & OfficeAuto-check passed
  • Mineru

    Nebutra/MinerU-Skill

    An AI-Native skill for parsing PDF / Office / image files into Markdown with MinerU — a fast, zero-config document parser for AI agents.

    123 GitHub stars~504 tokensUpdated 16 days ago
    Documents & OfficeAuto-check passed

More from iurykrieger/claude-bedrock

All 10 skills in this repo
  • Confluence To Markdown

    iurykrieger/claude-bedrock

    Internal fetcher module for Confluence pages. An agent skill from iurykrieger/claude-bedrock.

    105 GitHub starsUsed in 1 repo~2.8k tokens
    Auto-check: notes
  • Healthcheck

    iurykrieger/claude-bedrock

    Read-only vault health diagnostic. An agent skill from iurykrieger/claude-bedrock.

    105 GitHub starsUsed in 1 repo~3.7k tokens
    Auto-check: notes
  • Vaults

    iurykrieger/claude-bedrock

    Manage registered Bedrock vaults. An agent skill from iurykrieger/claude-bedrock.

    105 GitHub starsUsed in 1 repo~1.3k tokens
    Auto-check: notes
  • Setup

    iurykrieger/claude-bedrock

    Initialize any folder as a Bedrock-powered Obsidian vault. An agent skill from iurykrieger/claude-bedrock.

    105 GitHub starsUsed in 1 repo~11k tokens
    Auto-check: notes
  • Compress

    iurykrieger/claude-bedrock

    Vault alignment engine. An agent skill from iurykrieger/claude-bedrock.

    105 GitHub starsUsed in 1 repo~9.9k tokens
    Auto-check: warnings
  • Sync

    iurykrieger/claude-bedrock

    Re-synchronizes the vault with external sources. An agent skill from iurykrieger/claude-bedrock.

    105 GitHub starsUsed in 1 repo~11k tokens
    Auto-check: warnings

Questions about Gdoc To Markdown

What does Gdoc To Markdown do?

Internal fetcher module for Google Docs and Sheets. An agent skill from iurykrieger/claude-bedrock. Gdoc To Markdown is an agent skill from iurykrieger/claude-bedrock. Internal fetcher module for Google Docs and Sheets.

When should I use Gdoc To Markdown?

Gdoc To Markdown fits situations like: tasks that involve Cloud office suites; tasks that involve Markdown; tasks that involve MCP servers.

How do I install Gdoc To Markdown in Claude Code?

Run `npx skills add iurykrieger/claude-bedrock --skill gdoc-to-markdown -a claude-code`. Or copy the skill folder (skills/gdoc-to-markdown in iurykrieger/claude-bedrock) into .claude/skills/gdoc-to-markdown in your project. Claude Code loads it when a task matches its description.

How do I install Gdoc To Markdown in Codex?

Run `npx skills add iurykrieger/claude-bedrock --skill gdoc-to-markdown -a codex`. Or copy the skill folder (skills/gdoc-to-markdown in iurykrieger/claude-bedrock) into .agents/skills/gdoc-to-markdown in your project. Codex loads it when a task matches its description.

Can I use Gdoc To Markdown in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add iurykrieger/claude-bedrock --skill gdoc-to-markdown -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gdoc-to-markdown, .gemini/skills/gdoc-to-markdown, .github/skills/gdoc-to-markdown and .opencode/skills/gdoc-to-markdown in your project.

What does Gdoc To Markdown need to run?

Going by SKILL.md and its folder, Gdoc To Markdown needs JavaScript for the scripts in its folder, the command-line tools its instructions call (curl) and credentials named GOOGLE_ACCESS_TOKEN. Our summary lists: Node.js; A credential in GOOGLE_ACCESS_TOKEN. Its frontmatter pre-approves these tools: Bash, Read, Write, WebFetch, ToolSearch, mcp__claude-in-chrome__*.

Does Gdoc To Markdown access the network?

SKILL.md names 4 domains. In commands or code: docs.google.com, googleapis.com and sheets.googleapis.com; the agent is likely to contact these when it follows the instructions. As links in the text: developers.google.com. This is read from the text; nothing was executed.

Is Gdoc To Markdown safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Gdoc To Markdown use?

Gdoc To Markdown is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Gdoc To Markdown use?

About 3.8k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Gdoc To Markdown?

Skills that share tags, products or a category with Gdoc To Markdown: Managing Google Workspace (taylorwilsdon/google_workspace_mcp, 3.3k stars), Google Workspace (espennilsen/pi, 122 stars), Recipe Generate Report From Sheet (googleworkspace/cli, 31k stars) and Teach (ccplugins/awesome-claude-code-plugins, 970 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Gdoc To Markdown?

iurykrieger (a GitHub user) maintains it in iurykrieger/claude-bedrock, which has 105 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on May 5, 2026.

Source: iurykrieger/claude-bedrock on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.