n8n Workflow Engineering
v1.0.0Expertise in designing, building, debugging, and scaling production-grade n8n workflows with proper error handling, versioning, and modular architecture.
⭐ 0· 509·1 current·1 all-time
by@1kalin
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (n8n workflow design, debugging, scaling) matches the SKILL.md content (health checks, architecture patterns, trigger/security checklists, templates). It requests no unrelated credentials, binaries, or system paths.
Instruction Scope
The SKILL.md stays within the domain of designing and implementing n8n workflows (checklists, YAML briefs, webhook security, cron patterns, node organization). It recommends using n8n credentials and HMAC/JWT verification patterns; the guide implies secrets will be used inside n8n credential store but the skill itself does not request secrets. As with any guidance that produces code (code-node snippets), review any generated code before running it in production.
Install Mechanism
Instruction-only skill with no install spec and no code files to write to disk. Low installation risk.
Credentials
The skill declares no environment variables or credentials. The guidance sensibly recommends using n8n's credential store and secure handling of HMAC/JWT secrets — there is no disproportionate or unexplained credential request.
Persistence & Privilege
always:false and normal autonomous invocation settings. The skill does not request persistent system privileges or attempt to modify other skills or system-wide config.
Assessment
This skill is an instruction-only methodology/guide for building n8n workflows and appears coherent with that purpose. Before using it: (1) remember it does not ship code or install anything — you'll copy or generate workflow definitions and code-node snippets yourself, so review any generated code carefully before running it; (2) the guide recommends using secrets (HMAC keys, API keys, JWTs) inside n8n — never paste secrets into shared/public nodes; use n8n's credential store; (3) code nodes allow arbitrary JavaScript execution inside n8n — vet logic for unsafe operations; (4) the README links to paid context packs and external URLs — treat those like any third-party resource and validate before purchasing; (5) because the skill is instruction-only and asks for no env vars, there is low technical risk from the skill itself, but real workflows built from it will still require credentials and access to external systems, so apply least privilege and standard security controls when deploying. Overall assessment: coherent and appropriate for its stated purpose.Like a lobster shell, security has layers — review code before you run it.
automationvk9751xkxnm2gk539f7jxxz77v981kh9hintegrationvk9751xkxnm2gk539f7jxxz77v981kh9hlatestvk9751xkxnm2gk539f7jxxz77v981kh9hn8nvk9751xkxnm2gk539f7jxxz77v981kh9hnocodevk9751xkxnm2gk539f7jxxz77v981kh9hworkflowvk9751xkxnm2gk539f7jxxz77v981kh9h
License
MIT-0
Free to use, modify, and redistribute. No attribution required.