메뉴
This skill should be used when the user asks to "convert a Google Doc to markdown", "download Google Sheets as markdown", "create a Google Doc from markdown", or needs to convert between Google Workspace files and Markdown format.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | google-workspace-convert |
| description | This skill should be used when the user asks to "convert a Google Doc to markdown", "download Google Sheets as markdown", "create a Google Doc from markdown", or needs to convert between Google Workspace files and Markdown format. |
| version | 0.1.0 |
Convert Google Workspace files (Docs, Sheets, Slides) to Markdown and vice versa.
Uses Google Drive API with service account authentication.
| Format | To Markdown | From Markdown |
|---|---|---|
| Google Docs | Yes | Yes |
| Google Sheets | Yes | No |
| Google Slides | Yes | No |
| Google Drawings | Yes | No |
| Uploaded files (PDF, DOCX, etc.) | Yes | - |
Environment variables (can be in .env file):
GOOGLE_APPLICATION_CREDENTIALS - Path to service account JSONGOOGLE_CLOUD_PROJECT - GCP project IDService account needs:
info command to get email)uvx --with markitdown --with google-auth --with google-api-python-client --with python-dotenv \
python ~/.claude/skills/google-workspace-convert/scripts/convert.py \
to-markdown "GOOGLE_DRIVE_URL_OR_ID"
Options:
-o, --output PATH - Output path (default: current dir)--ocr - Enable OCR for image contentuvx --with markitdown --with google-auth --with google-api-python-client --with python-dotenv \
python ~/.claude/skills/google-workspace-convert/scripts/convert.py \
to-gdoc notes.md
Options:
-n, --name NAME - Name for the Google Doc (default: filename)-f, --folder ID - Google Drive folder ID to upload touvx --with markitdown --with google-auth --with google-api-python-client --with python-dotenv \
python ~/.claude/skills/google-workspace-convert/scripts/convert.py \
list
uvx --with markitdown --with google-auth --with google-api-python-client --with python-dotenv \
python ~/.claude/skills/google-workspace-convert/scripts/convert.py \
info
# Convert Google Doc to Markdown
uvx --with markitdown --with google-auth --with google-api-python-client --with python-dotenv \
python ~/.claude/skills/google-workspace-convert/scripts/convert.py \
to-markdown "https://docs.google.com/document/d/1ABC123/edit"
# Convert with OCR for embedded images
uvx --with markitdown --with google-auth --with google-api-python-client --with python-dotenv \
python ~/.claude/skills/google-workspace-convert/scripts/convert.py \
to-markdown "https://docs.google.com/document/d/1ABC123/edit" --ocr
# Create Google Doc from Markdown
uvx --with markitdown --with google-auth --with google-api-python-client --with python-dotenv \
python ~/.claude/skills/google-workspace-convert/scripts/convert.py \
to-gdoc ./meeting-notes.md --name "Meeting Notes 2024"
# Upload to specific folder
uvx --with markitdown --with google-auth --with google-api-python-client --with python-dotenv \
python ~/.claude/skills/google-workspace-convert/scripts/convert.py \
to-gdoc ./report.md --folder "https://drive.google.com/drive/folders/1XYZ789"
info command to get the service account emailfilename.md in current directory (or specified path)Produce single-file, self-contained HTML artifacts instead of Markdown for any output a human will actually read. Use whenever the user asks for a "report", "research summary", "write-up", "spec", "plan", "PR explainer", "code review", "design mockup", "prototype", "dashboard", "deck", or anything that benefits from tables, SVG diagrams, color coding, side-by-side comparisons, sliders, drag-and-drop, or shareable visuals. Also use when the user wants to share something visual with a teammate, when a Markdown plan would exceed ~100 lines, when interactive tweaking would help (sliders, copy-as-JSON, copy-as-prompt buttons), or when the model is about to resort to ASCII-art charts or Unicode color blocks in Markdown. Strongly prefer this skill for any "summarize and present" task — even if the user doesn't explicitly say "HTML".
Use this skill whenever the user asks to look at GitHub PR feedback, PR review comments, review bot output, Gemini/Claude review feedback, or pasted reviewer suggestions and wants a markdown table that separates what should be fixed from what does not need to be fixed. This skill should trigger for PR feedback triage, deciding whether review comments are actionable, and producing a concise markdown report with yes/no emoji decisions and reasoning.
Use this skill whenever the user wants to interact with Google Cloud's Agent Registry using gcloud commands. Triggers on any mention of "agent registry", "agent-registry", "mcp-servers", "gcloud agents", "register an agent", "list agents", "create a service", "agent service", or any request to manage agents, MCP servers, endpoints, or services in Google Cloud Agent Registry. Also triggers on requests to integrate or use the Google Agent Development Kit (ADK) with the Agent Registry.
Follow Kent Beck's "Tidy First" approach by strictly separating structural changes (renames, extractions, reorganizations that must not change behavior) from behavioral changes (features, bug fixes, logic changes). Use when refactoring, restructuring code, renaming variables/functions, extracting methods, separating concerns, preparing code for new features, or whenever you need structural and behavioral changes to land in separate commits.
Read this skill before making git commits
Automates the end-to-end Git workflow: branch creation, staging, committing, pushing, and opening or updating a GitHub pull request. Use when a feature or fix is ready for review and requires a structured PR, or when branch changes may need to be pushed to an existing PR for follow-up review.