ojuliocouto

Automation Creator Iautomate — DevOps skill for Claude Code

DevOps community

A Claude Code skill that plans and builds automations the IAutomate way: business-first requirements, a deliberate platform decision (n8n or Cloudflare Workers), a written plan, and a guided build wit.

How to install Automation Creator Iautomate

This entry records only its repository, not the path inside it, so there is no exact command to give. Open ojuliocouto/automation-creator-iautomate and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Automation Creator Iautomate does

A Claude Code skill that plans and builds automations the IAutomate way: business-first requirements, a deliberate platform decision (n8n or Cloudflare Workers), a written plan, and a guided build wit.

Alternatives in DevOps

README

Automation Creator by IAutomate

A Claude Code skill that plans and builds automations the IAutomate way: business-first requirements, a deliberate platform decision (n8n or Cloudflare Workers), a written plan, and a guided build with safety gates.

Built by [Júlio Couto](https://github.com/ojuliocouto), founder of **IAutomate**, for students of the IAutomate mentorship and Escola de Automação e I.A. The skill content is intentionally in Brazilian Portuguese, because that is the language it teaches in.

What this is

  • A guided methodology, not a template dump. The skill interviews you about the business problem, matches it against a catalog of battle-tested automation patterns (cart recovery, launch message sequences, sale webhooks, mass dispatch, lead routing, recurring reports, real-time alerts), decides the right platform with you, writes a plan, and only then builds.
  • A teacher. Every decision comes with the reasoning. The goal is that you finish each automation knowing more architecture than when you started.
  • Safety-first by design. n8n workflows are always created deactivated, and Workers are deployed in two steps (first without any automatic trigger, then the student enables it after testing); activation is a human act, after review. Every build is preceded by a dry-run showing exactly what will be created. Mass-messaging flows never trigger themselves.

What this is NOT

  • Not a library of ready-made workflows to import blindly. The catalog provides skeletons; the interview shapes them to your case.
  • Not a hosted service. Everything runs on your infrastructure: your n8n instance, your Cloudflare account, your credentials, your machine.
  • Not a substitute for reviewing what goes to production. The skill enforces review gates precisely because automation that messages real people deserves human eyes.

How it works

  1. Interview: trigger, data flow, volume, and the question that matters most: what happens when it fails?