n8n-automation

This skill documentation implements expected actions for managing n8n via its REST API and is internally consistent with its purpose. There are no signs of malicious code, obfuscated payloads, remote download-and-execute instructions, or third-party credential forwarding. The primary security concerns are operational: the API key is high-privilege and advice to store it in plaintext or export it into environment variables can lead to credential leakage. Webhook endpoints are unauthenticated by design and exposing webhook URLs can allow arbitrary triggers. Overall this appears benign in intent but operationally moderate risk if credentials or URLs are mishandled.