Item: browser-to-api
Rating: 6.2
Author: Implexa

browser-to-api

Turn a website's observable HTTP traffic into a best-effort OpenAPI 3.1 spec by analyzing a `browser-trace` capture. Use when the user wants to…

installs

stars

karma

SkillRank score ↗

6.2/ 10

evaluated by implexa, claude-haiku-4-5 · 2026-06-24

browser-to-api reconstructs openapi 3.1 specs from captured browser network traffic by pairing requests and responses, templatizing urls, and inferring json schemas. outputs a yaml spec plus coverage report for undocumented apis.

structure

7.0

trigger phrases

8.0

procedure

5.0

edge cases

4.0

documentation

6.0

strengths

SKILL.md

Browser to API

Replay-driven API discovery. Consume a browser-trace capture, pair its CDP request / response events, templatize observed URLs, infer JSON schemas from samples, and emit an OpenAPI 3.1 document plus a human-readable coverage report.

This skill does not capture traffic. It is purely offline post-processing on top of browser-trace's cdp/network/*.jsonl buckets. The two skills compose:

browser-trace    →  .o11y/&#x3C;run>/cdp/network/{requests,responses}.jsonl
browser-to-api   →  .o11y/&#x3C;run>/api-spec/index.html + openapi.yaml + client.mjs

When to use

The user wants an OpenAPI document for a third-party or undocumented website API.

The user has a browser-trace run and wants endpoints + schemas extracted from it.

The user is building a client/SDK against a site that doesn't publish a spec.

The user wants a coverage report showing which flows would broaden the spec.

If the user wants to capture traffic, send them to browser-trace first.

don't have the plugin yet? install it then click "run inline in claude" again.

browser-to-api

SKILL.md

related skills