How does the skill execute API tests?

It utilizes the Bash tool to run curl commands, allowing it to capture headers, body content, and status codes directly from the target endpoint.

Does this skill require existing documentation?

No, this skill is specifically designed to create documentation for undocumented or legacy APIs by performing empirical testing and observing real-world behavior.

What is the output format for the documentation?

The skill produces a structured 'endpoint-documentation.md' file featuring tables for parameters, response codes, and structural analysis based on actual test samples.

What kind of test cases does it generate?

It generates a comprehensive suite including valid data examples, format variations, edge cases like boundary values, and intentional invalid inputs to test error handling.

Can it handle authenticated endpoints?

Yes, as long as you provide the necessary authentication headers or tokens during the exploration process, the skill can document secured endpoints.

API Endpoint Exploration

Name: API Endpoint Exploration
Author: Omegaice

byOmegaice

API Development

Documents REST API endpoints through systematic empirical testing and response pattern analysis.

About

API Endpoint Exploration is a specialized skill designed to reverse-engineer and document undocumented or legacy APIs. It guides Claude through a rigorous seven-step process that includes URL structure analysis, parameter identification, automated test case generation, and real-time response capture. By executing empirical tests and analyzing HTTP headers and status codes, the skill produces concise, evidence-based documentation that eliminates guesswork and provides a reliable reference for developers working with mysterious or third-party integrations.

Key Features

Systematic URL and parameter structure analysis
Empirical validation using real-time HTTP request execution
Automated generation of valid, edge, and invalid test cases
Deep analysis of response patterns and status codes
0 GitHub stars
Structured Markdown documentation generation from test results

Use Cases

Reverse-engineering third-party endpoints for custom integrations
Validating API error handling and edge case behavior during development
Documenting legacy internal APIs that lack formal specifications

About

Key Features

Systematic URL and parameter structure analysis
Empirical validation using real-time HTTP request execution
Automated generation of valid, edge, and invalid test cases
Deep analysis of response patterns and status codes
0 GitHub stars
Structured Markdown documentation generation from test results

Use Cases

Reverse-engineering third-party endpoints for custom integrations
Validating API error handling and edge case behavior during development
Documenting legacy internal APIs that lack formal specifications