http-endpoint-add

Configure and expose HTTP endpoints as minimal-API lambdas in Program.cs.

55|1|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/MrSuttonmann/flightjar --skill http-endpoint-add
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: http-endpoint-add
Source: https://github.com/MrSuttonmann/flightjar/tree/main/.claude/skills/http-endpoint-add
Command: npx skills add https://github.com/MrSuttonmann/flightjar --skill http-endpoint-add

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables developers to add new HTTP endpoints to the FlightJar API, transforming manual wiring into consistent, testable minimal-API lambdas.

Core Features & Use Cases

  • Supports GET endpoints for reads and POST endpoints for state-changing actions, including /healthz and other /api/* routes.
  • Enforces snake_case JSON responses, parameter binding via DI, and structured payloads when features are disabled.
  • Includes guidance for testing and validation to ensure endpoints are robust and maintainable.

Quick Start

Create a new HTTP endpoint in the FlightJar API by adding a MapGet/MapPost route in dotnet/src/FlightJar.Api/Program.cs with DI and basic validation.

Frequently Asked Questions about http-endpoint-add

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new HTTP endpoint to a minimal API in Program.cs?

Yes, minimal-API lambdas enforce snake_case JSON responses for HTTP endpoints. When features are disabled, the API returns structured payloads to maintain consistent response formats across all endpoints.

Can I use dependency injection and feature flags in minimal API endpoints?

Yes, minimal API endpoints use dependency injection for service binding and support feature-flag guarded responses. This ensures endpoints are testable and securely control access to exposed API routes.

What's the best way to validate inputs for a POST endpoint in a minimal API?

The best way to validate POST endpoint inputs in a minimal API is to enforce validation directly within the MapPost lambda in Program.cs. This ensures state-changing actions process robust, verified data.

When should I use GET versus POST for minimal-API route creation?

Use GET for minimal-API route creation when handling read operations, and POST for state-changing actions or resets. This convention ensures HTTP endpoints align with standard REST verb semantics.