Vercel Composition Patterns
supabase/supabase
React composition patterns that scale. An agent skill from supabase/supabase.
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…
Install Make Scenario Explore
$ npx skills add integromat/make-skills --skill make-scenario-explore -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install integromat/make-skills make-scenario-explore --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-explore .claude/skills/make-scenario-explore && 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-explore" agent skill from https://github.com/integromat/make-skills/tree/main/skills/make-scenario-explore into .claude/skills/make-scenario-explore/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "make-scenario-explore", 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-exploreType 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-explore -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install integromat/make-skills make-scenario-explore --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-explore .agents/skills/make-scenario-explore && 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-explore" agent skill from https://github.com/integromat/make-skills/tree/main/skills/make-scenario-explore into .agents/skills/make-scenario-explore/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "make-scenario-explore", 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-explore -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install integromat/make-skills make-scenario-explore --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-explore .cursor/skills/make-scenario-explore && 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-explore" agent skill from https://github.com/integromat/make-skills/tree/main/skills/make-scenario-explore into .cursor/skills/make-scenario-explore/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "make-scenario-explore", 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-explore--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-explore -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install integromat/make-skills make-scenario-explore --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-explore .gemini/skills/make-scenario-explore && 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-explore" agent skill from https://github.com/integromat/make-skills/tree/main/skills/make-scenario-explore into .gemini/skills/make-scenario-explore/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "make-scenario-explore", 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-exploreInstalls 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-explore -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-explore .github/skills/make-scenario-explore && 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-explore" agent skill from https://github.com/integromat/make-skills/tree/main/skills/make-scenario-explore into .github/skills/make-scenario-explore/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "make-scenario-explore", 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-explore -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-explore --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-explore .opencode/skills/make-scenario-explore && 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-explore" agent skill from https://github.com/integromat/make-skills/tree/main/skills/make-scenario-explore into .opencode/skills/make-scenario-explore/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "make-scenario-explore", 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-explore- GitHub stars
- 127
- Token cost
- ~1.1k tokens
- SKILL.md length
- 560 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- MIT
At a glance
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…
- Orienting in a Make account — listing organizations
- SKILL.md covers Start with environment_get, Finding a scenario, Explaining one scenario and Account-wide health checks, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Teams and scenarios
What it does
Make Scenario Explore is an agent skill from integromat/make-skills. Use when orienting in a Make account — listing organizations, teams and scenarios, explaining what an existing scenario does, checking connection health, auditing several scenarios. Not for creating, editing, running or debugging.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. The licence is MIT.
When your agent uses it
- Orienting in a Make account — listing organizations
- Teams and scenarios
- Explaining what an existing scenario does
- Checking connection health
Example prompts
- “/make-scenario-explore”
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 Explore loads about 1.1k tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 560 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). 560 words, ~1,080 tokens.
Download SKILL.mdSave it as
.claude/skills/make-scenario-explore/SKILL.md (or your agent's skills folder).- name
- make-scenario-explore
- description
- Use when orienting in a Make account — listing organizations, teams and scenarios, explaining what an existing scenario does, checking connection health, auditing several scenarios. Not for creating, editing, running or debugging.
- metadata.version
- 0.2.0
Make scenarios — orienting and explaining
The read-only path from "what does this account have" to "explain this scenario" — the entry point of almost every conversation, and the tool of choice for a non-technical question about an automation.
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. Say what you resolved an ambiguous
value to before the call that acts on it. The refusal contract and the rest: make-scenario-reference, when
something is refused or no tool seems to fit.
Start with environment_get
Always first, no arguments: every organization and team the connection reaches, including private spaces,
and the zone needed for https://<zone>.make.com/<teamId>/scenarios/<id> links. An organization-bound
connection sees one organization and a remark counts the rest — mention that only if the user expects
something that is not there.
Finding a scenario
scenario_list returns at most 25, most recently edited first. Omitting status returns every status — it
is not a hidden "active only" filter. Its trigger is coarse (instant/scheduled/on-demand); the
webhook-vs-polling distinction lives in scenario_get. Narrow by name, folder or status rather than paging.
scenario_folder_list only when the user refers to a folder. scenario_list_show only when they ask to see
the list rendered.
Explaining one scenario
scenario_get is enough by itself: every module in flow order, nesting via parent (router arms,
if-else branches, error handlers, agent tools), filters, trigger and schedule, connection health, declared
inputs and outputs. It omits each module's config on purpose — do not read that as incomplete, and do not
fan scenario_module_get across every module. Call scenario_module_get only when a specific value is the
question: which spreadsheet, what the message says, how a field is computed.
How to read a few fields for a non-technical user:
trigger.kinddecides what "make it run" means:webhook→ give a URL to post to;polling/scheduled→ it runs on its schedule;on-demand→ run it directly, the only kind that returns outputs.connections[].status: "missing"covers both deleted and broken — the fix is the same, reconnect the app in Make — and it is the most common reason a scenario "stopped working". No other tool surfaces it.isWaitingOnIncompleteExecutionsmeans the scenario runs sequentially and is frozen behind stored failed runs: no new data flows until those are resolved in Make (this surface cannot). Different from a non-zeroincompleteExecutionsalone, which is informational on a non-sequential scenario.status: "error"carries no reason — Make records none. The cause is in the run history (make-scenario-operations), never in a guess.modules[].issuesare Make's own complaints about a module ("not set up") — usually the direct answer to "why won't it activate".
Show full SKILL.md (122 more words)Show less
Scenario ids come from scenario_list or from a create/patch response; scenario_get and
scenario_module_get take no teamId.
Account-wide health checks
scenario_list's status and incompleteExecutions are a cheap first pass, not the answer: status only
turns error after Make deactivates a scenario for repeated failures, so a scenario that started failing
yesterday still reads active. A structural read says nothing about whether recent runs succeeded. For a
real answer, call scenario_execution_list (narrowed to status: "error") for every scenario in scope, then
scenario_get on the ones that turn up failures for connection health and issues. With more scenarios than
the 25-row cap, narrow by folder or status and say the sweep is partial.
Not covered here
- Running, activating, or debugging —
make-scenario-operations. - Creating or editing —
make-scenario-building.
© 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
Just SKILL.md in skills/make-scenario-explore of integromat/make-skills.
Open the folder on GitHubat commit c65bccc
Compare with similar skills
Make Scenario Explore 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 Explore this skillintegromat/make-skills | 127 | — | ~1.1k | 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 Building
integromat/make-skills
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 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 Explore
What does Make Scenario Explore do?
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 Explore is an agent skill from integromat/make-skills. Use when orienting in a Make account — listing organizations, teams and scenarios, explaining what an existing scenario does, checking connection health, auditing several scenarios.
When should I use Make Scenario Explore?
Make Scenario Explore fits situations like: orienting in a Make account — listing organizations; teams and scenarios; explaining what an existing scenario does; checking connection health.
How do I install Make Scenario Explore in Claude Code?
Run `npx skills add integromat/make-skills --skill make-scenario-explore -a claude-code`. Or copy the skill folder (skills/make-scenario-explore in integromat/make-skills) into .claude/skills/make-scenario-explore in your project. Claude Code loads it when a task matches its description.
How do I install Make Scenario Explore in Codex?
Run `npx skills add integromat/make-skills --skill make-scenario-explore -a codex`. Or copy the skill folder (skills/make-scenario-explore in integromat/make-skills) into .agents/skills/make-scenario-explore in your project. Codex loads it when a task matches its description.
Can I use Make Scenario Explore 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-explore -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-explore, .gemini/skills/make-scenario-explore, .github/skills/make-scenario-explore and .opencode/skills/make-scenario-explore in your project.
What does Make Scenario Explore need to run?
SKILL.md names no scripts, command-line tools or credentials: Make Scenario Explore is instructions for the agent only.
Does Make Scenario Explore 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 Explore 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 Explore use?
Make Scenario Explore 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 Explore use?
About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Make Scenario Explore?
Skills that share tags, products or a category with Make Scenario Explore: 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 Explore?
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.