ReddRadar
Agent skill
dotnet-managedcode-mimetypes
Use ManagedCode.MimeTypes when a .NET application needs consistent MIME type detection, extension mapping, and content-type decisions for uploads, downloads, or HTTP responses.
Install this agent skill to your Project
npx add-skill https://github.com/managedcode/dotnet-skills/tree/main/catalog/Libraries/ManagedCode-MimeTypes/skills/dotnet-managedcode-mimetypes
SKILL.md
ManagedCode.MimeTypes
Trigger On
- integrating
ManagedCode.MimeTypesinto upload or download flows - mapping file extensions to content types in APIs or background processing
- reviewing content-type handling for files, blobs, or attachments
- documenting a reusable MIME-type decision point in a .NET application
Workflow
- Identify where the application needs stable MIME-type decisions:
- upload validation
- download response headers
- storage metadata
- attachment processing
- Centralize content-type mapping instead of scattering ad-hoc string tables across the codebase.
- Use one library boundary for extension and MIME lookups.
- Validate the extensions and media types that matter to the product.
- Document any product-specific overrides separately from the library defaults.
flowchart LR
A["File name or extension"] --> B["ManagedCode.MimeTypes lookup"]
B --> C["Resolved MIME type"]
C --> D["Upload validation, storage metadata, or HTTP response"]
Deliver
- guidance on where MIME lookup belongs in application code
- recommendations for centralized content-type decisions
- validation expectations for real file types used by the product
Validate
- MIME mapping is not duplicated across multiple services or controllers
- important file types are verified explicitly
- response or storage code uses the resolved type consistently
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?