What problem does it solve? Training data about public APIs goes stale quickly, leading to wrong endpoint paths, outdated parameter types, and incorrect auth assumptions. This Skill directs the agent to check the APIs-guru openapi-directory (2500+ machine-readable OpenAPI specs, auto-updated weekly) before consulting memory, doc sites, or Stack Overflow. ## Core Features & Use Cases - Spec-first lookup workflow: Search the openapi-directory by provider domain (stripe.com, github.com, googleapis.com, etc.), pick the latest version, and fetch the raw OpenAPI YAML from GitHub. - Structured extraction: Pull endpoint paths, request/response schemas, security schemes, and server base URLs directly from the spec instead of guessing. - Fallback guidance: Defines when to fall back to doc sites or context7 (API not in directory, GraphQL APIs, private APIs). - Use Case: When writing a Stripe integration, fetch the official OpenAPI spec to confirm exact parameter names, types, and auth scheme rather than relying on potentially outdated training knowledge. ## Quick Start Look up the current OpenAPI spec for the GitHub API in the openapi-directory and show me the correct endpoint and parameters for creating an issue.
