agentleFS
tmolavitmolavi/n8n-agent-skills/skills/n8n-credentials-security/SKILL.md

n8n-credentials-security

Skill1 starsChanged 3 months agoMITView on GitHub

Use whenever auth, API keys, OAuth, tokens, secrets, or credential setup appears in n8n work. Enforces credential system usage, least privilege, and safe HTTP auth patterns.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use n8n Credentials UI/API.

    line 18
  2. Distinctive:

    Do not ask the user for the cosmetic display name obsessively — focus on type + scopes.

    line 24
  3. Distinctive:

    Never echo full API keys back in summaries.

    line 25
  4. Distinctive:

    Prefer managed/connect credentials when the user has no preference and platform supports it.

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

n8n Credentials & Security

Author: Taghi Molavi

Non-negotiables

  1. No secrets in parameters, sticky notes, git, or Code strings.
  2. Use n8n Credentials UI/API; reference by credential attachment on the node.
  3. Least privilege scopes; separate prod/staging credentials.
  4. Rotate on leak; assume chat logs are semi-public.
  5. For HTTP without native node: HTTP Request + proper credential type (OAuth2, Header Auth, etc.).

Agent behavior

  • Do not ask the user for the cosmetic display name obsessively — focus on type + scopes.
  • Never echo full API keys back in summaries.
  • Prefer managed/connect credentials when the user has no preference and platform supports it.

Checklist

  • Credential type matches API
  • Test on staging first
  • Webhook signatures verified
  • No secret in workflow export shared publicly (strip credentials on export)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.