managedcode-markitdown

Name: managedcode-markitdown
Author: managedcode

461stars35forks

How to install managedcode-markitdown?

managedcode/dotnet-skills/managedcode-markitdown

$npx -y skills add managedcode/dotnet-skills --skill managedcode-markitdown

Installs into the current project.

Summary

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

Files · 1

View on GitHub

SKILL.md

1	# ManagedCode.MarkItDown
2
3	## Trigger On
4
5	- integrating `ManagedCode.MarkItDown` into document ingestion flows
6	- converting office or rich-text content into Markdown for downstream processing
7	- reviewing indexing, chunking, or AI-preparation pipelines that depend on Markdown output
8	- documenting file-conversion steps for a .NET application
9
10	## Workflow
11
12	1. Identify the document sources the app actually handles.
13	2. Decide where Markdown conversion belongs in the pipeline:
14	- before indexing
15	- before chunking
16	- before AI summarization or enrichment
17	3. Keep conversion isolated behind one ingestion or processing service instead of scattering format handling everywhere.
18	4. Validate real converted output for structure, links, headings, and attachment handling.
19	5. Document which downstream stage depends on the produced Markdown.
20
21	```mermaid
22	flowchart LR
23	A["Input document"] --> B["ManagedCode.MarkItDown conversion"]
24	B --> C["Markdown output"]
25	C --> D["Indexing, chunking, or AI workflow"]
26	```
27
28	## Deliver
29
30	- guidance on where ManagedCode.MarkItDown fits in a real processing pipeline
31	- conversion-boundary recommendations for application design
32	- output-validation expectations for document ingestion
33
34	## Validate
35
36	- the converted Markdown is good enough for the actual downstream consumer
37	- conversion is isolated in one clear pipeline step
38	- tests or review samples cover the real input formats the application claims to support

People who liked this also viewed

6 picks

Type