ClawHub

N8n Workflow Builder

v1.0.0

Converts plain English automation requests into complete, deployable N8N workflow JSON with triggers, actions, error handling, and setup guidance.

⭐ 0· 121·0 current·0 all-time
by@di5cip1e·duplicate of @di5cip1e/the-director-n8n-workflow-builder
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The name/description match the SKILL.md: it converts natural-language requests into n8n workflow JSON, identifies triggers, nodes, credentials, and provides setup guidance. No unrelated binaries, env vars, or config paths are requested.
✓
Instruction Scope
SKILL.md stays within scope: it instructs the agent to design workflows, output valid n8n JSON, annotate nodes, list required credentials, and give setup/testing guidance. It does not instruct reading local files, accessing system credentials, or sending data to unexpected external endpoints. Example nodes use n8n-style placeholders for secrets, which is appropriate.
✓
Install Mechanism
This is an instruction-only skill with no install spec and no code files, so nothing is written to disk or downloaded during installation — lowest-risk model.
✓
Credentials
The skill declares no required environment variables or credentials. The SKILL.md references placeholders like {{ secrets.SHEET_ID }} and recommends users configure API keys in n8n, which is proportional and expected for a workflow generator.
✓
Persistence & Privilege
The skill is not always-enabled and does not request persistent system privileges or modify other skills. Autonomous invocation is allowed (platform default) but not combined with other red flags.
Assessment
This skill appears coherent and focused on generating n8n workflows. Before importing generated workflows into production, review them manually: check function node code for unsafe JS, replace placeholder secrets with properly-scoped credentials stored in your n8n instance, verify webhook/auth settings, and test in a sandbox. Be cautious about pasting real API keys into generated JSON — configure them in n8n's credential store instead. If you need higher assurance, ask the author for provenance or a sample of more complete output before trusting in sensitive environments.

Like a lobster shell, security has layers — review code before you run it.

latestvk977r0qwrxv31s0thn9ztcbf7583p3qz

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments