Source profileQuality 85/100

Benknightdark/neo-skills/skills/neo-dotnet-webapi/SKILL.md

neo-dotnet-webapi

Use this skill when building, debugging, refactoring, or reviewing controller-based ASP.NET Core Web APIs, including ControllerBase, ActionResult<T>, Problem Details, API versioning, global exception handling, DTOs, and OpenAPI behavior.

Source repository stars
7
Declared platforms
0
Static risk flags
0
Last source update
2026-08-05
Source checked
2026-08-05
DecisionCompatibilityInstallWorkflowPermissionsEvidenceSource

Decision brief

What it does—and where it fits

NET Core Web APIs, including ControllerBase, ActionResult<T>, Problem Details, API versioning, global exception handling, DTOs, and OpenAPI behavior.

Best for

  • Use this skill when building, debugging, refactoring, or reviewing controller-based ASP.

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/Benknightdark/neo-skills --skill "skills/neo-dotnet-webapi"
Safe inspection promptEditorial

Inspect the Agent Skill "neo-dotnet-webapi" from https://github.com/Benknightdark/neo-skills/blob/c3e3d1bcf6aae00a729ceab257e6a68dd40d89ec/skills/neo-dotnet-webapi/SKILL.md at commit c3e3d1bcf6aae00a729ceab257e6a68dd40d89ec. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    Workflow

    1. Perceive (Architecture Awareness): - Check .csproj to identify TargetFramework. - Analyze project structure to confirm whether it uses N-Tier architecture or Vertical Slice. - Identify existing cross-cutting concern handling methods (filters, middleware). 2. Reason (Planning…

    Perceive (Architecture Awareness):Check .csproj to identify TargetFramework.Analyze project structure to confirm whether it uses N-Tier architecture or Vertical Slice.
  2. 02

    Trigger On

    The user requests to create, debug, refactor, or review ASP.NET Core Web APIs.

    The user requests to create, debug, refactor, or review ASP.NET Core Web APIs.The project contains a Controllers directory and inherits from ControllerBase.The target framework is .NET 6.0 (LTS) and above.
  3. 03

    Feature Roadmap (.NET 6 - 10)

    Controllers Architecture: Traditional controller patterns and attribute routing.

    Controllers Architecture: Traditional controller patterns and attribute routing.Problem Details: Unified error response standards.Output Caching: High-performance server-side caching.
  4. 04

    .NET 6 & 7 (Foundation)

    Controllers Architecture: Traditional controller patterns and attribute routing.

    Controllers Architecture: Traditional controller patterns and attribute routing.Problem Details: Unified error response standards.Output Caching: High-performance server-side caching.

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score85/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars7SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
Benknightdark/neo-skills
Skill path
skills/neo-dotnet-webapi/SKILL.md
Commit
c3e3d1bcf6aae00a729ceab257e6a68dd40d89ec
License
MIT
Collected
2026-08-05
Default branch
main
View the original SKILL.md

.NET Web API Expert Skill

Trigger On

  • The user requests to create, debug, refactor, or review ASP.NET Core Web APIs.
  • The project contains a Controllers directory and inherits from ControllerBase.
  • The target framework is .NET 6.0 (LTS) and above.
  • There is a need for API code modernization (e.g., migrating from Middleware exception handling to .NET 8+ IExceptionHandler).

Workflow

  1. Perceive (Architecture Awareness):
    • Check .csproj to identify TargetFramework.
    • Analyze project structure to confirm whether it uses N-Tier architecture or Vertical Slice.
    • Identify existing cross-cutting concern handling methods (filters, middleware).
  2. Reason (Planning Phase):
    • Evaluate whether to introduce the "Problem Details" standard.
    • Determine whether to use the .NET 8+ global exception handling mechanism.
    • Choose an appropriate versioning strategy based on project scale.
  3. Act (Execution Phase):
    • Write high-quality controllers compliant with [ApiController] conventions.
    • Implement strongly-typed and immutable DTOs (prioritize record).
    • Integrate dependency injection, prioritizing Primary Constructors (C# 12+).
  4. Validate (Standard Validation):
    • Validate whether Action return types comply with ActionResult<T> specifications.
    • Check NRT (Nullable Reference Types) safety.
    • Ensure asynchronous operations correctly pass down CancellationToken.

Feature Roadmap (.NET 6 - 10)

.NET 6 & 7 (Foundation)

  • Controllers Architecture: Traditional controller patterns and attribute routing.
  • Problem Details: Unified error response standards.
  • Output Caching: High-performance server-side caching.
  • Nullable Reference Types: Comprehensive null safety support.

.NET 8 & 9 (Productivity)

  • IExceptionHandler: More elegant centralized exception handling.
  • Antiforgery: Built-in anti-forgery support for Web APIs.
  • Keyed Services: More flexible dependency injection options.
  • HybridCache: Multi-level caching optimization.

.NET 10+ (Version-Specific Features)

  • Extension Members for Controllers: Extending base controller functionality.
  • Enhanced Serialization: JSON optimization for large payloads.

Coding Standards

  • Strong Typing: Prioritize ActionResult<T> to improve Swagger support.
  • NRT Compliance: Strictly enforce Null safety to reduce runtime errors.
  • Async Best Practices: Always accept and pass CancellationToken.
  • Naming: Controller names must end with Controller, async methods must end with Async.

Deliver

  • Version-Optimized Web API Code: Provide modernized controllers and configurations suitable for the target version.
  • Architectural Insights: Provide refactoring suggestions for N-Tier or Clean Architecture.
  • Security Recommendations: Provide security suggestions regarding Problem Details and exception handling.

Validate

  • Ensure the code complies with C# 10+ modern syntax standards.
  • Validate endpoints correctly return error formats compliant with RFC 7807.
  • Confirm the code has no resource leaks in the tested environment (correct use of using and async).

Documentation

Official References

Internal References

Alternatives

Compare before choosing

Computed 976

mgiovani/cc-arsenal

team-review

Multi-agent review team: architecture, security, performance, testing, style, docs/UX, plus an adversary that cross-examines the other 6, for security-sensitive, architectural, or large PRs (15+ files) where a single-agent pass risks missing cross-cutting issues. Use for auth/payments/PII changes, schema/pattern changes, compliance sign-off, or when asked to 'get the review team on this' / 'multi-agent review' / 'thorough review before merge'. For a standard PR or a quick pre-merge check, use /r

2026-08-040 platforms
Computed 964,944

dotnet/skills

dotnet-webapi

Guides creation and modification of ASP.NET Core Web API endpoints with correct HTTP semantics, OpenAPI metadata, and error handling. USE FOR: adding new API endpoints (controllers or minimal APIs), wiring up OpenAPI/Swagger, creating .http test files, setting up global error handling middleware. DO NOT USE FOR: general C# coding style, EF Core data access or query optimization (use optimizing-ef-core-queries), frontend/Blazor work, gRPC services, or SignalR hubs.

2026-08-050 platforms
Computed 96107

AI-Unified-Process/marketplace

reverse-engineer

Reverse-engineers an existing software project into AI Unified Process artifacts: a PlantUML use case diagram, per-use-case specification documents, and an entity model with a Mermaid ER diagram. Use when the user asks to "reverse engineer this codebase", "extract use cases from existing code", "document the system we already have", "generate use case specs from controllers", "derive an entity model from the database", "create AIUP artifacts from a legacy project", or mentions reverse engineerin

2026-08-040 platforms
Computed 9510,879

Jeffallan/claude-skills

fastapi-expert

Use when building high-performance async Python APIs with FastAPI and Pydantic V2. Invoke to create REST endpoints, define Pydantic models, implement authentication flows, set up async SQLAlchemy database operations, add JWT authentication, build WebSocket endpoints, or generate OpenAPI documentation. Trigger terms: FastAPI, Pydantic, async Python, Python API, REST API Python, SQLAlchemy async, JWT authentication, OpenAPI, Swagger Python.

2026-05-200 platforms