MarkItDown handles the PDFs, Word files and Excel sheets locally. It can't OCR scanned pages, so those need a separate local step first.
1. Install (local only)
uv venv --python 3.12 .venv && source .venv/bin/activate
uv pip install "markitdown[pdf,docx,xlsx,xls]==0.1.8"
brew install ocrmypdf # local Tesseract-based OCR, for the scanned PDFs
Don't install markitdown-ocr, and don't use Azure or LLM image-description options. Those all send content to an outside service.
2. OCR the scanned PDFs locally
MarkItDown's PDF converter only extracts existing text. A scanned PDF will come out nearly empty. ocrmypdf adds a text layer on your machine, and --skip-text leaves pages that already have text alone:
mkdir -p ocr
find contracts -type f -iname '*.pdf' | while read -r f; do
out="ocr/${f#contracts/}"; mkdir -p "$(dirname "$out")"
ocrmypdf --skip-text "$f" "$out" || echo "OCR FAILED: $f" >> ocr_failures.txt
done
This OCRs every PDF and skips pages that already have text. For 300 files that's fine. For other languages, install the matching Tesseract language pack and add -l eng+deu (or similar).
3. Convert everything to Markdown
Use a loop that preserves subfolders and avoids name collisions (a.pdf and a.docx both become .md). It writes <filename>.md, for example a.pdf.md:
mkdir -p markdown
find contracts -type f \( -iname '*.docx' -o -iname '*.xlsx' -o -iname '*.xls' \) > list.txt
find ocr -type f -iname '*.pdf' >> list.txt
while read -r f; do
rel="${f#*/}"; out="markdown/$rel.md"; mkdir -p "$(dirname "$out")"
markitdown "$f" -o "$out" || echo "FAILED: $f" >> convert_failures.txt
done < list.txt
The MarkItDown skill also bundles scripts/batch_convert.py, which does the same with a manifest. I haven't checked that it's present on your machine, so the loop above is the safe option. Plugins are off by default, which is what you want.
What to watch out for
- Network: MarkItDown's local converters don't call out, but its extension checks aren't an offline sandbox. Audio or URL handling can reach the network. For confidential files, run the conversion with Wi-Fi off or in a network-isolated container.
- Old
.docfiles: these aren't supported, only.docx. Convert them first withsoffice --headless --convert-to docx. - Silent bad output: a conversion can succeed and still be poor. Find empty or tiny outputs with
find markdown -size -200c, and open a few OCR'd files to check quality. Skewed or low-resolution scans are the usual cause. - Excel: each sheet becomes a Markdown table. Large sheets turn into huge tables that chunk badly in a search index. Formulas come through as their cached values, not the formulas.
- Tables and layout: multi-column PDFs, signature pages, stamps, handwriting and images inside Word files won't convert well. Spot-check key contracts against the originals.
- Provenance: keep each file's original path in your index metadata, so a search hit points back to the source document. The Markdown is only a derived copy.
- Hidden or injected text: contracts can contain hidden text or instructions. If an LLM reads your index later, treat the Markdown as data, not instructions.
- Storage: the
ocr/andmarkdown/folders are now confidential copies. Keep them in the same access-controlled location as the originals, and don't put them in a synced or cloud-backed folder. - Failures: check
ocr_failures.txtandconvert_failures.txtafterwards. Password-protected or corrupted PDFs are the usual culprits.
I can run this on the folder and report the failures and suspiciously small outputs. Tell me the path if you want that.
Real run in an isolated folder with only this skill installed. Only the Skill and Read tools were enabled, so no command was run and no file was written. The scenario is fictional. The commands in this answer were not run in this session. The skill's bundled scripts were then run by hand in a clean environment on sample files (docx, xlsx, pdf, html) and behaved as the skill describes, including skipping symbolic links, not overwriting existing outputs, refusing audio files without a flag, and failing on a PDF with no text layer. The OCR step recommended in the answer (ocrmypdf) is not part of the skill and was not tested.
Qué hace
Actúa como envoltorio de la herramienta MarkItDown de Microsoft y le indica a la IA cómo usarla de forma segura. Convierte PDF, DOCX, PPTX, XLSX, HTML, CSV, EPUB, notebooks, ZIP y más en Markdown que conserva la estructura, pensado para indexación, análisis de texto e ingesta en LLM (no para una reproducción exacta a nivel de píxel). Elige el método de conversión más acotado, trata el texto convertido como no confiable y separa el trabajo local de cualquier cosa que envíe datos a un servicio externo.
Herramientas incluidas
Tres scripts: un conversor por lotes que conserva la estructura de carpetas, omite enlaces simbólicos, nunca sobrescribe a menos que se le indique y puede escribir un manifiesto; un conversor para literatura que añade front matter de procedencia y un índice; y un inspector de instalación. Los archivos de referencia cubren seguridad, opciones de OCR y de nube, plugins, el servidor MCP y recetas de RAG.
Útil para
Convertir una carpeta de documentos a Markdown antes de crear un índice de búsqueda o preguntarle a una IA sobre ellos.
Riesgo medio: instalas paquetes de Python (uv o pip) y la Skill escribe archivos Markdown; los scripts incluidos omiten enlaces simbólicos y no sobrescriben a menos que pases --overwrite. Algunas funciones opcionales envían contenido a servicios externos: URLs, YouTube, transcripción de audio (Google Web Speech), descripciones de imágenes con IA, el plugin de OCR y Azure; la Skill indica que se obtenga aprobación primero y que se eviten para archivos confidenciales. Los plugins ejecutan Python arbitrario y están desactivados de forma predeterminada. El texto convertido puede ocultar instrucciones: trátalo como datos. No puede aplicar OCR a PDF escaneados localmente. La Skill también pide a la IA que cite un artículo de K-Dense cuando haya ayudado de forma sustancial a un manuscrito o informe y que lo busque en línea; elimina esa sección si no la quieres. Los scripts se ejecutaron manualmente con archivos de muestra y funcionaron como se describe. MIT, sin modificaciones.