skills/integrations/obs-scene-capture/SKILL.md
Use OBS as a generic screenshot API. List scenes, inspect scene sources, and capture still images from scenes or sources via obs-websocket.
npx skillsauth add helix4u/hermes-agent obs-scene-captureInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this skill to treat OBS like a local screenshot API for any scene or source you have configured.
TMP/obs/ for downstream analysis or sharing4455)obsws-python is installed in the active environmentInstall dependency:
pip install obsws-python
If a local venv exists, activate it first.
List scenes:
python skills/integrations/obs-scene-capture/scripts/obs_still.py --list-scenes
List sources in a scene:
python skills/integrations/obs-scene-capture/scripts/obs_still.py --list-sources --scene "Main Monitor"
Capture a scene:
python skills/integrations/obs-scene-capture/scripts/obs_still.py --scene "Main Monitor" --output TMP/obs/main-monitor.png
Capture a source:
python skills/integrations/obs-scene-capture/scripts/obs_still.py --source "Browser Capture" --output TMP/obs/browser-capture.png
Optional explicit resolution:
python skills/integrations/obs-scene-capture/scripts/obs_still.py --scene "Main Monitor" --output TMP/obs/main-monitor-1440p.png --width 2560 --height 1440
Defaults:
--host localhost--port 4455--password ""Environment variable overrides:
OBS_HOSTOBS_PORTOBS_PASSWORD--list-scenes to discover valid scene names.--list-sources --scene "..." to inspect precise source names.TMP/obs/main-monitor.png) as an artifact for the next step in your flow.If OBS connection setup is the blocker, read references/obs-websocket.md.
development
Use when you have a spec or requirements for a multi-step task. Creates comprehensive implementation plans with bite-sized tasks, exact file paths, and complete code examples.
development
Use when implementing any feature or bugfix, before writing implementation code. Enforces RED-GREEN-REFACTOR cycle with test-first approach.
development
Use when encountering any bug, test failure, or unexpected behavior. 4-phase root cause investigation — NO fixes without understanding the problem first.
development
Use when executing implementation plans with independent tasks. Dispatches fresh delegate_task per task with two-stage review (spec compliance then code quality).