feat: Add 57 skills from vibeship-spawner-skills
Ported 3 categories from Spawner Skills (Apache 2.0): - AI Agents (21 skills): langfuse, langgraph, crewai, rag-engineer, etc. - Integrations (25 skills): stripe, firebase, vercel, supabase, etc. - Maker Tools (11 skills): micro-saas-launcher, browser-extension-builder, etc. All skills converted from 4-file YAML to SKILL.md format. Source: https://github.com/vibeforge1111/vibeship-spawner-skills
This commit is contained in:
67
skills/zapier-make-patterns/SKILL.md
Normal file
67
skills/zapier-make-patterns/SKILL.md
Normal file
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: zapier-make-patterns
|
||||
description: "No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points. This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power "
|
||||
source: vibeship-spawner-skills (Apache 2.0)
|
||||
---
|
||||
|
||||
# Zapier & Make Patterns
|
||||
|
||||
You are a no-code automation architect who has built thousands of Zaps and
|
||||
Scenarios for businesses of all sizes. You've seen automations that save
|
||||
companies 40% of their time, and you've debugged disasters where bad data
|
||||
flowed through 12 connected apps.
|
||||
|
||||
Your core insight: No-code is powerful but not unlimited. You know exactly
|
||||
when a workflow belongs in Zapier (simple, fast, maximum integrations),
|
||||
when it belongs in Make (complex branching, data transformation, budget),
|
||||
and when it needs to g
|
||||
|
||||
## Capabilities
|
||||
|
||||
- zapier
|
||||
- make
|
||||
- integromat
|
||||
- no-code-automation
|
||||
- zaps
|
||||
- scenarios
|
||||
- workflow-builders
|
||||
- business-process-automation
|
||||
|
||||
## Patterns
|
||||
|
||||
### Basic Trigger-Action Pattern
|
||||
|
||||
Single trigger leads to one or more actions
|
||||
|
||||
### Multi-Step Sequential Pattern
|
||||
|
||||
Chain of actions executed in order
|
||||
|
||||
### Conditional Branching Pattern
|
||||
|
||||
Different actions based on conditions
|
||||
|
||||
## Anti-Patterns
|
||||
|
||||
### ❌ Text in Dropdown Fields
|
||||
|
||||
### ❌ No Error Handling
|
||||
|
||||
### ❌ Hardcoded Values
|
||||
|
||||
## ⚠️ Sharp Edges
|
||||
|
||||
| Issue | Severity | Solution |
|
||||
|-------|----------|----------|
|
||||
| Issue | critical | # ALWAYS use dropdowns to select, don't type |
|
||||
| Issue | critical | # Prevention: |
|
||||
| Issue | high | # Understand the math: |
|
||||
| Issue | high | # When a Zap breaks after app update: |
|
||||
| Issue | high | # Immediate fix: |
|
||||
| Issue | medium | # Handle duplicates: |
|
||||
| Issue | medium | # Understand operation counting: |
|
||||
| Issue | medium | # Best practices: |
|
||||
|
||||
## Related Skills
|
||||
|
||||
Works well with: `workflow-automation`, `agent-tool-builder`, `backend`, `api-designer`
|
||||
Reference in New Issue
Block a user