Studio
remotion-dev/remotion
Start Remotion Studio from packages/example and open it in the Codex browser.
Define, generate, inspect, and troubleshoot SMARTS scenarios from supported maps, traffic, missions, social agents, bubbles, surface patches, traffic histories, and metadata.
$ npx skills add VectorSpaceLab/AREX-Skill --skill scenario-studio -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install VectorSpaceLab/AREX-Skill scenario-studio --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/VectorSpaceLab/AREX-Skill.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/repositories/repo-skills/smarts/sub-skills/scenario-studio .claude/skills/scenario-studio && 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 "scenario-studio" agent skill from https://github.com/VectorSpaceLab/AREX-Skill/tree/main/skills/repositories/repo-skills/smarts/sub-skills/scenario-studio into .claude/skills/scenario-studio/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scenario-studio", 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/VectorSpaceLab/AREX-Skill/tree/main/skills/repositories/repo-skills/smarts/sub-skills/scenario-studioType 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 VectorSpaceLab/AREX-Skill --skill scenario-studio -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install VectorSpaceLab/AREX-Skill scenario-studio --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/VectorSpaceLab/AREX-Skill.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/repositories/repo-skills/smarts/sub-skills/scenario-studio .agents/skills/scenario-studio && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "scenario-studio" agent skill from https://github.com/VectorSpaceLab/AREX-Skill/tree/main/skills/repositories/repo-skills/smarts/sub-skills/scenario-studio into .agents/skills/scenario-studio/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scenario-studio", 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 VectorSpaceLab/AREX-Skill --skill scenario-studio -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install VectorSpaceLab/AREX-Skill scenario-studio --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/VectorSpaceLab/AREX-Skill.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/repositories/repo-skills/smarts/sub-skills/scenario-studio .cursor/skills/scenario-studio && 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 "scenario-studio" agent skill from https://github.com/VectorSpaceLab/AREX-Skill/tree/main/skills/repositories/repo-skills/smarts/sub-skills/scenario-studio into .cursor/skills/scenario-studio/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scenario-studio", 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/VectorSpaceLab/AREX-Skill.git --path skills/repositories/repo-skills/smarts/sub-skills/scenario-studio--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 VectorSpaceLab/AREX-Skill --skill scenario-studio -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install VectorSpaceLab/AREX-Skill scenario-studio --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/VectorSpaceLab/AREX-Skill.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/repositories/repo-skills/smarts/sub-skills/scenario-studio .gemini/skills/scenario-studio && 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 "scenario-studio" agent skill from https://github.com/VectorSpaceLab/AREX-Skill/tree/main/skills/repositories/repo-skills/smarts/sub-skills/scenario-studio into .gemini/skills/scenario-studio/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scenario-studio", 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 VectorSpaceLab/AREX-Skill scenario-studioInstalls 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 VectorSpaceLab/AREX-Skill --skill scenario-studio -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/VectorSpaceLab/AREX-Skill.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/repositories/repo-skills/smarts/sub-skills/scenario-studio .github/skills/scenario-studio && 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 "scenario-studio" agent skill from https://github.com/VectorSpaceLab/AREX-Skill/tree/main/skills/repositories/repo-skills/smarts/sub-skills/scenario-studio into .github/skills/scenario-studio/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scenario-studio", 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 VectorSpaceLab/AREX-Skill --skill scenario-studio -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install VectorSpaceLab/AREX-Skill scenario-studio --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/VectorSpaceLab/AREX-Skill.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/repositories/repo-skills/smarts/sub-skills/scenario-studio .opencode/skills/scenario-studio && 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 "scenario-studio" agent skill from https://github.com/VectorSpaceLab/AREX-Skill/tree/main/skills/repositories/repo-skills/smarts/sub-skills/scenario-studio into .opencode/skills/scenario-studio/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scenario-studio", 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.
scenario-studioDefine, generate, inspect, and troubleshoot SMARTS scenarios from supported maps, traffic, missions, social agents, bubbles, surface patches, traffic histories, and metadata.
Scenario Studio is an agent skill from VectorSpaceLab/AREX-Skill. Define, generate, inspect, and troubleshoot SMARTS scenarios from supported maps, traffic, missions, social agents, bubbles, surface patches, traffic histories, and metadata. Use this route when the task is scenario DSL or generated scenario layout; route live SUMO/TraCI, Envision replay, or environment lifecycle elsewhere.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including scripts and reference files (for example `references/api-reference.md`, `references/data-formats.md` and `references/maps-and-traffic.md`).
The repository describes itself as: A Skill Library for Automated Machine Learning. The licence is MIT.
6 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit ac3fe1a. It shows what the files ask for, not the result of running them.
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.
Ships 2 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
pythonFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Scenario Studio loads about 1.5k tokens when it runs, and up to ~8.8k if it reads all its reference files. Until then it costs about 85 tokens; SKILL.md has 579 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.
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); the scripts in this folder are not scanned.
The full file from VectorSpaceLab/AREX-Skill at commit ac3fe1a, republished under its MIT licence (© VectorSpaceLab). 579 words, ~1,538 tokens.
.claude/skills/scenario-studio/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.Use this route when you need a self-contained SMARTS scenario definition or
need to explain why generated scenario artifacts are missing or incompatible.
The runtime DSL is smarts.sstudio.types (smarts.sstudio.sstypes is the
implementation module) and the high-level entry point is
smarts.sstudio.genscenario.gen_scenario(scenario, output_dir, seed=42).
Scenario from smarts.sstudio.types for the authoring DSL. It combines
map_spec, named traffic, ego_missions, social_agent_missions,
bubbles, friction_maps, traffic_histories, and scenario_metadata.smarts.core.scenario.Scenario only after generation, when
SMARTS discovers a map and build/ assets. It is not the authoring dataclass.scripts/validate_scenario_layout.py for a read-only layout check and
scripts/generate_minimal_scenario.py for a bounded local fixture. Both take
explicit paths and never start SUMO, TraCI, Envision, or a network download.scl scenario build, scl scenario clean, SUMO/TraCI, Waymo/Argoverse
conversion, and other system integrations to cli-integrations.simulation-environments.
Route Envision replay and rendered sensors to sensors-visualization.Read the linked references before authoring a nontrivial scenario:
scenario.py in
it. Keep input maps and data paths explicit; do not depend on the current
working directory.map.net.xml/another .net.xml for SUMO, map.xodr
for OpenDRIVE, a Waymo .tfrecord source, an Argoverse map archive, or a
MapSpec(source=..., builder_fn=...) for a custom RoadMap implementation.gen_scenario(..., output_dir=scenario_dir, seed=<integer>). Set the
same seed for comparable generated output; seed random choices before the
call as well when authoring code uses Python or NumPy randomness.build/ tree. Build assets are
generated state, not source code; regenerate after changing the DSL or map.from pathlib import Path
from smarts.sstudio import gen_scenario, types as t
root = Path("my_scenario").resolve()
car = t.TrafficActor(name="car")
scenario = t.Scenario(
map_spec=t.MapSpec(source=str(root / "map.net.xml")),
traffic={"background": t.Traffic(
engine="SUMO",
flows=[t.Flow(
route=t.Route(begin=("edge_in", 0, "random"),
end=("edge_out", 0, "max")),
rate=60, begin=0, end=60, actors={car: 1.0},
)]
)},
ego_missions=[t.Mission(t.Route(
begin=("edge_in", 1, 10), end=("edge_out", 1, "max")
))],
)
gen_scenario(scenario, root, seed=42)SUMO traffic requires a SUMO road network and the SUMO Python/runtime
integration; use engine="SMARTS" for supported non-SUMO road maps. The recipe
is a shape example: replace edge ids with ids from the selected map and install
optional dependencies before claiming a successful build.
A successful generation normally creates build/build.db, a map artifact under
build/map/, route files under build/traffic/, and optional files for
missions, social agents, bubbles, friction, histories, and metadata. The exact
set is determined by non-empty Scenario fields; see the data-format reference.
smarts.core.scenario.Scenario.is_valid_scenario() checks that a map can be
built, not that every optional artifact or traffic combination is semantically
safe. Missing build/map/map.glb, stale build.db, or absent route files means
regenerate/build rather than edit generated pickle/XML files manually.
Run the validator from any cwd:
python /path/to/skills/disco/smarts/sub-skills/scenario-studio/scripts/validate_scenario_layout.py \
--scenario /absolute/path/to/my_scenario --require-buildFor a safe local fixture (OpenDRIVE is used only when the installed optional parser can load the supplied map), write to an explicit empty output directory:
python /path/to/skills/disco/smarts/sub-skills/scenario-studio/scripts/generate_minimal_scenario.py \
--map /absolute/path/to/map.net.xml --output /absolute/path/to/out --seed 42The helper refuses to overwrite non-empty output unless --force is supplied,
uses no external service, and exits nonzero with the failing path or import
reason. Treat missing SUMO, Waymo, Argoverse, or dataset packages as explicit
integration gaps, not as evidence that core Scenario Studio is broken.
© VectorSpaceLab, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 7 other files (scripts, references) in skills/repositories/repo-skills/smarts/sub-skills/scenario-studio of VectorSpaceLab/AREX-Skill.
Open the folder on GitHubat commit ac3fe1a
Scenario Studio 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 |
|---|---|---|---|---|---|---|
| Scenario Studio this skillVectorSpaceLab/AREX-Skill | 330 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Studioremotion-dev/remotion | 63k | — | ~376 | Automated safety check: Pass | Custom licence | |
| Node Inspect Debuggeropenclaw/openclaw | 392k | 1 repos | ~894 | Automated safety check: Pass | MIT | |
| Studio Error Handlingsupabase/supabase | 111k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Studio Queriessupabase/supabase | 111k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Scenario Caption Studioscenario-labs/skills | 931 | — | ~3.2k | Automated safety check: Pass | MIT |
remotion-dev/remotion
Start Remotion Studio from packages/example and open it in the Codex browser.
openclaw/openclaw
Debug Node.js with node inspect, --inspect, breakpoints, CDP, heap, and CPU profiles.
supabase/supabase
Error display and troubleshooting pattern for Supabase Studio.
supabase/supabase
React Query conventions for data fetching in Supabase Studio.
scenario-labs/skills
A skill your agent uses when a video needs its spoken words on screen through Scenario via MCP: burned-in styled captions for a TikTok, Reels, or Shorts cut, ad captions for sound-off feeds, YouTube…
supabase/supabase
Testing strategy for Supabase Studio. An agent skill from supabase/supabase.
VectorSpaceLab/AREX-Skill
Use this repo skill for Agent Lightning package tasks: authoring trainable agents, tracing rewards and spans, running LightningStore/Trainer loops, using agl CLI services, choosing examples, and…
VectorSpaceLab/AREX-Skill
A skill your agent uses when configuring LiteLLM for MCP tools, A2A agents, Claude Code/Cursor agent gateway traffic, MCP auth/OAuth, tool permissions, semantic filtering, or agent-specific proxy…
VectorSpaceLab/AREX-Skill
Build and debug DB-GPT agents, tools, skills, teams, and AWEL workflows, including deterministic local DAG runs and HTTP-trigger topology without assuming an LLM, credential, or external service.
VectorSpaceLab/AREX-Skill
Work on the actively maintained LangChain v1 agent package: initchatmodel, createagent, structured output, tools, middleware, embeddings initialization, provider routing, and agent runtime…
VectorSpaceLab/AREX-Skill
A skill your agent uses for giskard.agents async chat workflows, tools, prompt templates, structured outputs, retries, rate limiting, embeddings, and optional LiteLLM backend.
VectorSpaceLab/AREX-Skill
A skill your agent uses for AlphaFold 3 input preparation, prediction command planning, output interpretation, and Python API inspection.
Define, generate, inspect, and troubleshoot SMARTS scenarios from supported maps, traffic, missions, social agents, bubbles, surface patches, traffic histories, and metadata. Scenario Studio is an agent skill from VectorSpaceLab/AREX-Skill. Define, generate, inspect, and troubleshoot SMARTS scenarios from supported maps, traffic, missions, social agents, bubbles, surface patches, traffic histories, and metadata.
Run `npx skills add VectorSpaceLab/AREX-Skill --skill scenario-studio -a claude-code`. Or copy the skill folder (skills/repositories/repo-skills/smarts/sub-skills/scenario-studio in VectorSpaceLab/AREX-Skill) into .claude/skills/scenario-studio in your project. Claude Code loads it when a task matches its description.
Run `npx skills add VectorSpaceLab/AREX-Skill --skill scenario-studio -a codex`. Or copy the skill folder (skills/repositories/repo-skills/smarts/sub-skills/scenario-studio in VectorSpaceLab/AREX-Skill) into .agents/skills/scenario-studio in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add VectorSpaceLab/AREX-Skill --skill scenario-studio -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/scenario-studio, .gemini/skills/scenario-studio, .github/skills/scenario-studio and .opencode/skills/scenario-studio in your project.
Going by SKILL.md and its folder, Scenario Studio needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.
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.
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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Scenario Studio is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.5k tokens (SKILL.md is roughly 6.2k 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 7.3k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Scenario Studio: Studio (remotion-dev/remotion, 63k stars), Node Inspect Debugger (openclaw/openclaw, 392k stars), Studio Error Handling (supabase/supabase, 111k stars) and Studio Queries (supabase/supabase, 111k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
VectorSpaceLab (a GitHub organization) maintains it in VectorSpaceLab/AREX-Skill, which has 330 GitHub stars. The repository holds 159 skills in this directory. The repository was last updated on September 3, 2026.
Source: VectorSpaceLab/AREX-Skill on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.