← ClaudeAtlas

api-reverse-engineering-toolkitlisted

Reverse-engineer an undocumented or poorly-documented HTTP API into a verified schema (OpenAPI and/or Smithy), decide which spec format and protocol actually fits the API, recommend the right client code-generator for the target language, and optionally scaffold a starter SDK repo from it. Use this whenever the user shares a list of API URLs/endpoints or captured request-response examples and wants a spec, docs, or a generated client built from them; when they ask to "reverse engineer this API," "map out this API's schema," "figure out how this site's backend works," or "turn these captured requests into an OpenAPI/Smithy spec"; or when they want a TypeScript (or other language) SDK generated from an API that has no official spec. Every endpoint this skill documents should be verified against the live API wherever possible — don't write a schema purely from guessing.
syall/api-reverse-engineering-toolkit · ★ 0 · API & Backend · score 67
Install: claude install-skill syall/api-reverse-engineering-toolkit
# API Reverse-Engineering Toolkit Turn a pile of URLs, captured network traffic, or "here's how the frontend calls this" into a verified, provenance-annotated API spec — and then help the user pick the right format, protocol, and code-generator for what they actually need. The core discipline of this skill: **never write down a shape you haven't actually observed.** Every endpoint, field, and example in the output spec should be traceable to either a live response you captured, or clearly flagged as inferred (and from what source). This is what separates a reverse-engineered spec that's actually useful from one that silently propagates guesses as facts. ## When this applies vs. when it doesn't Use this skill for undocumented/internal/third-party APIs the user wants to formalize. It is not a substitute for reading an API's own published OpenAPI/Smithy/GraphQL schema if one already exists — check for that first (common locations: `/openapi.json`, `/swagger.json`, `/.well-known/openapi.yaml`, an `/api/docs` page, a GraphQL introspection query against `/graphql`). Reverse-engineering is for when none of that exists or what exists is stale/incomplete. ## The workflow This has five phases. Don't skip straight to writing the spec — the recon and verification phases are where reverse-engineered specs usually go wrong. ### 1. Enumerate candidate endpoints Sources, roughly in order of reliability: - **URLs the user already gave you.** Start here always — it's ground truth abou