markitdown
Convert documents to Markdown using MarkItDown MCP tools. Use when the user wants to convert PDF, read PPTX, extract text from DOCX, convert document to markdown, or mentions .pdf/.docx/.pptx/.xlsx/.xls/.ppt/.doc files for reading or conversion. Triggers on phrases like "convert to markdown", "read this document", "extract text from", "parse this file" with binary document formats.
What this skill does
# MarkItDown - Document to Markdown Conversion Use `mcp__markitdown__convert_to_markdown` whenever the user needs to read or extract text from binary document formats that Claude's native Read tool cannot parse. ## What MarkItDown Does MarkItDown converts binary and structured document formats into clean, readable Markdown text. It preserves document structure including headings, tables, lists, and other formatting elements. **Supported formats:** - **Office documents**: DOCX, PPTX, XLSX, DOC, PPT, XLS - **PDF**: PDF files (though Claude's Read tool also handles PDFs natively) - **Images**: PNG, JPG, JPEG, GIF, BMP, TIFF (extracts text via OCR when available) - **Web formats**: HTML, HTM - **Data formats**: CSV, JSON, XML - **Archives**: ZIP (extracts and converts contents) - **Audio**: MP3, WAV (transcribes audio when possible) - **eBooks**: EPUB ## When to Use MarkItDown Use the markitdown MCP tool when: 1. **The file is a binary Office format**: `.docx`, `.pptx`, `.xlsx`, `.doc`, `.ppt`, `.xls` — Claude's Read tool returns garbled binary data for these formats. MarkItDown is the only reliable way to extract their text content. 2. **The user wants structured extraction**: When the user needs to preserve table structure, slide content, spreadsheet data, or document formatting in a machine-readable form. 3. **Processing multiple documents in a ZIP**: When a ZIP archive contains documents that need to be converted together. 4. **The user explicitly asks to "convert to markdown"**: Regardless of file type, honor this intent by using MarkItDown. ## When NOT to Use MarkItDown Do NOT use MarkItDown for: - **Plain text files** (`.txt`, `.md`, `.csv`, `.json`, `.xml`, `.html`): Use Claude's native Read tool — it handles these perfectly and is faster. - **Source code files** (`.py`, `.js`, `.ts`, `.java`, etc.): Use the Read tool directly. - **PDF files**: For PDF extraction, prefer **EdgeParse** (`edgeparse` plugin) — it is faster, preserves document structure (headings, tables, bounding boxes), and supports page ranges and borderless tables. Only fall back to MarkItDown for PDFs when EdgeParse is not installed. - **Images when the user wants visual analysis**: Use Claude's native image understanding instead of OCR-only text extraction. ## How to Use ### Basic document conversion Call `mcp__markitdown__convert_to_markdown` with a `file://` URI: ``` mcp__markitdown__convert_to_markdown(uri="file:///absolute/path/to/document.docx") ``` The tool accepts `http:`, `https:`, `file:`, or `data:` URIs. For local files, always use the `file://` scheme with an absolute path (`file:///path/to/file`). The tool returns the document content as a Markdown string. Use this output directly to answer the user's question or to further process the content. ### Workflow for binary documents When the user asks to read, summarize, or analyze a `.docx`, `.pptx`, or `.xlsx` file: 1. Construct a `file://` URI from the absolute path (e.g. `file:///home/user/report.docx`) 2. Call `mcp__markitdown__convert_to_markdown` with the `uri` argument 3. Read the returned Markdown content 4. Answer the user's question based on the extracted content Do not attempt to use the Read tool on these binary formats first — it will return unreadable binary data and waste time. ### Handling PPTX (PowerPoint) files PowerPoint files convert to Markdown with each slide's content. Slide titles become headings, bullet points become list items, and tables are preserved. Speaker notes may also be included. ### Handling XLSX (Excel) files Excel spreadsheets convert with each sheet's data rendered as Markdown tables. Multiple sheets are separated with sheet name headings. ### Handling DOCX (Word) files Word documents convert with full structure: headings, paragraphs, tables, and lists are all preserved in Markdown format. ## Important Notes - **Always use `file://` URIs with absolute paths**: Construct the URI as `file:///absolute/path/to/file`. Relative paths are not supported — resolve to absolute first if needed. - **The MCP server uses `uvx markitdown-mcp`**: It requires `uv` to be installed on the system. If the tool fails, check that `uv` is available. - **Large files**: Very large documents (hundreds of pages) may take longer to convert. This is expected behavior. - **Password-protected files**: MarkItDown cannot open password-protected Office documents or encrypted PDFs without the password.
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".