credential-recipe-research

Lookup 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.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

100%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exceptionally well-crafted instruction-only skill body: lean, fully actionable, with a clearly sequenced workflow and explicit validation/omit-on-failure checkpoints at every stage. No bundle files are needed or referenced, and structure is clean.

Dimension	Reasoning	Score
Conciseness	Lean and efficient with no concept explanations; every line is an actionable rule or concrete step and assumes Claude's competence.	5 / 5
Actionability	Provides concrete executable guidance — exact search query strings, `research(action="web-search")`/`fetch-url` commands, and specific endpoint examples like `/v1/account` and `elevenlabs.io/app/settings/api-keys`.	5 / 5
Workflow Clarity	A clearly numbered 1–4 sequence with explicit validation checkpoints ("stop at the first qualifying hit", "Nothing conclusive → omit docsUrl") and omit-on-failure feedback loops.	5 / 5
Progressive Disclosure	Self-contained, well-organized into clearly signaled sections with no nested references; appropriately single-file for a single-purpose procedure.	5 / 5
	Total	20 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A highly specific, distinctive description that clearly answers both what it does and when to use it. Its only weakness is trigger-term jargon that lacks synonyms or file-extension variants a user might naturally say.

Dimension	Reasoning	Score
Specificity	"sources the auth template, the key-issuing docsUrl and an auth-rejecting testUrl" lists multiple concrete actions covering every recipe field comprehensively.	5 / 5
Completeness	Explicitly states both what (lookup procedure sourcing template/docsUrl/testUrl from real docs) and when ("Load before composing credentialHints… or when asked to fix a recipe…").	5 / 5
Trigger Term Quality	"fix a recipe whose template, key page or test endpoint is wrong" is a natural trigger, but coverage leans on system jargon ("credentialHints", "post-build-flow") with no synonyms or extensions.	4 / 5
Distinctiveness Conflict Risk	Narrow niche (Simplified Custom Auth recipe fields, recipe-fixing triggers) makes it clearly distinguishable with minimal conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: n8n-io/n8n
Path: packages/@n8n/instance-ai/skills/credential-recipe-research/SKILL.md
Commit: 7700b76

Reviewed: ~4 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.