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 OBS Studio Scene Editor CLI agent skill teaches an AI agent to use a command-line tool that edits OBS Studio scene collections, the saved files that define scenes, sources, filters, audio and output settings. It is aimed at streamers, video producers and developers who want scripted or templated OBS layouts instead of clicking through the interface. After this guide you will know what the skill does, how to install it, how to ask for work in plain language, and what to check before saving changes.
OBS Studio Scene Editor CLIHKUDS/CLI-Anything · Apache-2.0 Download the skill Quick start
- 1Install prerequisites. Confirm Python 3.10 or newer is installed and that OBS Studio is installed on your system.
- 2Install the CLI package. Run pip install cli-anything-obs_studio in your terminal.
- 3Add the skill folder. Download the skill ZIP from this page and unzip it into ~/.claude/skills/ or a project's .claude/skills/ folder, or upload it under Settings, Capabilities, Skills in the Claude apps.
- 4Test the CLI. Run cli-anything-obs_studio --help to confirm the command is available.
- 5Make a copy of your project file. Back up any existing scene collection JSON before the agent edits it.
- 6Ask for a change in plain language. Describe the scene, source or audio change you want, then ask the agent to list the result and check it before saving.
What the skill lets an agent do
The skill describes a stateful command-line interface for OBS Studio scene collection editing. Instead of working in the OBS window, an agent can create a new project file, list and change scenes, add and adjust sources, add filters, manage global audio sources, set transitions, and configure streaming, recording and output settings.
The tool works on a JSON scene collection format. The source states that no OBS installation is needed for editing, but OBS Studio must still be installed on the system. The skill edits project files; it does not control a running OBS instance.
- Scenes: add, remove, duplicate, set active, list
- Sources: add, remove, duplicate, set name/visible/locked/opacity/rotation, transform position, size, crop and rotation, list
- Filters: add, remove, set parameters, list, list available types
- Audio: add or remove global sources, set volume (0.0-3.0), mute, unmute, set monitoring type, list
- Transitions, output settings and session undo, redo and history
Install the skill and its CLI
Download the skill ZIP from this page and unzip it into one of these folders: ~/.claude/skills/ for your user account, or .claude/skills/ inside a specific project. Alternatively, in the Claude apps, open Settings, then Capabilities, then Skills, and upload the skill there.
The CLI itself is a Python package. The skill's install command is shown below. You need Python 3.10 or newer and OBS Studio installed on your system.
- Prerequisite: Python 3.10+
- Prerequisite: OBS Studio installed on the system
- The package is distributed as cli-anything-obs_studio
pip install cli-anything-obs_studioTrigger the skill with natural requests
You do not need to type commands yourself. Describe the result you want in plain language, and name OBS and the project file if you have one. The agent should pick the matching command group. Be specific about which scene or source to change, because the tool works by index and name.
If you want to check the agent's work, ask it to list the scenes or sources first and then make the change. Ask it to show the JSON output when you want to read exact values.
- 'Create a new OBS scene collection called gaming-layout.json with three scenes: Start, Game and Ending.'
- 'In project.json, list all sources in the Game scene and tell me which ones are hidden.'
- 'Set the volume of the Mic source to 0.8 and mute the Desktop Audio source.'
- 'Undo the last change I made to the scene collection.'
- 'Show me the current streaming and recording output settings in project.json.'
Commands the agent uses
The skill groups commands under Project, Scene, Source, Filter, Audio, Transition, Output and Session. Each group has the operations listed below. The CLI supports a human-readable default output and a --json flag that returns structured JSON, which the source recommends for agents.
Agents following the skill should use the --json flag, use absolute paths for file operations, check return codes (0 means success), parse stderr for errors, and verify that output files exist after exports.
- project: new, open, save, info, json
- scene: add, remove, duplicate, set-active, list
- source: add, remove, duplicate, set, transform, list
- filter: add, remove, set, list, list-available
- audio: add, remove, volume, mute, unmute, monitor, list
- transition: add, remove, set-active, duration (milliseconds), list
- output: streaming, recording, settings, info, presets
- session: status, undo, redo, history
cli-anything-obs_studio --json project info -p project.jsonSafety, scripts and network use
The skill runs scripts, because the CLI is a Python program that the agent executes. It does not use the network, according to the skill listing. The skill folder contains a single file, SKILL.md.
Edits write directly to project JSON files. Undo and redo cover up to 50 levels within a session, but the source does not describe undo across separate sessions. Before letting an agent change a live production file, keep a copy of it, and review the agent's listed changes before you save. The skill cannot check the layout visually.
- Runs scripts: yes (Python CLI)
- Uses network: no
- Files included: SKILL.md only
- Undo/redo: up to 50 levels of history in a session
- Edits overwrite project JSON files directly, so keep a backup copy
What people use it for
- Create a template scene collection with the same scenes and sources for every stream or recording setup
- Batch-adjust audio levels, such as setting microphone volume or muting a source across layouts
- Add or change filters on a source and read back the filter list to confirm the result
- Set streaming or recording output settings from a script or agent workflow
- Review an existing scene collection as JSON and report hidden or locked sources
Frequently asked questions
How do I install the OBS Studio Scene Editor CLI agent skill?
Download the skill ZIP from this page and unzip it into ~/.claude/skills/ or a project's .claude/skills/ folder. You can also upload it in the Claude apps under Settings, then Capabilities, then Skills. The CLI itself is installed with pip install cli-anything-obs_studio.
What do I need to run it?
The source lists Python 3.10 or newer and OBS Studio installed on the system. OBS does not need to be running for editing, because the tool edits JSON scene collection files.
Is the skill free to use?
This page lists the skill under the Apache-2.0 licence, and the source repository is HKUDS/CLI-Anything. Check the licence file in the repository for the full terms before redistributing it.
Can the agent control OBS while it is streaming?
No. The skill describes editing project JSON files, not live control of a running OBS instance. Use OBS itself for live changes.
Why does the skill name show as >- in the file?
The SKILL.md frontmatter uses a YAML folded-style marker for the name field, so the parsed name can appear as >- instead of cli-anything-obs_studio. If your agent does not recognise the skill, check that the folder and file are in the right location and that the frontmatter is valid.
How does it compare with editing scenes in the OBS interface?
The skill suits repeatable, scripted or templated changes and gives agents structured JSON output with undo and redo. For visual layout work or live switching, the OBS interface is the better tool, since the agent cannot see the result.
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 agent to batch-edit, template or inspect OBS scene collection files and you can review changes before saving. Skip it if you need live control of a running OBS session or want the agent to check the visual layout, since it only edits data files.
Download the skill