Agent skill

Launch Scene

Launch a geniesimbringup scene against a chosen physics + render backend, using ros2 launch geniesimbringup app.launch.py.

MPL-2.0Auto-check passed

Install Launch Scene

skills CLI

$ npx skills add AgibotTech/genie_sim --skill launch-scene -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install AgibotTech/genie_sim launch-scene --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/AgibotTech/genie_sim.git skills-src && mkdir -p .claude/skills && cp -r skills-src/source/geniesim_ros/skills/launch-scene .claude/skills/launch-scene && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "launch-scene" agent skill from https://github.com/AgibotTech/genie_sim/tree/main/source/geniesim_ros/skills/launch-scene into .claude/skills/launch-scene/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-scene", 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

$skill-installer install https://github.com/AgibotTech/genie_sim/tree/main/source/geniesim_ros/skills/launch-scene

Type 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.

skills CLI

$ npx skills add AgibotTech/genie_sim --skill launch-scene -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install AgibotTech/genie_sim launch-scene --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/AgibotTech/genie_sim.git skills-src && mkdir -p .agents/skills && cp -r skills-src/source/geniesim_ros/skills/launch-scene .agents/skills/launch-scene && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "launch-scene" agent skill from https://github.com/AgibotTech/genie_sim/tree/main/source/geniesim_ros/skills/launch-scene into .agents/skills/launch-scene/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-scene", 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.

skills CLI

$ npx skills add AgibotTech/genie_sim --skill launch-scene -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install AgibotTech/genie_sim launch-scene --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/AgibotTech/genie_sim.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/source/geniesim_ros/skills/launch-scene .cursor/skills/launch-scene && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "launch-scene" agent skill from https://github.com/AgibotTech/genie_sim/tree/main/source/geniesim_ros/skills/launch-scene into .cursor/skills/launch-scene/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-scene", 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

$ gemini skills install https://github.com/AgibotTech/genie_sim.git --path source/geniesim_ros/skills/launch-scene

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add AgibotTech/genie_sim --skill launch-scene -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install AgibotTech/genie_sim launch-scene --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/AgibotTech/genie_sim.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/source/geniesim_ros/skills/launch-scene .gemini/skills/launch-scene && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "launch-scene" agent skill from https://github.com/AgibotTech/genie_sim/tree/main/source/geniesim_ros/skills/launch-scene into .gemini/skills/launch-scene/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-scene", 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.

GitHub CLI

$ gh skill install AgibotTech/genie_sim launch-scene

Installs 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).

skills CLI

$ npx skills add AgibotTech/genie_sim --skill launch-scene -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/AgibotTech/genie_sim.git skills-src && mkdir -p .github/skills && cp -r skills-src/source/geniesim_ros/skills/launch-scene .github/skills/launch-scene && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "launch-scene" agent skill from https://github.com/AgibotTech/genie_sim/tree/main/source/geniesim_ros/skills/launch-scene into .github/skills/launch-scene/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-scene", 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.

skills CLI

$ npx skills add AgibotTech/genie_sim --skill launch-scene -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install AgibotTech/genie_sim launch-scene --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/AgibotTech/genie_sim.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/source/geniesim_ros/skills/launch-scene .opencode/skills/launch-scene && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "launch-scene" agent skill from https://github.com/AgibotTech/genie_sim/tree/main/source/geniesim_ros/skills/launch-scene into .opencode/skills/launch-scene/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-scene", 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: launch-scene
GitHub stars: 1.4k
Token cost: ~2.1k tokens
SKILL.md length: 606 words
Files: 1
Skills in repo: 26
Repo updated: Sep 7, 2026
First seen: Oct 7, 2026
Licence: MPL-2.0

At a glance

Launch a geniesimbringup scene against a chosen physics + render backend, using ros2 launch geniesimbringup app.launch.py.

Works in 5 steps: Collect inputs → Make sure the overlay is sourced → Launch the scene → …
Asks to launch a scene
SKILL.md covers When to Use, Critical Patterns, The matrix and Workflow, plus 3 more sections
Calls ssh

What it does

