Use ManagedCode.MarkItDown when a .NET application needs deterministic document-to-Markdown conversion for ingestion, indexing, summarization, or content-processing workflows. USE FOR: ManagedCode.MarkItDown integration; document ingestion flows; Office or rich-text conversion to Markdown; indexing and summarization pipelines. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant bui
SkillScore86Maintained
Automatic
◆AI Engineer pack
Last verified 8/19/2026
What it changes
Passed 19 of 22 test cases with the skill, and 16 of 22 without it.
Without skill73%
With skill86%
Checks it passed that the model alone missed
Import the `ManagedCode.MarkItDown` namespace
Use ManagedCode.MarkItDown for native document-to-Markdown conversion in .NET
Throw a `NotSupportedException` when encountering an unsupported file extension
3 fixed16 passed either way3 still failing0 broke
Pass-rate lift
+14 pp
Tokens
-11%
Agent turns
0%
Response time
-31%
Model gemini-3.6-flashMeasured 8/19/2026v119 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 3
Prompt
What namespace must be imported in C# source files to access the `MarkItDown` and `IMarkItDown` types?
What was checked, without and with the skill
Checked
Without skill
With skill
Import the `ManagedCode.MarkItDown` namespace
Missed
Passed
case-19 · gemini-3.6-flash · 8/19/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md38 linessingle file
ManagedCode.MarkItDown
Trigger On
integrating ManagedCode.MarkItDown into document ingestion flows
converting office or rich-text content into Markdown for downstream processing
reviewing indexing, chunking, or AI-preparation pipelines that depend on Markdown output
documenting file-conversion steps for a .NET application
Workflow
Identify the document sources the app actually handles.
Decide where Markdown conversion belongs in the pipeline:
before indexing
before chunking
before AI summarization or enrichment
Keep conversion isolated behind one ingestion or processing service instead of scattering format handling everywhere.
Validate real converted output for structure, links, headings, and attachment handling.
Document which downstream stage depends on the produced Markdown.
flowchart LR
A["Input document"] --> B["ManagedCode.MarkItDown conversion"]
B --> C["Markdown output"]
C --> D["Indexing, chunking, or AI workflow"]
Deliver
guidance on where ManagedCode.MarkItDown fits in a real processing pipeline
conversion-boundary recommendations for application design
output-validation expectations for document ingestion
Validate
the converted Markdown is good enough for the actual downstream consumer
conversion is isolated in one clear pipeline step
tests or review samples cover the real input formats the application claims to support
Use ManagedCode.Orleans.SignalR when a distributed .NET application needs Orleans-based coordination of SignalR real-time messaging, hub delivery, and grain-driven push flows. USE FOR: integrating ManagedCode.Orleans.SignalR into a real-time distributed application; coordinating SignalR delivery from Orleans grains; reviewing grain-to-hub push flows. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted fil