Skill

import-gdoc

Import Google Docs from Drive into local google-in/ folder with manifest tracking. Use when importing Google documents for local analysis. Triggers include "import gdoc", "google doc", "import from drive", "google docs import".

Install

npx claudepluginhub digital-stoic-org/agent-skills --plugin dstoic

Tool Access

This skill is limited to using the following tools:

mcp__google-docs__search_docsmcp__google-docs__get_doc_contentmcp__google-docs__list_docs_in_foldermcp__google-docs__search_drive_filesReadWriteBashAskUserQuestion

Preview

Import Google Docs from Drive into `google-in/` with manifest tracking.

Supporting Assets

reference.md

SKILL.md

Similar Skills

using-git-worktrees

Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.

superpowers

169.2k

subagent-driven-development

3 files

Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.

superpowers

169.2k

dispatching-parallel-agents

Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.

superpowers

169.2k

Stats

Parent Repo Stars5

Parent Repo Forks2

Last CommitMar 3, 2026

Actions

View Source View Plugin View on GitHub View README

Google Docs Import

Import Google Docs from Drive into google-in/ with manifest tracking.

⚠️ AskUserQuestion Guard

CRITICAL: After EVERY AskUserQuestion call, check if answers are empty/blank. Known Claude Code bug: outside Plan Mode, AskUserQuestion silently returns empty answers without showing UI.

If answers are empty: DO NOT proceed with assumptions. Instead:

Output: "⚠️ Questions didn't display (known Claude Code bug outside Plan Mode)."

Present the options as a numbered text list and ask user to reply with their choice number.

WAIT for user reply before continuing.

Steps

Get user email (required for MCP auth): AskUserQuestion

Determine search: $ARGUMENTS as query, or interactive if empty

Search docs: Use MCP tools, present numbered results, let user select

Setup: mkdir -p google-in

Import each doc:

Fetch via mcp__google-docs__get_doc_content
Sanitize filename (lowercase, hyphens, max 100 chars, .md)
Handle duplicates (same ID → update, different ID → suffix)
Write to google-in/<name>.md

Update manifest: google-in/README.md with table (Name, Last Import, Drive Link, File ID)

Report: file count, paths, suggest re-run for updates

See reference.md for manifest format, duplicate handling, error handling, and edge cases.