القائمة
Use when converting local document files such as PDFs, Office documents, HTML, text, or other MarkItDown-supported inputs into Markdown.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | markitdown-cli |
| description | Use when converting local document files such as PDFs, Office documents, HTML, text, or other MarkItDown-supported inputs into Markdown. |
Use the installed markitdown command to convert readable local files into Markdown. Preserve source files and prefer the CLI over custom extraction code unless the user rejects it or a conversion fails for a clear reason.
Use for single-file or batch conversion, conversion checks or retries, stdin, and extensionless inputs. Do not use for summarizing without conversion, editing existing Markdown, dependency management, or standalone OCR/cloud extraction.
command -v markitdown. If missing, report it, do not install without approval, and point to https://github.com/microsoft/markitdown#installation..md files unless replacement is explicit.markitdown invocation per input so failures are attributable. Quote paths and avoid unsafe glob assumptions.--extension or --mime-type for stdin, extensionless files, or misleading filenames.| Need | Pattern |
|---|---|
| Save converted output | markitdown input.docx -o output.md |
| Stream to stdout | markitdown input.pdf |
| Extensionless input | markitdown --extension pdf input -o output.md |
| Stdin type hint | markitdown --mime-type text/html -o output.md < input.html |
| Text encoding | markitdown input.txt --charset utf-8 -o output.md |
Use --use-docintel or --use-content-understanding only for MarkItDown Markdown conversion when the user explicitly asks for that route and the required endpoint is configured.
Use when a maintainer explicitly asks for Knowledge Workflow setup, checks, upgrade migration, manifest work, or approved configuration updates.
Use when the user asks to implement an approved Kanban task or linked project change with clear acceptance criteria.
Use when delivery work needs a proposal before editing task candidates, Kanban cards, backlog shape, or board changes.
Use when delivery work needs review, a PR or local diff needs validation, or Done readiness is in question.
Use when a user asks how to use Knowledge Workflow in a repository, where content belongs, which skill applies, what project rules mean, how to recover safely, or how to record local workflow feedback.
Use when the user has approved a specific shared-knowledge write, promotion, reorganization, or update.