Retellai Common Errors
jeremylongshore/tons-of-skills-marketplace
Diagnose and fix Retell AI voice agent errors: call failures, webhook issues, voice quality.
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.
Install Make Scenario Operations
$ npx skills add integromat/make-skills --skill make-scenario-operations -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install integromat/make-skills make-scenario-operations --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-operations .claude/skills/make-scenario-operations && 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-operations" agent skill from https://github.com/integromat/make-skills/tree/main/skills/make-scenario-operations into .claude/skills/make-scenario-operations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "make-scenario-operations", 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-operationsType 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-operations -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install integromat/make-skills make-scenario-operations --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-operations .agents/skills/make-scenario-operations && 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-operations" agent skill from https://github.com/integromat/make-skills/tree/main/skills/make-scenario-operations into .agents/skills/make-scenario-operations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "make-scenario-operations", 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-operations -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install integromat/make-skills make-scenario-operations --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-operations .cursor/skills/make-scenario-operations && 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-operations" agent skill from https://github.com/integromat/make-skills/tree/main/skills/make-scenario-operations into .cursor/skills/make-scenario-operations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "make-scenario-operations", 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-operations--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-operations -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install integromat/make-skills make-scenario-operations --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-operations .gemini/skills/make-scenario-operations && 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-operations" agent skill from https://github.com/integromat/make-skills/tree/main/skills/make-scenario-operations into .gemini/skills/make-scenario-operations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "make-scenario-operations", 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-operationsInstalls 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-operations -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-operations .github/skills/make-scenario-operations && 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-operations" agent skill from https://github.com/integromat/make-skills/tree/main/skills/make-scenario-operations into .github/skills/make-scenario-operations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "make-scenario-operations", 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-operations -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-operations --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-operations .opencode/skills/make-scenario-operations && 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-operations" agent skill from https://github.com/integromat/make-skills/tree/main/skills/make-scenario-operations into .opencode/skills/make-scenario-operations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "make-scenario-operations", 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-operations- GitHub stars
- 127
- Token cost
- ~1.2k tokens
- SKILL.md length
- 661 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- MIT
At a glance
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.
- Works in 3 steps: scenario_execution_inspect — overall… → scenario_execution_module_get on the… → Cross-check the current config with…
- Running a scenario
- SKILL.md covers Running: scenario_run, Activating and deactivating, History:… and Debugging a failed run:…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Make Scenario Operations is an agent skill from integromat/make-skills. Use when running a scenario, switching it on or off, reviewing or debugging executions, or investigating a webhook that receives nothing. Not for creating, editing or explaining a scenario.
Its SKILL.md is about 1.2k 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 Backend & APIs, covering Webhooks and Debugging. The licence is MIT.
When your agent uses it
- Running a scenario
- Switching it on
- Debugging executions
- Investigating a webhook that receives nothing
Example prompts
- “/make-scenario-operations”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- scenario_execution_inspect — overall status and error, plus every module that ran with invocation and
- scenario_execution_module_get on the suspect module and the cycle inspect reported (usually 1) —
- Cross-check the current config with scenario_module_get — but first compare scenario_get's lastEdit
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 Operations loads about 1.2k tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 661 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). 661 words, ~1,227 tokens.
Download SKILL.mdSave it as
.claude/skills/make-scenario-operations/SKILL.md (or your agent's skills folder).- name
- make-scenario-operations
- description
- Use when running a scenario, switching it on or off, reviewing or debugging executions, or investigating a webhook that receives nothing. Not for creating, editing or explaining a scenario.
- metadata.version
- 0.2.0
Make scenarios — running and debugging
Everything after a scenario exists: running it, switching it on or off, and the run → inspect → drill-down
chain for a failure. Know trigger.kind (from scenario_get) before calling scenario_run — its behavior
depends on it entirely.
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.
Running: scenario_run
- on-demand — runs with
inputskeyed by the declared input names and returns the declared outputs. - polling / scheduled — runs once now;
inputsare rejected, nothing is returned, the run lands in history. - webhook — nothing runs. The response hands back the webhook URL (or names the app event). Do not
report the scenario as "run"; have the user send a real request and check
scenario_execution_list.
An inactive scenario refuses with a pointer to scenario_activate — new scenarios start inactive. A
"pending" status means the run outlived the wait: check scenario_execution_get with the executionId, do
not assume failure. A rejected inputs key comes back naming the declared interface — read it rather than
guessing again. Inputs passed to a scenario with no interface are silently unused; a remark says so — relay it.
Activating and deactivating
Two separate tools, and an already-satisfied request is success, not an error. An activation refusal almost
always means a module still has a configuration error — scenario_get's per-module issues say which.
History: scenario_execution_list → scenario_execution_get
The list carries errorMessage inline for failed runs — often enough for "did it work, why not" without a
second call. A run started moments ago can lag the list by a few seconds (a remark says so; not data loss).
scenario_execution_get is for one run's outcome, outputs and consumption (credits and bytes — usage units,
not money); it has no per-module breakdown, so it answers "did it finish", not "which module broke". The
_show twins only when the user wants a rendered timeline or card.
Show full SKILL.md (313 more words)Show less
Debugging a failed run: scenario_execution_inspect → scenario_execution_module_get
scenario_execution_inspect— overall status and error, plus every module that ran with invocation and error counts. Make records one error per run (the one that ended it); other failures show only aserrorCyclescounts. A warning run has no top-levelerrorat all —modules[].errorsis the only signal, so never report "no error found" as "nothing went wrong".scenario_execution_module_geton the suspect module and thecycleinspectreported (usually 1) — the real input and output that module saw. Never pick a cycle independently; a wrong cycle returns unrelated data with no warning.- Cross-check the current
configwithscenario_module_get— but first comparescenario_get'slastEditto the run'sstartedAt. If the scenario was edited after the run, what you read is not necessarily what ran; say so before attributing the bug.
…[truncated] marks a cut payload — text, not JSON to parse. A module with no downstream consumer
(ReturnData, WebhookRespond, a throw) always reports an empty output here even when correct; the scenario's
own output lives in scenario_execution_get's outputs.
A webhook that "isn't receiving data"
scenario_trigger_inspectfirst: it reportsqueueddeliveries — requests stored and waiting because the scenario is inactive, paused, or rate-limited. A non-zeroqueued.countis the answer to "I sent data and nothing happened" far more often than a broken mapping. It also shows the detected structure and recent deliveries, and with adeliveryIdone raw request.scenario_trigger_learnputs the webhook into learning mode: the next request is captured as the structure without running the scenario (safe on an active scenario). Give the user the URL and have them send one real request.
Withheld payloads (confidential or shared webhooks, bodies over 1 MB, binary) are replaced by a placeholder and explained in a remark — not "nothing arrived".
Not covered here
- Editing the scenario to fix what you found —
make-scenario-building. - Explaining the scenario without running it —
make-scenario-explore.
© 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-operations of integromat/make-skills.
Open the folder on GitHubat commit c65bccc
Compare with similar skills
Make Scenario Operations 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 Operations this skillintegromat/make-skills | 127 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Retellai Common Errorsjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~881 | Automated safety check: Pass | MIT | |
| Tg Bot Opsserejaris/personal-corp-os | 229 | — | ~1.6k | Automated safety check: Notes | MIT | |
| Lindy Common Errorsjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Clay Common Errorsjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~2k | Automated safety check: Pass | MIT | |
| Shopify DebuggingMicrock/ordinary-claude-skills | 403 | — | ~3.8k | Automated safety check: Pass | Custom licence |
Similar skills
Tg Bot Ops
serejaris/personal-corp-os
A skill your agent uses when operating, debugging, deploying, or monitoring a Telegram bot or Telegram-to-agent gateway.
Lindy Common Errors
jeremylongshore/tons-of-skills-marketplace
Troubleshoot common Lindy AI agent errors and workflow failures.
Clay Common Errors
jeremylongshore/tons-of-skills-marketplace
Diagnose and fix the most common Clay errors and integration issues.
Shopify Debugging
Microck/ordinary-claude-skills
Complete debugging and troubleshooting guide for Shopify including Liquid errors, theme preview debugging, API error handling, JavaScript console debugging, network request inspection, cart issues…
PR Review Provider
yansongda/pay
A skill your agent uses when reviewing PRs that add or modify a payment Provider in yansongda/pay - covers plugin pipeline, multi-tenant safety, signature verification, docs, and naming conventions.
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 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 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 Operations
What does Make Scenario Operations do?
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 Operations is an agent skill from integromat/make-skills. Use when running a scenario, switching it on or off, reviewing or debugging executions, or investigating a webhook that receives nothing.
When should I use Make Scenario Operations?
Make Scenario Operations fits situations like: running a scenario; switching it on; debugging executions; investigating a webhook that receives nothing.
How do I install Make Scenario Operations in Claude Code?
Run `npx skills add integromat/make-skills --skill make-scenario-operations -a claude-code`. Or copy the skill folder (skills/make-scenario-operations in integromat/make-skills) into .claude/skills/make-scenario-operations in your project. Claude Code loads it when a task matches its description.
How do I install Make Scenario Operations in Codex?
Run `npx skills add integromat/make-skills --skill make-scenario-operations -a codex`. Or copy the skill folder (skills/make-scenario-operations in integromat/make-skills) into .agents/skills/make-scenario-operations in your project. Codex loads it when a task matches its description.
Can I use Make Scenario Operations 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-operations -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-operations, .gemini/skills/make-scenario-operations, .github/skills/make-scenario-operations and .opencode/skills/make-scenario-operations in your project.
What does Make Scenario Operations need to run?
SKILL.md names no scripts, command-line tools or credentials: Make Scenario Operations is instructions for the agent only.
Does Make Scenario Operations 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 Operations 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 Operations use?
Make Scenario Operations 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 Operations use?
About 1.2k tokens (SKILL.md is roughly 4.9k 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 Operations?
Skills that share tags, products or a category with Make Scenario Operations: Retellai Common Errors (jeremylongshore/tons-of-skills-marketplace, 2.8k stars), Tg Bot Ops (serejaris/personal-corp-os, 229 stars), Lindy Common Errors (jeremylongshore/tons-of-skills-marketplace, 2.8k stars) and Clay Common Errors (jeremylongshore/tons-of-skills-marketplace, 2.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Make Scenario Operations?
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.