web-api-reverse-engineering

Discover website APIs via Chrome automation and generate OpenAPI 3.1 specs.

6|1|Updated Feb 8, 2026

Search Tags:#versioning #documentation #openapi #web-api #reverse-engineer #api-discovery #chrome-automation

Ready to run

npx skills add https://github.com/vicentereig/engineering --skill web-api-reverse-engineering

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: web-api-reverse-engineering
Source: https://github.com/vicentereig/engineering/tree/main/plugins/engineering-skills/skills/web-api-reverse-engineering
Command: npx skills add https://github.com/vicentereig/engineering --skill web-api-reverse-engineering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

APIs exposed by websites are often undocumented or hard to discover. This skill automates browser-based exploration and network analysis to reveal endpoints and generate OpenAPI 3.1 specifications for client integration and versioning.

Core Features & Use Cases

Discover APIs on web pages using Chrome automation and network analysis to surface endpoints and data schemas.
Document endpoints, parameters, and authentication requirements in the OpenAPI 3.1 format.
Use cases include API discovery for legacy sites, documenting APIs for client libraries, and tracking changes across site iterations.

Quick Start

Initialize a Chrome automation session against a target website to begin API discovery and OpenAPI 3.1 spec generation.

Frequently Asked Questions about web-api-reverse-engineering

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

FAQPage Schema

How do I reverse engineer an undocumented web API from a website?▼

You can discover undocumented web APIs using Chrome automation and network analysis to surface hidden endpoints, map parameters, and generate OpenAPI 3.1 specifications for client integration.

What is the best way to generate OpenAPI specs for legacy sites?▼

Generating OpenAPI specs for legacy sites is done by automating browser-based exploration to discover endpoints, analyze network traffic, and document data schemas directly into OpenAPI 3.1 format.

Can I track API changes across site iterations using network analysis?▼

Yes, you can track API changes across site iterations by repeatedly running Chrome automation against web UIs to discover endpoints and compare the generated OpenAPI 3.1 specifications over time.

Does API discovery with Chrome automation handle pagination and security considerations?▼

API discovery with Chrome automation supports network analysis, HTML scraping, pagination handling, and security considerations during endpoint mapping to ensure comprehensive OpenAPI 3.1 spec generation.

How do I document authentication requirements for discovered web endpoints?▼

You document authentication requirements for discovered web endpoints by using automated network analysis during browser exploration, which captures authentication flows and records them in the OpenAPI 3.1 output.