url-parsing

Fetch and parse OpenAPI and Swagger specifications from URLs.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/GolfNext/golfnext-tool-kiosk-support-page --skill url-parsing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: url-parsing
Source: https://github.com/GolfNext/golfnext-tool-kiosk-support-page/tree/main/.claude/plugins/mvp-dev-stack/skills/url-parsing
Command: npx skills add https://github.com/GolfNext/golfnext-tool-kiosk-support-page --skill url-parsing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @apidevtools/swagger-parser, zod, yaml, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of integrating with external APIs by enabling the fetching and parsing of API documentation directly from URLs, eliminating manual specification handling.

Core Features & Use Cases

  • Remote API Spec Fetching: Securely retrieves OpenAPI/Swagger specifications from provided URLs via a backend API route to bypass CORS restrictions.
  • URL Validation: Ensures that provided URLs are in a valid format before attempting to fetch.
  • Endpoint Extraction: Parses fetched specifications to extract API endpoints, their methods, parameters, and descriptions.
  • Use Case: When building a feature that allows users to input a URL to an API's documentation, this Skill handles the validation, fetching, and parsing, making the API's structure readily available for use.

Quick Start

Use the url-parsing skill to fetch and parse the API specification from the URL 'https://api.example.com/v1/swagger.json'.

Frequently Asked Questions about url-parsing

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

FAQPage Schema
How do I fetch and parse a remote OpenAPI or Swagger specification from a URL?

To fetch and parse a remote OpenAPI or Swagger spec, provide the documentation URL. The skill validates the URL format, retrieves the specification via a backend route to bypass CORS restrictions, and extracts the API endpoints.

What is the best way to extract API endpoints and methods from a Swagger documentation URL?

The best way to extract API endpoints is parsing the fetched specification with swagger-parser. This process reads the remote Swagger or OpenAPI definition and isolates the available endpoints, methods, parameters, and descriptions.

Does this approach handle CORS restrictions when fetching remote API specs?

Yes, fetching remote API specs handles CORS restrictions by routing requests through a backend API route. This backend proxy securely retrieves the OpenAPI or Swagger definitions from the provided URL without client-side CORS blocks.

How do I validate a URL before attempting to fetch an OpenAPI specification?

To validate a URL before fetching an OpenAPI specification, the skill checks the provided string against a defined schema. It uses Zod validation to ensure the URL is in a valid format before any network request is attempted.

Can I use swagger-parser to parse both YAML and JSON API specifications?

Yes, you can parse both YAML and JSON API specifications. The skill utilizes the yaml dependency and swagger-parser to successfully read and validate remote API documentation provided in either of these formats.