agentsclimarketplace

Make com operations

Skill frankxai/starlight-automation-agent-skills/skills/make-com-operations

Portable automation agent skills for the Starlight substrate — scheduling, pipelines, and fleet ops.

Install
npx -y skills add frankxai/starlight-automation-agent-skills --skill make-com-operations

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

1.9 KB, 322 tokens by cl100k_base, as published. Nobody here has run it

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.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.