obs-settings-advisor
OBS Studio settings advisor skill for Claude Code.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Badge for your README
Markdown
[](/listings/mikahatdichlieb--obs-settings-advisor)HTML
<a href="/listings/mikahatdichlieb--obs-settings-advisor"><img src="/api/listings/mikahatdichlieb--obs-settings-advisor/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
Claude Code
/plugin marketplace add mikahatdichlieb/obs-settings-advisor /plugin install obs-settings-advisor@obs-settings-advisor
Or copy the skill folder into your skills directory:
git clone https://github.com/mikahatdichlieb/obs-settings-advisor.git mkdir -p ~/.claude/skills cp -r obs-settings-advisor/skills/obs-settings-advisor ~/.claude/skills/
On Windows:
git clone https://github.com/mikahatdichlieb/obs-settings-advisor.git New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null Copy-Item -Recurse obs-settings-advisor\skills\obs-settings-advisor "$HOME\.claude\skills\"
Claude.ai
Zip the skill folder (`cd skills && zip -r obs-settings-advisor.zip obs-settings-advisor`) and upload it under Settings > Capabilities > Skills. Code execution has to be enabled.
Scripts on Claude.ai run in a cloud sandbox, not on your PC, so the skill will ask you to run the hardware script locally and paste the result, and to attach your OBS log file (OBS: Help > Log Files > Show Log Files).
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
.claude-plugin/marketplace.json · Manifest · 15 lines
- {
- "name": "obs-settings-advisor",
- "description": "OBS Studio settings advisor skill for Claude Code.",
- "owner": {
- "name": "mikahatdichlieb"
- },
- "plugins": [
- {
- "name": "obs-settings-advisor",
- "source": "./",
- "description": "Recommends OBS Studio settings for your PC and goal, and diagnoses dropped frames, encoder overload and rendering lag from real OBS logs. Read-only.",
- "version": "0.2.0"
- }
- ]
- }
README.md · README · 158 lines
- # obs-settings-advisor
- [](https://github.com/mikahatdichlieb/obs-settings-advisor/actions/workflows/ci.yml)
- [](LICENSE)
- A skill for Claude that suggests OBS Studio settings for your PC. It looks at your hardware and
- your OBS logs, checks the current requirements of Twitch, YouTube or Kick, and explains every
- value it recommends. If you ask, it also writes a [blur](https://github.com/f0e/blur) config or a
- [Smoothie](https://github.com/couleur-tweak-tips/smoothie-rs) recipe that matches your recordings.
- It only reads. Your OBS configuration is never changed; you apply the settings yourself. blur
- and Smoothie configs are only written when you ask for it.
- <img src="assets/demo.svg" alt="Output of analyze_obs_log.py: NVENC at 6000 kbps, 2.9% dropped frames over Wi-Fi, 0.6% rendering lag" width="100%">
- ## Install
- ### Claude Code
- ```text
- /plugin marketplace add mikahatdichlieb/obs-settings-advisor
- /plugin install obs-settings-advisor@obs-settings-advisor
- ```
- Or copy the skill folder into your skills directory:
- ```bash
- git clone https://github.com/mikahatdichlieb/obs-settings-advisor.git
- mkdir -p ~/.claude/skills
- cp -r obs-settings-advisor/skills/obs-settings-advisor ~/.claude/skills/
- ```
- On Windows:
- ```powershell
- git clone https://github.com/mikahatdichlieb/obs-settings-advisor.git
- New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null
- Copy-Item -Recurse obs-settings-advisor\skills\obs-settings-advisor "$HOME\.claude\skills\"
- ```
- ### Claude.ai
- Zip the skill folder (`cd skills && zip -r obs-settings-advisor.zip obs-settings-advisor`) and
- upload it under Settings > Capabilities > Skills. Code execution has to be enabled.
- Scripts on Claude.ai run in a cloud sandbox, not on your PC, so the skill will ask you to run the
- hardware script locally and paste the result, and to attach your OBS log file
- (OBS: Help > Log Files > Show Log Files).
- ## Usage
- Ask Claude about your OBS setup, for example:
- - "My Twitch stream drops frames in Apex. What should I change?"
- - "Which settings should I use to record Valorant at 240 fps?"
- - "I record Minecraft at 240 fps for motion blur. Are my OBS settings right?"
- - "Make me a blur config, a bit less blurry than the default."
- - "Turn my blur config into a Smoothie recipe."
- - "Here's my blur config, why do my clips look so unclear?"
- What the skill does:
- 1. Asks for what it can't detect: stream or record (and whether the recording is for motion
- blur), platform, upload speed, which games.
- 2. Runs a hardware script: CPU, RAM, GPU and driver, hardware encoder, displays, OBS version.
- 3. Looks up the current platform limits and OBS documentation.
- 4. Finds your newest OBS log and analyzes it: encoder, resolution, FPS, and skipped, lagged and
- dropped frames.
- 5. Gives one table of settings with a reason for each value, plus alternatives where there is a
- real tradeoff. If your upload or hardware can't do what you're asking for, it says so.
- 6. Ends with a short test: record 2-3 minutes of gameplay, then analyze the new log.
- 7. Optionally writes a `.blur-config.cfg` or a Smoothie recipe. It first checks that the OBS
- recording suits frame blending (FPS, rate control, encoder preset, no skipped frames), and it
- can review existing configs: old blur v1 configs whose keys v2 ignores, and Smoothie recipes
- with typos that stop Smoothie.
- ## Motion blur recordings
- For clips that blur or Smoothie turn into motion blur, the OBS recording is an intermediate file,
- and the skill sets it up that way:
- - 120 to 360 fps through "Fractional FPS Value" (the other FPS fields in OBS stop at 60 and 120),
- quality-based rate control, a fast encoder preset and NV12.
- - A test recording checked with `analyze_obs_log.py --goal blend`: skipped frames, slow encoder
- settings, FPS that don't divide evenly into the output FPS.
- - On Linux, a capture source that fits X11 or Wayland, including obs-vkcapture for games.
- - Then the blur config or Smoothie recipe, as a code block or, if you ask, as a file. Existing
- configs are never overwritten without your OK.
- ## Scripts
- The scripts also work without Claude. They print JSON and need nothing beyond the OS tools and
- Python 3.8+.
- | Script | Purpose |
- |---|---|
- | `detect_hardware.sh` / `.ps1` | Hardware and OBS version, on Linux also session type and capture tools (bash for macOS and Linux, PowerShell for Windows) |
- | `find_obs_logs.sh` / `.ps1` | Newest three OBS logs, and the newest one that contains a finished recording or stream |
- | `analyze_obs_log.py` | Turns an OBS log into JSON with frame statistics and detected problems |
- ```bash
- cd skills/obs-settings-advisor/scripts
- bash detect_hardware.sh
- bash find_obs_logs.sh
- python3 analyze_obs_log.py "~/.config/obs-studio/logs/<file>.txt"
- python3 analyze_obs_log.py "~/.config/obs-studio/logs/<file>.txt" --goal blend # recording for blur/Smoothie
- ```
- ```powershell
- cd skills\obs-settings-advisor\scripts
- powershell -NoProfile -ExecutionPolicy Bypass -File detect_hardware.ps1
- powershell -NoProfile -ExecutionPolicy Bypass -File find_obs_logs.ps1
- python analyze_obs_log.py "%APPDATA%\obs-studio\logs\<file>.txt"
- ```
- Output never contains your username, hostname, serial numbers, or MAC/IP addresses. Paths are
- printed as `~`, `$USER` or `%APPDATA%`, and the analyzer accepts them in that form.
- Problems the analyzer reports:
- | ID | Meaning |
- |---|---|
- | `encoder_overloaded` | Frames skipped because the encoder can't keep up |
- | `rendering_lag` | Frames lagged because the GPU is busy, usually with the game |
- | `network_dropped_frames` | Frames dropped because the upload can't sustain the bitrate |
- | `stream_disconnects`, `bitrate_congestion` | Connection lost or bitrate lowered during the stream |
- | `configured_encoder_missing`, `hardware_encoder_error` | Encoder failed to load or errored, usually a driver problem |
- | `obs_on_integrated_gpu` | OBS runs on the integrated GPU of a laptop that has a dedicated one |
- | `stream_not_cbr`, `stream_keyframe_interval` | Stream encoder not set to CBR or 2 s keyframes |
- | `fps_above_60`, `x264_with_hw_available`, `lookahead_under_load` | Settings that cost performance for little gain |
- | `blend_fps_low`, `blend_fps_uneven`, `blend_slow_encoder_settings`, `blend_bitrate_rate_control`, `blend_color_format` | With `--goal blend`: the high-FPS recording doesn't suit frame blending |
- ## Repository layout
- ```text
- skills/obs-settings-advisor/
- SKILL.md instructions Claude follows
- scripts/ detection, log finder, log analyzer
- references/ encoders, platform limits, log patterns, sources, blur, Smoothie
- tests/ unit tests, sample OBS logs, macOS mocks
- ```
- ## Development
- ```bash
- python3 tests/validate_skill.py
- python3 -m unittest discover -s tests -v
- ```
- CI runs the tests, ShellCheck and PSScriptAnalyzer on Ubuntu, macOS and Windows, and runs the
- PowerShell scripts under both Windows PowerShell 5.1 and PowerShell 7.
- Sample logs and fixes for hardware that isn't covered yet are welcome. Remove usernames, paths,
- device IDs and stream URLs from logs before sharing them.
- ## License
- MIT. Not affiliated with the OBS Project, blur or Smoothie.
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.