What problem does it solve?
Building credential recipes from memory produces wrong auth headers, dead-end key URLs, and unverifiable test endpoints that break user setup flows. This Skill enforces a documentation-first lookup procedure so every credential hint points to a real, fetched page.
Core Features & Use Cases
- Auth Scheme Lookup: Identifies the exact header name, prefix, and casing from the provider's authentication docs.
- Key Page Discovery: Locates the dashboard, console, or app URL where users create or copy API keys, avoiding invented paths.
- Verification Endpoint Selection: Finds a side-effect-free GET endpoint that rejects bad keys with 401 or 403 for credential testing.
- Use Case: When composing credential hints for a service like Apify or ElevenLabs during post-build-flow setup, this procedure sources the auth template, docsUrl, and testUrl directly from the provider's real documentation.
Quick Start
Research the credential recipe for the service used in this workflow and return the auth template, key page URL, and verification endpoint.