From make-automation-specialist
Diverge-then-converge for Make.com automation planning. Fires when the user has a business problem but no clear automation direction. Takes messy impulses like 'I'm wasting time on X' or 'I need to be more efficient' and produces ONE pointed direction sentence — the input that discovery-to-blueprint or kickstart-intake needs. Always routes to the next skill in the factory chain. Never produces standalone output.
How this skill is triggered — by the user, by Claude, or both
Slash command
/make-automation-specialist:brainstorm-sharpThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The user knows they want to automate something but doesn't know what, exactly.
The user knows they want to automate something but doesn't know what, exactly.
This skill converts "I keep manually entering leads from Typeform into our CRM"
into "Automatically sync new Typeform submissions into HubSpot as contacts, tagged
by form source." That one sentence is what discovery-to-blueprint or
kickstart-intake can work with.
Never standalone. Output is ONE direction sentence, then hand off.
Ask exactly this (one question):
"Tell me what you're doing manually that shouldn't be manual. One breath."
Wait. Take what comes. Do not ask a follow-up yet.
Choose the 3 most relevant lenses based on what the user said:
REPLACE (different user type): "What if this automation served a completely different role in your business than the obvious one?"
COMBINE (merge two pain points): "What if you automated [thing they said] AND [adjacent manual step that emerged]?"
ELIMINATE (strip to minimum): "If you automated only the single most painful moment — what's left? What's the one step that must be automatic?"
REPURPOSE (new context): "The same automation logic, but applied to a completely different workflow — where else does this pattern exist in your business?"
AMPLIFY (10× scale): "If this ran 10× more often or processed 10× more records, which part becomes the bottleneck? What would the automation need to handle?"
For each lens: short question, wait, reflect one line, move to next. After all three: synthesize in 2–3 sentences. Do not present as directions yet.
Present 3–5 directions derived from the lenses. Each is ONE sentence:
[automatically] [what happens] [for who/when] [so that outcome]
Example: "Automatically create a HubSpot contact and assign to the right sales rep whenever a Typeform lead submission comes in with a budget over $10K."
Ask:
"Which one is it? Or tell me how to combine two."
If user picks one → Phase 4. If user wants to combine → synthesize into ONE sentence, confirm → Phase 4. If none fit → one more round: "What's closest? What's wrong with it?"
Do not loop more than twice. If stuck:
"Pick the one that would embarrass you least to abandon. We can always course-correct during the blueprint."
State the direction:
"Direction locked: [one sentence]"
Then assess complexity:
For simple:
"Simple automation — heading into the intake to spec this out." [Begin kickstart-intake with direction as seed]
For complex:
"This has a few moving parts. Let's map the full flow before jumping to Make.com. Starting discovery — I'll ask one question at a time." [Begin discovery-to-blueprint Phase 1 with direction as seed]
This skill fires automatically in two cases:
In both cases: output is a direction sentence → immediate hand-off to the appropriate next skill. Never standalone output.
| Rationalization | Reality |
|---|---|
| "The user described something — that's enough direction" | Test: does it have a trigger, action, and destination? If not, run this skill. |
| "I'll skip the lenses and go straight to directions" | Lenses are what generates non-obvious directions. Skip them and you get the obvious answer the user already had. |
| "The user is too vague to converge" | Force a pick: "Which one embarrasses you least to abandon?" It works. |
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub cardinalconseils/make-automation-specialist --plugin make-automation-specialist