Skill Detail

Bootstrap an OpenAPI spec from captured API traffic before client or test automation starts

Uses mitmproxy2swagger to turn captured mitmproxy flows or HAR exports into a first-pass OpenAPI document that an agent can refine, validate, and hand off to downstream tooling. Invoke it when the API already exists but the contract does not, and you need a concrete spec before generating clients, mocks, tests, or reviewable docs.

Integrations & ConnectorsMulti-Framework
Integrations & Connectors Multi-Framework Security Reviewed
⭐ 9.3k GitHub stars
INSTALL WITH ANY AGENT
npx skills add agentskillexchange/skills --skill bootstrap-openapi-spec-from-captured-api-traffic-before-client-or-test-automation Copy
Works best when you want a reusable capability, not another fragile one-off prompt.
At a glance
Tools required
Python 3 and pip, plus mitmproxy flow captures or a HAR export from browser DevTools
Install & setup
pip install mitmproxy2swagger
Author
alufers
Publisher
Individual Maintainer
Last updated
Apr 12, 2026
Quick brief

This skill uses mitmproxy2swagger as a bounded reverse-engineering workflow for undocumented HTTP APIs. The tool converts captured mitmproxy flow files or browser-exported HAR files into an OpenAPI 3.0 schema, which gives an agent a concrete starting point instead of a pile of ad hoc request logs. The valuable job here is not β€œuse an API tool.” It is β€œbootstrap a usable contract from real traffic so later automation has something structured to work from.”

How it works

What this skill actually does

Invoke this when a team has a live API, mobile app backend, or internal service that is already being called in the wild, but there is no trustworthy spec to generate a client, create mocks, write contract tests, or diff future changes. An agent can capture representative traffic, run the first pass, review and clean the generated x-path-templates, then rerun the tool to materialize endpoint descriptions and optional examples. That makes it useful before SDK generation, before Schemathesis or Prism-style testing, before documentation backfills, and before integration teams start guessing at request shapes.

The scope boundary matters. This is not a generic API platform entry, a documentation portal, or a full lifecycle governance tool. It is specifically for creating a first-pass OpenAPI document from observed traffic. Its output becomes input for other systems, but the skill itself stops at traffic capture, schema generation, and targeted cleanup. Integration points include mitmproxy, browser DevTools HAR export, OpenAPI validators, client generators, mock servers, and CI pipelines that want a contract artifact to version and review.