Codex .NET MarkItDown for Document Conversion Validation
Place ManagedCode.MarkItDown in a clear ingestion step and verify the converted headings, links, and attachments against downstream needs.
中文Install in Codex
Codex with a .NET project evaluating ManagedCode.MarkItDown and non-sensitive sample documents.
- Copy the entire pinned `.codex/skills/dotnet-managedcode-markitdown/` directory to `.agents/skills/dotnet-managedcode-markitdown/` in the target checkout.
- Open Codex in that checkout and invoke `$dotnet-managedcode-markitdown` with the example task and desired output.
Example task
Invoke `$dotnet-managedcode-markitdown` for local help documents in a practice project. Compare a heading and link in a sample conversion.What to check
Conversion has one clear boundary. The Markdown can be compared with its fixture and downstream indexing can rely on the documented structure.
Original SKILL.md on GitHub · Updated
Frequently asked question
Where should conversion happen?
Decide according to the consumer. Put a focused conversion step before indexing or chunking when it needs Markdown.