N8n Workflow Automation 1.0.0
v1.0.0Designs and outputs n8n workflow JSON with robust triggers, idempotency, error handling, logging, retries, and human-in-the-loop review queues. Use when you...
⭐ 0· 1.2k·17 current·20 all-time
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 match the SKILL.md: it designs n8n workflow JSON with retries, idempotency, logging, and review queues. It does not request unrelated binaries, credentials, or system access.
Instruction Scope
All runtime instructions are limited to designing workflow specs, runbooks, and templates. The document explicitly requires asking the user for destinations/credentials before including them and forbids embedding secrets in emitted JSON. It does suggest writing failed items to DB/Sheet in the workflow design (expected), but does not instruct the agent to access local files, other skills' configs, or external endpoints on its own.
Install Mechanism
No install spec and no code files — the skill is instruction-only, so nothing is written to disk or downloaded during install.
Credentials
The skill does not declare any required environment variables or credentials (none are requested up front). The instructions do, correctly, recommend referencing env var names in generated JSON rather than embedding secrets and also tell the agent to stop and ask when credentials are unspecified. Users must supply appropriate credentials when implementing the generated workflows.
Persistence & Privilege
always is false and the skill does not request persistent/system-wide privileges. It does not modify other skills or system configs.
Assessment
This skill is an authoring helper (it produces n8n workflow JSON and a runbook). It is coherent and does not demand credentials itself, but when you use it: 1) never paste secrets or actual credentials into prompts — prefer placeholder env var names; 2) review any generated workflow.json before importing into n8n to ensure no sensitive data is embedded and that node permissions are minimal; 3) provide only the credentials required for the target systems (least privilege) and test generated workflows in a staging environment; 4) when the runbook references storage or review queues, ensure those endpoints are controlled and audited. If you want the skill to generate workflows that interact with specific systems, be prepared to supply safe examples and credential strategy (env var names) rather than secrets.Like a lobster shell, security has layers — review code before you run it.
latestvk97atd6r6z1rh1ytakb090kdrn81nm1y
License
MIT-0
Free to use, modify, and redistribute. No attribution required.