skillboardUpdated every 6 hours
skillboardLookup procedure for Simplified Custom Auth recipe fields — sources the auth template, the key-issuing docsUrl and an auth-rejecting testUrl from the provider's real documentation instead of memory. Load before composing credentialHints for a service without a dedicated credential type (the post-build-flow setup step), or when asked to fix a recipe whose template, key page or test endpoint is wrong.
Credential Recipe Research A recipe is only as good as the documentation it came from. This is a procedure, not guidance: execute every step with the tool and keep only findings you can point to on a fetched page. Guessed URLs are how users end up on the wrong page with a key that can't be verified. Inputs: the service name and the API host(s) the workflow's nodes call. 1. Auth scheme (template) Fetch the provider's authentication docs — with , then the best docs hit. Record the scheme EXACTLY…
Full body not shown for this license – view the source on GitHub →Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/credential-recipe-research · pinned to the source commit
git clone https://github.com/n8n-io/n8n.git
cd n8n
git checkout b4d91bfe8a293106815b308a841e210562002735
mkdir -p ".claude/skills/credential-recipe-research"
cp -r "packages/@n8n/instance-ai/skills/credential-recipe-research" ".claude/skills/credential-recipe-research"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit b4d91bfe8a29. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
References credentials, tokens or secret files that a skill should not need.
Evidence: [redacted]· fingerprint 2e9bc6c94a4cbdfe