Guide · Agent skill
How to use the OBS Studio Scene Editor CLI agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The cli-anything-obs-studio skill teaches an AI agent to use a command-line tool that edits OBS Studio scene collections, the saved layouts of scenes, sources, filters, audio and output settings. It is useful if you want to script or batch-edit a scene layout, or have an agent draft one that you review in OBS later. After this guide you will know what the skill lets the agent do, how to install it, how to ask for work in plain language, and what to check before trusting its edits.
OBS Studio Scene Editor CLIHKUDS/CLI-Anything · Apache-2.0 Download the skill Quick start
- 1Download and unzip the skill. Download the skill ZIP from this page and unzip it into ~/.claude/skills/ or a project's .claude/skills/ folder. In the Claude apps, you can instead upload it under Settings, Capabilities, Skills.
- 2Install the CLI package. Run pip install cli-anything-obs_studio. The skill requires Python 3.10 or newer.
- 3Confirm the tool runs. Run cli-anything-obs_studio --help and check that the command list prints.
- 4Back up your scene collection. Copy any important JSON scene collection file, because saves write directly to that file.
- 5Ask for a change in plain language. Name the file, scene and change you want, such as adding a filter or setting a volume.
- 6Review the result. Run project info or list on the file and open it in OBS to check the scenes and sources before using them.
What the skill makes the agent do
A skill is a folder of instructions that an AI agent loads when a task matches it. This one wraps a command-line interface called cli-anything-obs_studio. The source describes it as a stateful interface for OBS Studio scene collection editing that uses a JSON scene collection format and needs no OBS installation for editing.
With the skill, the agent can create, inspect and change scene collection files through commands rather than clicking through the OBS interface. The command groups cover projects, scenes, sources, filters, audio, transitions, output settings and session undo/redo.
- Project: create, open, save, show info or print the raw JSON
- Scene: add, remove, duplicate, set the active scene, list scenes
- Source: add, remove, duplicate, set name/visible/locked/opacity/rotation, transform position, size, crop and rotation
- Filter: add, remove, set parameters, list filters, list available filter types
- Audio: add or remove global audio sources, set volume (0.0-3.0), mute, unmute, set monitoring type
- Transition: add, remove, set active, set duration in milliseconds
- Output: configure streaming, recording and general output settings, list encoding presets
- Session: status, undo, redo and history
Install the skill
Download the skill ZIP from this page and unzip it into one of two locations. Use ~/.claude/skills/ to make the skill available to all your projects, or a project's .claude/skills/ folder to limit it to that project.
If you use the Claude apps instead, you can upload the ZIP under Settings, then Capabilities, then Skills.
The CLI itself is a Python package. Install it with pip. The skill's SKILL.md lists Python 3.10 or newer and says OBS Studio must be installed on your system, although the same file also says no OBS installation is required for editing.
pip install cli-anything-obs_studioCheck that the command works
Before asking the agent for anything, run the help command in a terminal. If it prints the command list, the agent will be able to call the tool. The source also documents an interactive mode that starts when you run the command with no subcommand.
cli-anything-obs_studio --helpTrigger the skill with natural requests
You do not need to name commands. Describe the change you want in plain language and mention the scene collection file, and the agent should pick the skill when the request matches its description. Good requests name the file, the scene and the change. Vague requests are more likely to produce guesses.
Ask for a review step when the stakes are high, for example by asking the agent to save to a new file rather than overwriting the original.
- Create a new scene collection called studio-draft.json with a Main scene and a Camera scene, then list the scenes.
- In myproject.json, set the volume of the desktop audio source to 0.5 and tell me what changed.
- Add a color correction filter to the webcam source in the Gaming scene of show.json.
- Set the transition duration to 500 milliseconds and show the output settings.
- Undo the last change to show.json and show me the history.
Run commands yourself
You can use the same commands the agent uses. The source shows creating a project file, reading its info, and using JSON output. The --json flag comes before the subcommand. The source says it is meant for agent consumption, so you will see structured output rather than tables.
- Human-readable output is the default, with tables and formatted text.
- Add --json before the command to get structured output.
- Check return codes: 0 means success, non-zero means an error.
- Use absolute paths for file operations, as the source recommends for agents.
cli-anything-obs_studio --json project info -p project.jsonSafety notes before you run it
This skill runs scripts, and the Python package executes locally. The skill metadata says it does not use the network. Read the source before running any tool an agent gives you, and keep the scene collection file under version control or copy it yourself first.
Saves write directly to the JSON file, so a bad edit lands in your original file. Undo covers up to 50 levels of history in the session, but do not rely on it as a backup. Do not expect the skill to change a live stream: the documentation describes editing JSON project files, not controlling a running OBS instance.
- Copy your important scene collection before letting an agent edit it.
- Review the saved JSON in OBS before using it on air.
- Expect edits to affect only the file, not what is currently broadcast.
What people use it for
- Batch-creating several scene collection drafts with the same scenes and sources for different shows.
- Setting audio volumes, mute states and monitoring types across a saved layout without clicking through OBS.
- Adding or adjusting filters on named sources in a scene, then checking the list of filters.
- Changing transition durations and output settings in a file before handing it to a broadcast operator to review.
- Experimenting with a layout and using undo, redo and history to step back through changes in a session.
Frequently asked questions
How do I install the cli-anything-obs-studio skill?
Download the skill ZIP from this page and unzip it into ~/.claude/skills/ or a project's .claude/skills/ folder. In the Claude apps, you can upload it under Settings, Capabilities, Skills. The CLI itself installs with pip install cli-anything-obs_studio.
What are the requirements for the OBS Studio CLI skill?
The SKILL.md lists Python 3.10 or newer and says OBS Studio must be installed on your system. The same file also says no OBS installation is required for editing, so the two statements should be checked against your own setup.
Is the OBS Studio scene editor CLI free?
The source material provided for this guide does not state a price or licence terms for the package itself. This page's item is listed under the Apache-2.0 licence, so check the licence file in the package before you rely on it.
Can this skill control a live OBS stream?
No. The documentation describes editing JSON scene collection files, not controlling a running OBS instance. Edits may not change what is on air, so review the saved file in OBS before using it live.
Will the agent overwrite my scene collection?
Saves write directly to the JSON file. Copy any important scene collection before letting an agent edit it, and use a new output file name when you want to keep the original.
How does this compare with editing scenes in the OBS interface?
The skill edits saved files through commands, which suits scripting, batch changes and agent-drafted layouts. Manual editing in the OBS interface is better for live adjustments and visual placement. The source does not compare the two in terms of speed or accuracy.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Use this skill if you want an AI agent or a script to draft, batch-edit or inspect OBS scene collection files that you will review in OBS afterwards. Pick something else if you need to control a live stream or change what is on air in real time, or if you cannot afford to risk an original scene collection without a backup.
Download the skill