Launch Scene is an agent skill from AgibotTech/genie_sim. Launch a geniesimbringup scene against a chosen physics + render backend, using ros2 launch geniesimbringup app.launch.py. Covers the scene × launcher matrix (pick-and-place / whole-body-control / flat-table demos × Isaac PhysX / Newton-standalone backends) and the optional MoveIt 2 + WBC RViz overlay. Trigger: When the user asks to "launch a scene", "启动场景", "run pnp", "run wbc", "start the simulator", names any scene.yaml or launcher.yaml, or wants to bring up the RT Engine in interactive mode (with or without…

Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Simulation Platform from AgiBot. The licence is MPL-2.0.

When your agent uses it

Asks to launch a scene
Start the simulator
Names any scene.yaml
Wants to bring up the RT Engine in interactive mode (with

Example prompts

“launch a scene”
“run pnp”
“run wbc”
“/launch-scene”

Requirements

Docker

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Collect inputs
Make sure the overlay is sourced
Launch the scene
(optional) MoveIt 2 + WBC RViz
Verify topics

What it can do on your machine

Read from SKILL.md and the folder at commit 6ca11c7. 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
Shell commands in SKILL.md call:
- ssh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use ssh, which can reach the network depending on how they are called.
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

Launch Scene loads about 2.1k tokens when it runs. Until then it costs about 140 tokens; SKILL.md has 606 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~140
When it runs · the whole SKILL.md, loaded when a task matches: ~2.1k

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 AgibotTech/genie_sim at commit 6ca11c7, republished under its MPL-2.0 licence (© AgibotTech). 606 words, ~2,051 tokens.

Download SKILL.mdSave it as .claude/skills/launch-scene/SKILL.md (or your agent's skills folder).

name: launch-scene
description: Launch a `genie_sim_bringup` scene against a chosen physics + render backend, using `ros2 launch genie_sim_bringup app.launch.py`. Covers the scene × launcher matrix (pick-and-place / whole-body-control / flat-table demos × Isaac PhysX / Newton-standalone backends) and the optional MoveIt 2 + WBC RViz overlay. Trigger: When the user asks to "launch a scene", "启动场景", "run pnp", "run wbc", "start the simulator", names any `scene_*.yaml` or `launcher_*.yaml`, or wants to bring up the RT Engine in interactive mode (with or without rviz / moveit).
license: MPL-2.0
metadata.author: genie-sim
metadata.version: 1.0
prerequisites: geniesim_ros:build-workspace

When to Use

User wants to bring up the Genie Sim RT Engine interactively — physics + render + ROS topics on one shared sim_time.
User references any scene yaml under source/geniesim_ros/src/ros_ws/src/genie_sim_bringup/config/scene_*.yaml or launcher yaml launcher_*.yaml.
User wants MoveIt 2 + WBC RViz on top of a running scene (Genie G2 only).

Do not use for:

Running a benchmark task → run-benchmark (under source/geniesim_benchmark/skills/).
Probing an inference server → check-inference.
Building the workspace first → build-workspace. Run that before this skill.

Critical Patterns

Scene = robot + task; Launcher = physics engine + renderer. They're orthogonal axes — pair any scene with any launcher.
Stable path is launcher_ovrtx_isaac_physx. Every launcher_newton_* and launcher_ovrtx_isaac_newton row is research / preview — physics behaviour, perf, and yaml schema can break between commits. Use the stable launcher unless the user explicitly wants the experimental rig (cloth / soft body / mjwarp).
MoveIt is Genie G2 only. Other robots run on the engine but don't have a packaged MoveIt config.
Inside the container. Every command below assumes geniesim docker into and source devel/setup.bash (see build-workspace skill).

The matrix

Scenes

Scene	Robot	What it showcases
`scene_pnp_g2_op`	Genie G2 + omnipicker	Pick-and-place workflow
`scene_wbc_g2_sp`	Genie G2 + swiftpicker	Whole-body control workflow
`scene_flat_g2_sp`	Genie G2 + swiftpicker, flat table	Baseline tabletop
`scene_flat_acone`	ARX acone	Reference robot (tabletop)
`scene_flat_aloha`	Aloha	Reference robot (tabletop)
`scene_flat_fr3`	Franka FR3	Reference robot (tabletop)
`scene_flat_ur5_robotiq_140` / `_85`	UR5 + Robotiq	Reference robot (tabletop)

Launchers

Launcher	Physics engine	Renderer	Status
`launcher_ovrtx_isaac_physx`	Isaac Sim PhysX	Standalone OVRtx node	✅ Stable — start here
`launcher_ovrtx_isaac_newton`	Isaac Sim Newton (wrapper)	Standalone OVRtx node	🧪 EXPERIMENTAL
`launcher_newton_mjwarp`	Newton-standalone + mujoco-warp	Inline OVRtx	✅ Stable (rigid only)
`launcher_newton_fsvbd`	Newton-standalone + Featherstone + VBD	Inline OVRtx	🧪 EXPERIMENTAL — cloth / soft body
`launcher_newton_avbd` / `_mjvbd` / `_mjxpbd`	Newton-standalone, mixed solvers	Inline OVRtx	🧪 EXPERIMENTAL

Workflow

Step 1 — Collect inputs

Ask the user via AskUserQuestion if not given:

Scene: free-text basename (e.g. scene_pnp_g2_op). Auto-complete from the table above.
Launcher: default launcher_ovrtx_isaac_physx (stable). Only pick a launcher_newton_* if the user explicitly wants the experimental backend or cloth / soft body.
Headless? Default false (GUI window opens on $DISPLAY). Pick the value by where you're running:
- Local workstation with a screen → headless:=false. The Isaac Sim viewport renders into a window you can see.
- Remote / SSH / headless server / CI → headless:=true. No GUI, no $DISPLAY requirement. Physics + render still run; cameras publish over ROS exactly the same. Use this on machines without a display, when running over ssh without X-forwarding, or in container / batch jobs.
- Remote machine, want the GUI? SSH with X-forwarding (ssh -X) or set $DISPLAY to a Xvfb / VNC server, then use headless:=false. Otherwise the launcher errors on the missing display rather than silently failing late.
MoveIt + RViz? Default false. Only meaningful for scene_*_g2_*.

Show full SKILL.md (176 more words)Show less

Step 2 — Make sure the overlay is sourced

bash

source devel/setup.bash                   # see `build-workspace` skill if missing
ros2 pkg list | grep genie_sim_bringup    # must list the package

Step 3 — Launch the scene

bash

ros2 launch genie_sim_bringup app.launch.py \
  scene:=<SCENE> \
  launcher_config:=<LAUNCHER> \
  headless:=<true|false>

Recommended starting line for new users (P&P, stable physics, GUI):

bash

ros2 launch genie_sim_bringup app.launch.py \
  scene:=scene_pnp_g2_op \
  launcher_config:=launcher_ovrtx_isaac_physx \
  headless:=false

Step 4 — (optional) MoveIt 2 + WBC RViz

In a second container shell:

bash

source devel/setup.bash

# default Genie G2: crsB arm + swiftpicker gripper
ros2 launch genie_sim_moveit wbc.launch.py

# different arm/gripper combo (match whatever scene_*_g2_{op,sp} you launched):
ros2 launch genie_sim_moveit wbc.launch.py arm:=crs gripper:=omnipicker

arm:={crs,crsB} and gripper:={swiftpicker,omnipicker,none} are independent — the launch wires both into the URDF filename and the SRDF xacro mappings.

Step 5 — Verify topics

bash

ros2 topic list                            # /tf, /joint_states, /joint_command, /clock, …
ros2 topic hz /clock                       # should print sim-time pacing

Commands (copy-paste summary for the user)

bash

# Inside the container, after `geniesim ros build dev`:
source devel/setup.bash

# Pick-and-place + stable Isaac PhysX:
ros2 launch genie_sim_bringup app.launch.py \
  scene:=scene_pnp_g2_op \
  launcher_config:=launcher_ovrtx_isaac_physx \
  headless:=false   # local workstation with a screen; flip to true on a remote/headless host

# Whole-body control + Newton-standalone (experimental):
ros2 launch genie_sim_bringup app.launch.py \
  scene:=scene_wbc_g2_sp \
  launcher_config:=launcher_newton_mjwarp \
  headless:=false   # local workstation with a screen; flip to true on a remote/headless host

# Optional MoveIt 2 + WBC RViz (second shell):
ros2 launch genie_sim_moveit wbc.launch.py

Notes

The same app.launch.py covers every scene × launcher combo — there is no per-scene launch file. Don't try to invoke a yaml directly.
Newton GL viewer pose is configurable per scene: every scene_*.yaml carries a viewer_camera: block with pos: / lookat:.
For cloth / soft-body work, you need a launcher_newton_* that pairs with a VBD-family solver and a scene yaml that opts into the deformable. Treat any cloth / soft-body result as a preview, not a benchmark.
init_base_pose and init_joint_pos apply as a non-physics teleport on every backend — the robot spawns at the configured pose without an initial PD swing.

Resources

Bringup package: source/geniesim_ros/src/ros_ws/src/genie_sim_bringup/
Scene + launcher yamls: source/geniesim_ros/src/ros_ws/src/genie_sim_bringup/config/
Engine overview: source/geniesim_ros/README.md
MoveIt config: source/geniesim_ros/src/ros_ws/src/genie_sim_moveit/
Package routing: source/geniesim_ros/AGENTS.md

Files

Just SKILL.md in source/geniesim_ros/skills/launch-scene of AgibotTech/genie_sim.

Open the folder on GitHubat commit 6ca11c7

Compare with similar skills

Launch Scene 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.

Launch Scene compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Launch Scene this skillAgibotTech/genie_sim	1.4k	—	~2.1k	Automated safety check: Pass	MPL-2.0	1 mo ago
Shipping and Launch Checklistaddyosmani/agent-skills	102k	1 repos	~2.8k	Automated safety check: Pass	MIT	4 days ago
Launch Strategyalirezarezvani/claude-skills	28k	—	~1.4k	Automated safety check: Pass	MIT	1 mo ago
HTML Ppt Product Launchnexu-io/open-design	100k	—	~1.3k	Automated safety check: Pass	Apache-2.0	today
Product Launch Videoheygen-com/hyperframes	58k	3 repos	~8.3k	Automated safety check: Notes	Apache-2.0	today
Launch Registryaaron-he-zhu/aaron-marketing-skills	2.9k	1 repos	~1.4k	Automated safety check: Pass	Apache-2.0	today

Similar skills

Shipping and Launch Checklist
addyosmani/agent-skills
Prepares a production launch with a pre-launch checklist, monitoring, a staged rollout and a rollback plan so every release is reversible and observable.
102k GitHub starsUsed in 1 repo~2.8k tokens
DevOps & CloudAuto-check passed
Launch Strategy
alirezarezvani/claude-skills
When the user wants to plan a product launch, feature announcement, or release strategy.
28k GitHub stars~1.4k tokensUpdated 1 mo ago
Marketing & SEOAuto-check passed
HTML Ppt Product Launch
nexu-io/open-design
OpenDesign Teams: a launch-and-adoption proposal for a mid-market design team weighing a switch from closed cloud tools.
100k GitHub stars~1.3k tokensUpdated today
Marketing & SEOAuto-check passed
Product Launch Video
heygen-com/hyperframes
Turns a product URL, script or brief into a launch or promo video built frame by frame in HyperFrames, from brand capture and story design to rendering.
58k GitHub starsUsed in 3 repos~8.3k tokens
Media & CreativeAuto-check: notes
Launch Registry
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when the user asks to "log this launch", query a launch date/embargo, record a stage transition, or update submissions/outcomes; curates launch facts through the append-only…
2.9k GitHub starsUsed in 1 repo~1.4k tokens
Marketing & SEOAuto-check passed
Launch Readiness Checklist
Donchitos/Claude-Code-Game-Studios
Generates a launch-readiness checklist across code, content, store, marketing, community, infrastructure and legal, scoped to the project and ending in go/no-go sign-offs.
26k GitHub stars~4.3k tokensUpdated 8 days ago
Product & Project ManagementAuto-check passed

More from AgibotTech/genie_sim

All 26 skills in this repo

Challenge Baseline Model
AgibotTech/genie_sim
Provision and launch the Simulation Challenge baseline inference model end to end: clone the inference code from a given git repo/branch, download the checkpoints from ModelScope into the repo's…
1.4k GitHub stars~2.4k tokensUpdated 1 mo ago
Auto-check passed
Challenge Download Datasets
AgibotTech/genie_sim
Download the Simulation Challenge LeRobot v2.1 training datasets from ModelScope using ./scripts/downloaddataset.sh.
1.4k GitHub stars~960 tokensUpdated 1 mo ago
Auto-check passed
Add Robot
AgibotTech/genie_sim
Bring a custom robot into the Genie Sim RT Engine — author / fix a xacro / URDF in geniesimrobotmodel, prep meshes with the offline tools (normalizeobjnames.py, diagnoseurdf.py, recomputeinertia.py…
1.4k GitHub stars~2.1k tokensUpdated 1 mo ago
Auto-check passed
Build Workspace
AgibotTech/genie_sim
Build the geniesimros colcon workspace inside the Genie Sim Docker container using the geniesim ros build CLI verb.
1.4k GitHub stars~1.2k tokensUpdated 1 mo ago
Auto-check passed
Challenge Inference Protocol
AgibotTech/genie_sim
Reference for the Simulation Challenge inference wire protocol — the exact obs (input) and action (output) message format exchanged between the gateway/genie-sim simulator and the contestant's…
1.4k GitHub stars~1.7k tokensUpdated 1 mo ago
Auto-check passed
Challenge Login
AgibotTech/genie_sim
A skill your agent uses when the contestant needs to obtain or refresh their Simulation Challenge JWT (CHALLENGETOKEN), or wants to inspect the current logged-in user.
1.4k GitHub stars~1.6k tokensUpdated 1 mo ago
Auto-check passed

Questions about Launch Scene

What does Launch Scene do?

Launch a geniesimbringup scene against a chosen physics + render backend, using ros2 launch geniesimbringup app.launch.py. Launch Scene is an agent skill from AgibotTech/genie_sim.py.

When should I use Launch Scene?

Launch Scene fits situations like: asks to launch a scene; start the simulator; names any scene.yaml; wants to bring up the RT Engine in interactive mode (with.

How do I install Launch Scene in Claude Code?

Run `npx skills add AgibotTech/genie_sim --skill launch-scene -a claude-code`. Or copy the skill folder (source/geniesim_ros/skills/launch-scene in AgibotTech/genie_sim) into .claude/skills/launch-scene in your project. Claude Code loads it when a task matches its description.

How do I install Launch Scene in Codex?

Run `npx skills add AgibotTech/genie_sim --skill launch-scene -a codex`. Or copy the skill folder (source/geniesim_ros/skills/launch-scene in AgibotTech/genie_sim) into .agents/skills/launch-scene in your project. Codex loads it when a task matches its description.

Can I use Launch Scene 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 AgibotTech/genie_sim --skill launch-scene -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/launch-scene, .gemini/skills/launch-scene, .github/skills/launch-scene and .opencode/skills/launch-scene in your project.

What does Launch Scene need to run?

Going by SKILL.md and its folder, Launch Scene needs the command-line tools its instructions call (ssh). Our summary lists: Docker.

Does Launch Scene access the network?

SKILL.md contains no URLs. Its commands use ssh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Launch Scene 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 Launch Scene use?

Launch Scene is published under the MPL-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Launch Scene use?

About 2.1k tokens (SKILL.md is roughly 8.2k 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 Launch Scene?

Skills that share tags, products or a category with Launch Scene: Shipping and Launch Checklist (addyosmani/agent-skills, 102k stars), Launch Strategy (alirezarezvani/claude-skills, 28k stars), HTML Ppt Product Launch (nexu-io/open-design, 100k stars) and Product Launch Video (heygen-com/hyperframes, 58k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Launch Scene?

AgibotTech (a GitHub organization) maintains it in AgibotTech/genie_sim, which has 1,413 GitHub stars. The repository holds 26 skills in this directory. The repository was last updated on September 7, 2026.

Source: AgibotTech/genie_sim on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Launch Scene

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

When to Use

Critical Patterns

The matrix

Scenes

Launchers

Workflow

Step 1 — Collect inputs

Step 2 — Make sure the overlay is sourced

Step 3 — Launch the scene

Step 4 — (optional) MoveIt 2 + WBC RViz

Step 5 — Verify topics

Commands (copy-paste summary for the user)

Notes

Resources

Files

Compare with similar skills

Similar skills

More from AgibotTech/genie_sim

Questions about Launch Scene