extract-apilisted

Extract API endpoints from any source and import them into sdkck as executable CLI commands. ## Overview This skill reads API documentation from three source types: - **GitHub repositories** (public): scans for OpenAPI specs, Postman collections, GraphQL schemas, README, and docs files - **HTTP/HTTPS documentation URLs**: fetches single or multi-page doc sites; probes for spec/collection/schema files; POSTs introspection query to live GraphQL endpoints - **Local files**: reads OpenAPI JSON/YAML, Postman collections, GraphQL SDL/introspection JSON, markdown, HTML, or plain text When an existing OpenAPI spec, Postman collection, or GraphQL schema is found it is used directly — no extraction needed. Otherwise, API endpoints are extracted from the documentation and an OpenAPI 3.0 JSON document is generated. Either way, the result is imported via `sdkck api import`. ## Usage ``` /extract <source> [--name <name>] ``` <!-- prettier-ignore --> | Argument | Description | |----------|-------------| | `<source>` | GitHub URL, HTTP/HTTPS URL, or local file path | | `--name` | Override the API name (default: derived from source) | **Examples:** ```bash /extract https://petstore3.swagger.io/api/v3/openapi.json --name petstore /extract https://github.com/stripe/openapi --name stripe /extract https://developers.notion.com/reference/intro /extract https://docs.github.com/en/rest --name github /extract https://api.example.com/graphql --name myapi /extract ./my-workspace.postman_collec