メニュー
This skill should be used when the user asks to "convert a document to markdown", "extract text from PDF", "convert Word/PowerPoint/Excel to markdown", or needs to transform documents into markdown format.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | convert-to-markdown |
| description | This skill should be used when the user asks to "convert a document to markdown", "extract text from PDF", "convert Word/PowerPoint/Excel to markdown", or needs to transform documents into markdown format. |
| version | 0.1.0 |
Convert various document formats to Markdown using markitdown and pandoc.
| Format | Extension | Notes |
|---|---|---|
| Text + OCR hybrid mode available | ||
| Word | .docx | Full support |
| PowerPoint | .pptx | Extracts text from slides |
| Excel | .xlsx | Converts tables |
| HTML | .html, .htm | Full support |
| EPUB | .epub | Via pandoc |
| Images | .jpg, .png, .gif, .webp | OCR extraction |
| Google Docs | URL | Public docs, exports as docx |
uvx --with markitdown python ~/.claude/skills/convert-to-markdown/scripts/convert.py INPUT
| Flag | Description |
|---|---|
-o, --output PATH | Output path (default: input.md next to original) |
--mode auto|ocr|text | Extraction mode (default: auto) |
--hybrid | PDF only: run both text + OCR, merge results |
# Basic conversion (saves as document.md)
uvx --with markitdown python ~/.claude/skills/convert-to-markdown/scripts/convert.py document.pdf
# Force OCR mode for scanned document
uvx --with markitdown python ~/.claude/skills/convert-to-markdown/scripts/convert.py scanned.pdf --mode ocr
# Hybrid extraction for PDFs with mixed content
uvx --with markitdown python ~/.claude/skills/convert-to-markdown/scripts/convert.py report.pdf --hybrid
# Convert Word document
uvx --with markitdown python ~/.claude/skills/convert-to-markdown/scripts/convert.py report.docx
# Convert public Google Doc
uvx --with markitdown python ~/.claude/skills/convert-to-markdown/scripts/convert.py "https://docs.google.com/document/d/DOCUMENT_ID/edit"
# Specify output location
uvx --with markitdown python ~/.claude/skills/convert-to-markdown/scripts/convert.py slides.pptx -o notes.md
For Google Docs conversion:
https://docs.google.com/document/d/DOC_ID/editfilename.md next to the original file-o to specify a different locationbrew install pandoc # macOS
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.