Firm N8n Bridge Pack
v1.0.0n8n workflow bridge pack. Export OpenClaw pipelines to n8n format and import n8n workflows. 2 bridge tools.
⭐ 0· 363·3 current·3 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name and description (bridge between OpenClaw and n8n) align with the content: two tools are declared and the SKILL.md describes exporting/importing workflows. The declared dependency on mcp-openclaw-extensions >= 3.0.0 is plausible for this functionality.
Instruction Scope
SKILL.md lists tool names and example usage and only references expected inputs (config_path, pipeline_name, workflow_path). It does not instruct reading unrelated files or secrets. However the instructions are high-level and do not include concrete implementation steps — it assumes other skill(s) or binaries provide the named tools, and includes an explicit AI-generated warning requiring human validation.
Install Mechanism
No install spec and no code files are present (instruction-only). This minimizes disk-write/installation risk, but also means the skill is a wrapper/integration description that depends on external components being present.
Credentials
The skill does not request environment variables, credentials, or config paths. The declared dependency (mcp-openclaw-extensions) is a reasonable supporting requirement for the stated purpose.
Persistence & Privilege
always is false and the skill doesn't request persistent system changes or modify other skills' configs. The skill allows model invocation (the platform default); this is normal and not flagged by itself.
Assessment
This skill is an instruction-only bridge that describes two tools but contains no implementation and no source/homepage. Before installing or enabling it: 1) confirm that mcp-openclaw-extensions >= 3.0.0 (the declared dependency) is present and inspect that package's code to see how the export/import are actually performed; 2) don't run it against production data until you validate mappings and output; 3) treat the skill as documentation/wiring rather than executable code — ensure the named commands/tools exist from trusted sources; 4) because the source is unknown, prefer manual review and testing in a safe environment and consider disabling autonomous invocation if you do not want the agent to call external tools without explicit approval.Like a lobster shell, security has layers — review code before you run it.
latestvk97apaqbg2hsqm19phmwe5kmm1823qk8
License
MIT-0
Free to use, modify, and redistribute. No attribution required.