Vercel Composition Patterns
supabase/supabase
React composition patterns that scale. An agent skill from supabase/supabase.
A skill your agent uses when creating a new Make scenario or editing an existing one — finding modules, connections and account-dependent values, wiring the flow, saving through scenariocreate or…
Install Make Scenario Building
$ npx skills add integromat/make-skills --skill make-scenario-building -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install integromat/make-skills make-scenario-building --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/integromat/make-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/make-scenario-building .claude/skills/make-scenario-building && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "make-scenario-building" agent skill from https://github.com/integromat/make-skills/tree/main/skills/make-scenario-building into .claude/skills/make-scenario-building/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "make-scenario-building", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/integromat/make-skills/tree/main/skills/make-scenario-buildingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add integromat/make-skills --skill make-scenario-building -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install integromat/make-skills make-scenario-building --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/integromat/make-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/make-scenario-building .agents/skills/make-scenario-building && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "make-scenario-building" agent skill from https://github.com/integromat/make-skills/tree/main/skills/make-scenario-building into .agents/skills/make-scenario-building/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "make-scenario-building", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add integromat/make-skills --skill make-scenario-building -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install integromat/make-skills make-scenario-building --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/integromat/make-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/make-scenario-building .cursor/skills/make-scenario-building && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "make-scenario-building" agent skill from https://github.com/integromat/make-skills/tree/main/skills/make-scenario-building into .cursor/skills/make-scenario-building/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "make-scenario-building", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/integromat/make-skills.git --path skills/make-scenario-building--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add integromat/make-skills --skill make-scenario-building -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install integromat/make-skills make-scenario-building --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/integromat/make-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/make-scenario-building .gemini/skills/make-scenario-building && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "make-scenario-building" agent skill from https://github.com/integromat/make-skills/tree/main/skills/make-scenario-building into .gemini/skills/make-scenario-building/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "make-scenario-building", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install integromat/make-skills make-scenario-buildingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add integromat/make-skills --skill make-scenario-building -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/integromat/make-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/make-scenario-building .github/skills/make-scenario-building && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "make-scenario-building" agent skill from https://github.com/integromat/make-skills/tree/main/skills/make-scenario-building into .github/skills/make-scenario-building/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "make-scenario-building", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add integromat/make-skills --skill make-scenario-building -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install integromat/make-skills make-scenario-building --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/integromat/make-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/make-scenario-building .opencode/skills/make-scenario-building && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "make-scenario-building" agent skill from https://github.com/integromat/make-skills/tree/main/skills/make-scenario-building into .opencode/skills/make-scenario-building/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "make-scenario-building", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
make-scenario-building- GitHub stars
- 127
- Token cost
- ~1.4k tokens
- SKILL.md length
- 700 words
- Files
- 18 (incl. references)
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when creating a new Make scenario or editing an existing one — finding modules, connections and account-dependent values, wiring the flow, saving through scenariocreate or…
- Works in 9 steps: Pin the design in words the user agrees… → environment_get → organizationId/teamId. → app_find with the user's words, once per… → …
- Creating a new Make scenario
- SKILL.md covers Build a new scenario, Edit an existing scenario, A webhook whose payload is… and Decisions the tools leave to you, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Make Scenario Building is an agent skill from integromat/make-skills. Use when creating a new Make scenario or editing an existing one — finding modules, connections and account-dependent values, wiring the flow, saving through scenariocreate or scenariopatch. Not for explaining, running or debugging a scenario, or for API-call shells.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 19 other files, including reference files (for example `examples/README.md`, `examples/ai-agent-with-tool.json` and `examples/error-handler.json`).
It sits in Development. The licence is MIT.
When your agent uses it
- Creating a new Make scenario
- Editing an existing one — finding modules
- Connections and account-dependent values
- Wiring the flow
Example prompts
- “/make-scenario-building”
Workflow steps
9 steps, taken from the first numbered list in SKILL.md.
- Pin the design in words the user agrees with: every app by name (ask when they name a category — "email",
- environment_get → organizationId/teamId.
- app_find with the user's words, once per goal. Given an instant and a polling trigger for the same
- module_spec for every planned module in one call, schemas: true — it gives each module's exact
- Connections: reuse an id from connection.existing; otherwise one connection_create for every app,
- module_field_resolve every dynamic path in dependsOn order, copying value into config. A polling
- Compose the flat list: your ids, one root: "main", everything else follows or parent, one config
- scenario_create, autoActivate off unless asked. Fix everything in errors and resubmit; relay
- Verify, then scenario_activate. On-demand: scenario_run with inputs. Polling/scheduled: activate,
What it can do on your machine
Read from SKILL.md and the folder at commit c65bccc. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Make Scenario Building loads about 1.4k tokens when it runs, and up to ~9.7k if it reads all its reference files. Until then it costs about 73 tokens; SKILL.md has 700 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from integromat/make-skills at commit c65bccc, republished under its MIT licence (© integromat). 700 words, ~1,413 tokens.
Download SKILL.mdSave it as
.claude/skills/make-scenario-building/SKILL.md (or your agent's skills folder). This skill also uses 17 other files; get the full folder from GitHub.- name
- make-scenario-building
- description
- Use when creating a new Make scenario or editing an existing one — finding modules, connections and account-dependent values, wiring the flow, saving through scenario_create or scenario_patch. Not for explaining, running or debugging a scenario, or for API-call shells.
- metadata.version
- 0.2.0
Make scenarios — creating and editing
The tool descriptions carry each tool's rules; this skill carries the order of operations and the decisions the tools cannot make. A straight-line scenario needs nothing beyond the workflow below. Load a reference only when its trigger applies.
Ground rules. A 403 means the whole connection must be re-authorized with every permission — never one
tool. A content remark on a result is an instruction, not decoration. scenario_create/scenario_patch
make one save each: put everything one change needs in one call, and read a refused write's errors as a
free dry run. Say what you resolved an ambiguous value to ("the Sales channel", "next Monday") before the
call that acts on it. Details and the refusal contract: make-scenario-reference, when something is refused.
Build a new scenario
- Pin the design in words the user agrees with: every app by name (ask when they name a category — "email", "a form", "AI"), what starts it, what moves where, what happens to non-matching items.
environment_get→organizationId/teamId.app_findwith the user's words, once per goal. Given an instant and a polling trigger for the same source, say which you chose and why.module_specfor every planned module in one call,schemas: true— it gives each module's exactconfigshape and itsdynamicpaths.- Connections: reuse an id from
connection.existing; otherwise oneconnection_createfor every app, hand over the link,connection_getwhen the user says they are done. module_field_resolveeverydynamicpath independsOnorder, copyingvalueintoconfig. A polling trigger's start point is the/datapath — ask "existing items or from now?" before resolving it. (module_options_getis the same lookup keyed bymodule_spec'sdynamicFieldsand aconnectionId; use one or the other per field, not both.)- Compose the flat list: your ids, one
root: "main", everything elsefollowsorparent, oneconfigper module,filterfor a plain continue-or-stop gate. Google Sheets, Gmail, Make AI Tools or date math involved → App gotchas first. scenario_create,autoActivateoff unless asked. Fix everything inerrorsand resubmit; relaywarnings.- Verify, then
scenario_activate. On-demand:scenario_runwithinputs. Polling/scheduled: activate,scenario_run,scenario_execution_get. Webhook: the user sends one real request —scenario_rundoes not exercise a webhook. Then givehttps://<zone>.make.com/<teamId>/scenarios/<scenarioId>.
Show full SKILL.md (329 more words)Show less
Edit an existing scenario
scenario_getfor structure andlastEdit;scenario_module_getonly for the modules you will change.- Adding modules:
app_findandmodule_spec(schemas: true)as above; resolvedynamicpaths against the module's currentconfig. - One
scenario_patchwithexpectedLastEditand every operation the change needs. Send only theconfigdomains you changed. Fix every{{<id>.field}}reference a removed or moved module leaves dangling in the same call. - A module added in a call gets its id on save, so wiring onto it is a second call with the returned
lastEdit. Verify from the response'smodulesecho.
A webhook whose payload is unknown
payloadShape: "learned" in module_spec, or a bare gateway:CustomWebHook: create with the trigger alone →
the user sends one real request (or scenario_trigger_learn first) → scenario_trigger_inspect →
scenario_patch the rest. Do not activate a webhook scenario whose fields nobody has seen.
Decisions the tools leave to you
- Filter vs if-else vs router. Skip non-matching items and nothing else →
filter. Non-matching items need their own action →builtin:BasicIfElse(+builtin:BasicMergeto rejoin). Several arms that may all fire →builtin:BasicRouter. - Do not over-build. No error handlers, aggregators or variables unless the design needs them.
References — load only on the trigger
| Trigger | Reference |
|---|---|
| Mapping a trigger's or on-demand input, a whole bundle or an array element; a mapped field came back empty | Mapping |
| A value must be transformed (dates, text, arrays, conditionals) | IML functions |
| More than a straight line: routers, if-else + merge, multi-condition filters, iterating, aggregating | Flow control |
| The scenario is on-demand, calls another scenario, or is called by one or by an agent | Subscenarios |
| Placing a Make AI Agent module with tools | AI agents |
| A run must remember earlier runs (dedup, counters), or a payload needs a fixed schema | Data stores |
| The user asks for retries or fallbacks, or failure/data loss is unacceptable — most scenarios need none | Error handling |
| Finalizing a Google Sheets, Gmail or Make AI Tools config, or a date expression | App gotchas |
A complete scenario_create call to pattern from | Examples |
© integromat, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 17 other files (references) in skills/make-scenario-building of integromat/make-skills.
- SKILL.md
- examples/README.md
- examples/ai-agent-with-tool.json
- examples/error-handler.json
- examples/if-else-merge.json
- examples/iterator-aggregator.json
- examples/on-demand-subscenario.json
- examples/polling-sheets-ai-update-row.json
- examples/router-fanout.json
- examples/webhook-to-google-sheets.json
- references/ai-agents.md
- references/app-gotchas.md
- references/data-stores.md
- references/error-handling.md
- references/flow-control.md
- references/iml-functions.md
- references/mapping.md
- references/subscenarios.md
Open the folder on GitHubat commit c65bccc
Compare with similar skills
Make Scenario Building next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Make Scenario Building this skillintegromat/make-skills | 127 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Vercel Composition Patternssupabase/supabase | 111k | 59 repos | ~726 | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 296k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Typescript Advanced Typesrolling-scopes/rsschool-app | 10k | 25 repos | ~4.2k | Automated safety check: Pass | MPL-2.0 | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 5 repos | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Typescript Advanced Types
rolling-scopes/rsschool-app
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
More from integromat/make-skills
Make Scenario Explore
integromat/make-skills
A skill your agent uses when orienting in a Make account — listing organizations, teams and scenarios, explaining what an existing scenario does, checking connection health, auditing several…
Make Scenario Operations
integromat/make-skills
A skill your agent uses when running a scenario, switching it on or off, reviewing or debugging executions, or investigating a webhook that receives nothing.
Make Scenario Reference
integromat/make-skills
Load when a Make scenario tool answers 403, refuses a write for a reason you cannot explain, or no tool seems to cover the request — the shared conventions of environmentget, scenario, appfind…
Related
Categories
Questions about Make Scenario Building
What does Make Scenario Building do?
A skill your agent uses when creating a new Make scenario or editing an existing one — finding modules, connections and account-dependent values, wiring the flow, saving through scenariocreate or…. Make Scenario Building is an agent skill from integromat/make-skills. Use when creating a new Make scenario or editing an existing one — finding modules, connections and account-dependent values, wiring the flow, saving through scenariocreate or scenariopatch.
When should I use Make Scenario Building?
Make Scenario Building fits situations like: creating a new Make scenario; editing an existing one — finding modules; connections and account-dependent values; wiring the flow.
How do I install Make Scenario Building in Claude Code?
Run `npx skills add integromat/make-skills --skill make-scenario-building -a claude-code`. Or copy the skill folder (skills/make-scenario-building in integromat/make-skills) into .claude/skills/make-scenario-building in your project. Claude Code loads it when a task matches its description.
How do I install Make Scenario Building in Codex?
Run `npx skills add integromat/make-skills --skill make-scenario-building -a codex`. Or copy the skill folder (skills/make-scenario-building in integromat/make-skills) into .agents/skills/make-scenario-building in your project. Codex loads it when a task matches its description.
Can I use Make Scenario Building in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add integromat/make-skills --skill make-scenario-building -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/make-scenario-building, .gemini/skills/make-scenario-building, .github/skills/make-scenario-building and .opencode/skills/make-scenario-building in your project.
What does Make Scenario Building need to run?
SKILL.md names no scripts, command-line tools or credentials: Make Scenario Building is instructions for the agent only.
Does Make Scenario Building access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Make Scenario Building safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Make Scenario Building use?
Make Scenario Building is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Make Scenario Building use?
About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 8.2k tokens, read only when the agent opens those files.
What are the alternatives to Make Scenario Building?
Skills that share tags, products or a category with Make Scenario Building: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 296k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Make Scenario Building?
integromat (a GitHub organization) maintains it in integromat/make-skills, which has 127 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 7, 2026.
Source: integromat/make-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.