credential-recipe-research

Research API authentication templates, key pages, and verification endpoints from provider documentation.

203k|60.5k|Updated Jun 22, 2019
One-click install
npx skills add https://github.com/n8n-io/n8n --skill credential-recipe-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: credential-recipe-research
Source: https://github.com/n8n-io/n8n/tree/main/packages/%40n8n/instance-ai/skills/credential-recipe-research
Command: npx skills add https://github.com/n8n-io/n8n --skill credential-recipe-research

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about credential-recipe-research

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

FAQPage Schema
How do I find the correct API authentication header for a third-party service?

Fetch the provider's authentication documentation using web search and URL fetching. Record the header name, prefix word, and casing exactly as documented, such as Authorization: Bearer or a custom header like xi-api-key.

Where do users create or copy API keys for a given service?

Search for the service dashboard, console, or app settings page where keys are issued. The URL typically lives on an app or console host, not under docs or reference paths, and must appear verbatim on a fetched page.

What endpoint should I use to verify an API key works?

Use a documented, side-effect-free GET endpoint that returns 401 or 403 for invalid keys. Check account, usage, or list endpoints in that order, and skip endpoints that return 2xx regardless of authentication status.

Why should I avoid constructing dashboard URLs by analogy with other APIs?

Dashboards are apps behind login walls that return 200 for any invented route. A fetch cannot verify the path, so only emit deep dashboard URLs that appear verbatim on a fetched documentation page.

When should I omit the docsUrl or testUrl from a credential recipe?

Omit docsUrl when no conclusive key-issuing page is found after searching. Omit testUrl when no qualifying verification endpoint exists, since an honest unverifiable credential beats a false green status.