n8n-operations
Skill0 starsChanged 3 months agoMITView on GitHub
Build, inspect, validate, document, migrate, and template n8n workflows, workflow JSON exports, nodes, credentials placeholders, MCP Server Trigger nodes, MCP Client Tool nodes, and self-hosted automation patterns. Use when a user asks about n8n, workflow exports, workflow templates, branching automation, private workflow engines, or Make-to-n8n migration.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- automation-tool-routerSkill
- codex-automation-operatorSkill
- make-com-operationsSkill
- mcp-governanceSkill
- starlight-excellenceSkill
- starlight-queen-queueSkill
- xquik-public-x-dataSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 8
Use n8n for durable technical workflow ownership, reusable templates, private data paths, and workflows that benefit from JSON review.
- Distinctive: line 26
remove credentials before sharing
- Distinctive: line 35
Use n8n's MCP server capabilities to expose selected workflows to agents.
- Distinctive: line 36
Use MCP Client Tool nodes when an n8n agent needs tools from an external MCP server.
- Distinctive: line 41
Do not commit credentials blocks.
- Distinctive: line 42
Do not publish live webhook URLs.
- Distinctive: line 43
Do not activate production workflows as a validation shortcut.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
n8n Operations
Use n8n for durable technical workflow ownership, reusable templates, private data paths, and workflows that benefit from JSON review.
Best Fit
- multi-step branching workflows
- API orchestration with transformations
- workflow templates for developers
- private or self-hosted automations
- MCP Server Trigger entry points
- n8n agents using MCP Client Tool nodes
Workflow Review Checklist
For exported workflow JSON:
- parse JSON before editing
- confirm all nodes have stable ids
- remove credentials before sharing
- check dangling connections
- separate test and production webhooks
- define retry and error workflow behavior
- record idempotency key and dedupe policy
- include mock input and output payloads
MCP In n8n
Use n8n's MCP server capabilities to expose selected workflows to agents. Use MCP Client Tool nodes when an n8n agent needs tools from an external MCP server. Keep tool lists small and explicit.
Safety
- Do not commit credentials blocks.
- Do not publish live webhook URLs.
- Do not activate production workflows as a validation shortcut.
- Human approval is required for outbound sends, deletes, production deploys, account changes, and spending.
Validation
When available, run:
python scripts/validate_n8n_workflow.py path/to/workflow.json
python scripts/scan_public_safety.py path/to/public/exportOutput Shape
Return: workflow map, node table, data contract, error route, MCP exposure plan, validation commands, and migration notes.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

