managedcode-markitdown
ManagedCode.MarkItDown is a .NET library that converts Office documents and rich-text formats into Markdown for deterministic processing. Use it when building document ingestion pipelines that require reliable Markdown output for indexing, chunking, summarization, or AI enrichment workflows. The skill guides placement of conversion logic within the pipeline, validates output structure against downstream requirements, and ensures conversion boundaries are cleanly isolated rather than scattered throughout the application.
git clone --depth 1 https://github.com/managedcode/dotnet-skills /tmp/managedcode-markitdown && cp -r /tmp/managedcode-markitdown/catalog/Libraries/ManagedCode-MarkItDown/skills/managedcode-markitdown ~/.claude/skills/managedcode-markitdownSKILL.md
# 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 1. Identify the document sources the app actually handles. 2. Decide where Markdown conversion belongs in the pipeline: - before indexing - before chunking - before AI summarization or enrichment 3. Keep conversion isolated behind one ingestion or processing service instead of scattering format handling everywhere. 4. Validate real converted output for structure, links, headings, and attachment handling. 5. Document which downstream stage depends on the produced Markdown. ```mermaid 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
Build, debug, modernize, or review ASP.NET Core applications with correct hosting, middleware, security, configuration, logging, and deployment patterns on current .NET. USE FOR: working on ASP.NET Core apps, services, or middleware; changing auth, routing, configuration, hosting, or deployment behavior; deciding between ASP.NET Core sub-stacks. 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 build, test, lint, or validation commands when changes are made.
Build, upgrade, and operate .NET Aspire 13.3.x application hosts with current CLI, AppHost, ServiceDefaults, integrations, dashboard, testing, and Azure deployment patterns for distributed apps. USE FOR: Aspire.AppHost.Sdk, Aspire.Hosting.*, DistributedApplication.CreateBuilder, WithReference, WaitFor, AddProject, AddRedis, AddPostgres, aspire run, aspire init, aspire. 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 build, test, lint, or validation commands when changes are made.
Build, review, or migrate Azure Functions in .NET with correct execution model, isolated worker setup, bindings, DI, and Durable Functions patterns. USE FOR: working on Azure Functions in .NET; migrating from the in-process model to the isolated worker model; adding Durable Functions, bindings, or host configuration. 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 build, test, lint, or validation commands when changes are made.
Build and review Blazor applications across server, WebAssembly, web app, and hybrid scenarios with correct component design, state flow, rendering, and hosting choices. USE FOR: building interactive web UIs with C# instead of JavaScript; choosing between Server, WebAssembly, or Auto render modes; designing component hierarchies and state. 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 build, test, lint, or validation commands when changes are made.
Maintain or migrate EF6-based applications with realistic guidance on what to keep, what to modernize, and when EF Core is or is not the right next step. USE FOR: EF6 codebases; runtime versus ORM migration decisions; EDMX, code-first, ObjectContext, and legacy data-access review. 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 build, test, lint, or validation commands when changes are made.
Design, tune, or review EF Core data access with proper modeling, migrations, query translation, performance, and lifetime management for modern .NET applications. USE FOR: DbContext, migrations, model configuration, EF queries, tracking, loading, performance, transactions, and EF6 migration decisions. 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 build, test, lint, or validation commands when changes are made.
Build, review, or migrate .NET MAUI applications across Android, iOS, macOS, and Windows with correct cross-platform UI, platform integration, and native packaging assumptions. USE FOR: working on cross-platform mobile or desktop UI in .NET MAUI; integrating device capabilities, navigation, or platform-specific code; migrating Xamarin.Forms or aligning. 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 build, test, lint, or validation commands when changes are made.
Use ML.NET to train, evaluate, or integrate machine-learning models into .NET applications with realistic data preparation, inference, and deployment expectations. USE FOR: ML.NET integration; local model training or retraining; inference pipelines, model loading, evaluation, and deployment review. 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 build, test, lint, or validation commands when changes are made.