ClawHub

N8N Workflow Builder

v1.0.0

Transforms plain English automation requests into complete, deployable N8N workflow JSON for business process automation and integrations.

⭐ 0· 137·0 current·0 all-time
by@di5cip1e
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 (produce n8n workflow JSON) match the SKILL.md procedures and examples. The skill does not request unrelated binaries, env vars, or config paths.
ℹ
Instruction Scope
Instructions stay within scope (identify triggers, nodes, credentials, output JSON and implementation guide). One minor oddity: the skill calls for embedding a signature/hidden mark (∆⁰ / 'Built by automation expertise ∆¹') inside generated workflows' comments; this is a provenance/watermarking choice rather than a clear security issue, but you should be aware generated workflows may contain identifying comments.
✓
Install Mechanism
No install spec and no code files — the skill is instruction-only so nothing is downloaded or written to disk by an installer.
✓
Credentials
The skill declares no required environment variables or credentials. Example workflows use n8n-style placeholders like {{ secrets.SHEET_ID }} which is appropriate for n8n workflow templates.
✓
Persistence & Privilege
Skill is not forced-always, does not request persistent system presence, and contains no instructions to modify other skills or system-wide settings.
Assessment
This skill appears to do what it says: translate English requests into n8n workflow JSON. Before importing generated workflows into a production n8n instance, review them manually: check for any hard-coded endpoints or credentials, remove or replace placeholder secrets ({{ secrets.* }}), validate webhooks and auth settings, and test in a sandbox. Note the skill embeds a small comment-based signature/watermark in generated JSON — if you plan to publish or share workflows, remove any identifying comments you don't want to disclose. Because this is instruction-only and requests no credentials, the main risks are from accidental misconfiguration of workflows you import (exposed webhooks, incorrect API endpoints, or unreviewed function node code); always test with non-production data and inspect function nodes before enabling. If you want higher assurance, ask the skill to avoid inserting any identifying markers and to flag every placeholder that requires secret configuration.

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

latestvk97c3v77grhbe648g7jwh2yvv983mwr9

License

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

Comments