add-tool-from-openapi-spec

Generate a Pixie tool wrapper from an OpenAPI/Swagger REST endpoint.

6|1|Updated May 17, 2026
One-click install
npx skills add https://github.com/AlexKapadia/Pixie --skill add-tool-from-openapi-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-tool-from-openapi-spec
Source: https://github.com/AlexKapadia/Pixie/tree/main/.claude/skills/add-tool-from-openapi-spec
Command: npx skills add https://github.com/AlexKapadia/Pixie --skill add-tool-from-openapi-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Wraps a REST API endpoint from an OpenAPI/Swagger specification as a Pixie tool - generating tool.json from the spec parameters and a httpx-based main.py, then validating the integration.

Core Features & Use Cases

  • Validates the OpenAPI document and selects the endpoint to wrap, or prompts for a choice when multiple endpoints exist.
  • Maps path parameters, query parameters, and request bodies into lightweight Pixie inputs and converts responses into usable outputs.
  • Auto-generates tool.json, pyproject.toml, and a deterministic /run workflow that executes the wrapped API via httpx, with configurable authentication through environment variables.

Quick Start

Provide the OpenAPI/Swagger URL or local spec path and the tool will generate a Pixie wrapper ready for validation.

Frequently Asked Questions about add-tool-from-openapi-spec

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

FAQPage Schema
How do I convert an OpenAPI spec into a callable tool?

To convert an OpenAPI spec into a callable tool, this Skill validates the document and auto-generates a tool.json file mapping path and query parameters into lightweight inputs for immediate use.

Can I wrap a specific REST API endpoint from a Swagger document?

Yes, you can wrap a specific REST API endpoint from a Swagger document by providing the spec URL or local path, and the tool will prompt you to select when multiple endpoints exist.

How does httpx handle API requests generated from OpenAPI specifications?

Httpx handles API requests generated from OpenAPI specifications by executing a deterministic run workflow within main.py, translating request bodies to JSON and returning usable outputs.

Do I need environment variables for API key authentication when wrapping an API?

Yes, you need environment variables for API key or bearer token authentication when wrapping an API, as the generated configuration securely maps these credentials for endpoint access.

What files are auto-generated when wrapping a REST API from a specification?

Wrapping a REST API from a specification auto-generates tool.json for inputs, pyproject.toml for project configuration, and main.py containing the httpx-based run logic.

Are there limitations when mapping request bodies to JSON from an OpenAPI spec?

A limitation when mapping request bodies to JSON is that the process targets single or minimal endpoint sets, translating request bodies only when present and configuring environment-based authentication.