make-com-operations
Skill0 starsChanged 3 months agoMITView on GitHub
Design, document, review, and govern Make.com automations, scenarios, modules, routers, webhooks, and Make MCP exposure. Use when a user asks about Make.com, Integromat, Make scenarios, SaaS workflow glue, form-to-CRM flows, Make MCP server setup, scenario inputs and outputs, or whether Make is preferable to n8n or Codex automations.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- automation-tool-routerSkill
- codex-automation-operatorSkill
- mcp-governanceSkill
- n8n-operationsSkill
- starlight-excellenceSkill
- starlight-queen-queueSkill
- xquik-public-x-dataSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
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
- Distinctive: line 8
Use Make.com when the workflow is mostly SaaS glue and speed matters more than deep code ownership.
- Distinctive: line 47
Prefer run-only scopes first.
- Distinctive: line 52
Never run a production scenario while testing unless the user explicitly asks.
- Distinctive: line 53
Use mock payloads for public examples.
- Distinctive: line 54
Do not paste live webhook URLs or connection names into final answers.
≈ “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
Make.com Operations
Use Make.com when the workflow is mostly SaaS glue and speed matters more than deep code ownership. Keep live scenario IDs, webhook URLs, and credentials out of public artifacts.
Best Fit
- lead capture and routing
- simple CRM or sheet updates
- purchase or signup follow-up
- approval notifications
- public-safe low-code demos
- MCP exposure of specific on-demand scenarios
Use n8n Instead When
- the workflow needs code-heavy branching
- the export should become a public technical template
- sensitive data should stay self-hosted
- step volume makes action-based billing expensive
- git review of workflow JSON matters
Scenario Design Checklist
Return a scenario map with:
- trigger
- modules
- filters and routers
- dedupe key
- retry policy
- error route
- audit trail
- human approval gate
- test payload
- rollback or disable step
Make MCP Rule
Expose only activated on-demand scenarios with explicit inputs and outputs. Prefer run-only scopes first. Avoid management scopes until the scenario has a clear owner, tests, and approval gates.
Safety
- Never run a production scenario while testing unless the user explicitly asks.
- Use mock payloads for public examples.
- Do not paste live webhook URLs or connection names into final answers.
- Human approval is required before outbound email, posting, deleting, inviting, or spending.
Output Shape
Return: scenario map, data contract, risk gates, Make-vs-n8n rationale, validation steps, and what remains manual.
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.

