Plan and validate HTTP requests against OpenAPI specifications in dry-run mode.
npx skills add https://github.com/joshka0/foxctl --skill foxctl-openapi
Please help me install this Agent Skill. Skill: foxctl OpenAPI Source: https://github.com/joshka0/foxctl/tree/main/configs/skills-condensed/foxctl-openapi Command: npx skills add https://github.com/joshka0/foxctl --skill foxctl-openapi
It removes the guesswork of crafting correct HTTP requests by planning them from OpenAPI specs and validating them before you send anything.
Ask the agent to plan and validate a GET request by providing the base_url and path, while enabling dry-run so it does not execute the HTTP call.
High-intent search queries and answers about installing and using this skill.
You can validate an HTTP request against an OpenAPI specification by using a dry-run mode to plan the request. This generates a plan-only output that checks base URL, path, method, headers, and body correctness without executing the call.
OpenAPI-driven request planning translates your base URL, path, and method into a concrete HTTP request plan. It applies spec-aware validation rules to catch parameter mismatches early, preventing invalid request construction before execution.
Yes, you can explore API endpoints and prepare POST or PUT request bodies using OpenAPI validation. The planning workflow maps query parameters, headers, and body payloads into a validated request result for correctness.
Construct a valid HTTP request plan by providing the base URL, path, and method while enabling dry-run behavior. This produces a plan-only output that maps and validates your request components against the OpenAPI spec without sending it.
Yes, dry-run API validation supports endpoint discovery by allowing you to set query parameters and headers. It validates these components against OpenAPI specifications to ensure your request design is fully spec-compliant before execution.
Razaib-khanAlign frontend requests with backend API contracts to fix integration failures.
microwindDiagnose HTTP requests and responses to uncover API issues.
Pieverse-EngGenerate signed EIP-712 requests for Aster Futures API endpoints.
dreadnodeSearch and replay HTTP proxy traffic via Caido MCP tools.
