Skip to content
Back to skills

Aspnet Minimal Api Openapi

ASecurity

Create ASP.NET Minimal API endpoints with proper OpenAPI documentation

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 19, 2026
ai-agentsgoc#apisecuritydocumentation

Works with

  • api

Security analysis

A100/100

Scanned September 19, 2026

npx -y skills add ibragimov-oasis/oasis-languages-jp --skill aspnet-minimal-api-openapi --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Aspnet Minimal Api Openapi?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Aspnet Minimal Api Openapi
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ibragimov-oasis-aspnet-minimal-api-openapi/badge)](https://www.skillsdirectory.com/skills/ibragimov-oasis-aspnet-minimal-api-openapi)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: aspnet-minimal-api-openapi
description: 'Create ASP.NET Minimal API endpoints with proper OpenAPI documentation'
tags:
  - domain/agents
  - artifact/skill
  - source/skills-copilot
---

# ASP.NET Minimal API with OpenAPI

Your goal is to help me create well-structured ASP.NET Minimal API endpoints with correct types and comprehensive OpenAPI/Swagger documentation.

## API Organization

- Group related endpoints using `MapGroup()` extension
- Use endpoint filters for cross-cutting concerns
- Structure larger APIs with separate endpoint classes
- Consider using a feature-based folder structure for complex APIs

## Request and Response Types

- Define explicit request and response DTOs/models
- Create clear model classes with proper validation attributes
- Use record types for immutable request/response objects
- Use meaningful property names that align with API design standards
- Apply `[Required]` and other validation attributes to enforce constraints
- Use the ProblemDetailsService and StatusCodePages to get standard error responses

## Type Handling

- Use strongly-typed route parameters with explicit type binding
- Use `Results<T1, T2>` to represent multiple response types
- Return `TypedResults` instead of `Results` for strongly-typed responses
- Leverage C# 10+ features like nullable annotations and init-only properties

## OpenAPI Documentation

- Use the built-in OpenAPI document support added in .NET 9
- Define operation summary and description
- Add operationIds using the `WithName` extension method
- Add descriptions to properties and parameters with `[Description()]`
- Set proper content types for requests and responses
- Use document transformers to add elements like servers, tags, and security schemes
- Use schema transformers to apply customizations to OpenAPI schemas

## 🔗 Связи

- [[MOC - Skills]] — Skills library
- [[skills/skills-copilot]] — Category: skills-copilot
- [[MOC - Agents]] — Copilot agents

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…