ReddRadar
Agent skill
dotnet-managedcode-markitdown
Use ManagedCode.MarkItDown when a .NET application needs deterministic document-to-Markdown conversion for ingestion, indexing, summarization, or content-processing workflows.
Install this agent skill to your Project
npx add-skill https://github.com/managedcode/dotnet-skills/tree/main/catalog/Libraries/ManagedCode-MarkItDown/skills/dotnet-managedcode-markitdown
SKILL.md
ManagedCode.MarkItDown
Trigger On
- integrating
ManagedCode.MarkItDowninto 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
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
managedcode/dotnet-skills
dotnet-project-setup
Create or reorganize .NET solutions with clean project boundaries, repeatable SDK settings, and a maintainable baseline for libraries, apps, tests, CI, and local development.
managedcode/dotnet-skills
csharp-scripts
Run single-file C# programs as scripts (file-based apps) for quick experimentation, prototyping, and concept testing. Use when the user wants to write and execute a small C# program without creating a full project.
managedcode/dotnet-skills
dotnet-pinvoke
Correctly call native (C/C++) libraries from .NET using P/Invoke and LibraryImport. Covers function signatures, string marshalling, memory lifetime, SafeHandle, and cross-platform patterns. USE FOR: writing new P/Invoke or LibraryImport declarations, reviewing or debugging existing native interop code, wrapping a C or C++ library for use in .NET, diagnosing crashes, memory leaks, or corruption at the managed/native boundary. DO NOT USE FOR: COM interop, C++/CLI mixed-mode assemblies, or pure managed code with no native dependencies.
managedcode/dotnet-skills
nuget-trusted-publishing
Set up NuGet trusted publishing (OIDC) on a GitHub Actions repo — replaces long-lived API keys with short-lived tokens. USE FOR: trusted publishing, NuGet OIDC, keyless NuGet publish, migrate from NuGet API key, NuGet/login, secure NuGet publishing. DO NOT USE FOR: publishing to private feeds or Azure Artifacts (OIDC is nuget.org only). INVOKES: shell (powershell or bash), edit, create, ask_user for guided repo setup.
managedcode/dotnet-skills
dotnet-legacy-aspnet
Maintain classic ASP.NET applications on .NET Framework, including Web Forms, older MVC, and legacy hosting patterns, while planning realistic modernization boundaries.
managedcode/dotnet-skills
dotnet-code-review
Review .NET changes for bugs, regressions, architectural drift, missing tests, incorrect async or disposal behavior, and platform-specific pitfalls before you approve or merge them.
Didn't find tool you were looking for?