Skip to content
Back to search

obs-settings-advisor

MarketplaceWorks with Claude CodeGitHub

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
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/mikahatdichlieb--obs-settings-advisor/badge.svg)](/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
  1. {
  2. "name": "obs-settings-advisor",
  3. "description": "OBS Studio settings advisor skill for Claude Code.",
  4. "owner": {
  5. "name": "mikahatdichlieb"
  6. },
  7. "plugins": [
  8. {
  9. "name": "obs-settings-advisor",
  10. "source": "./",
  11. "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.",
  12. "version": "0.2.0"
  13. }
  14. ]
  15. }
README.md · README · 158 lines
  1. # obs-settings-advisor
  2. [![CI](https://github.com/mikahatdichlieb/obs-settings-advisor/actions/workflows/ci.yml/badge.svg)](https://github.com/mikahatdichlieb/obs-settings-advisor/actions/workflows/ci.yml)
  3. [![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
  4. A skill for Claude that suggests OBS Studio settings for your PC. It looks at your hardware and
  5. your OBS logs, checks the current requirements of Twitch, YouTube or Kick, and explains every
  6. value it recommends. If you ask, it also writes a [blur](https://github.com/f0e/blur) config or a
  7. [Smoothie](https://github.com/couleur-tweak-tips/smoothie-rs) recipe that matches your recordings.
  8. It only reads. Your OBS configuration is never changed; you apply the settings yourself. blur
  9. and Smoothie configs are only written when you ask for it.
  10. <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%">
  11. ## Install
  12. ### Claude Code
  13. ```text
  14. /plugin marketplace add mikahatdichlieb/obs-settings-advisor
  15. /plugin install obs-settings-advisor@obs-settings-advisor
  16. ```
  17. Or copy the skill folder into your skills directory:
  18. ```bash
  19. git clone https://github.com/mikahatdichlieb/obs-settings-advisor.git
  20. mkdir -p ~/.claude/skills
  21. cp -r obs-settings-advisor/skills/obs-settings-advisor ~/.claude/skills/
  22. ```
  23. On Windows:
  24. ```powershell
  25. git clone https://github.com/mikahatdichlieb/obs-settings-advisor.git
  26. New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null
  27. Copy-Item -Recurse obs-settings-advisor\skills\obs-settings-advisor "$HOME\.claude\skills\"
  28. ```
  29. ### Claude.ai
  30. Zip the skill folder (`cd skills && zip -r obs-settings-advisor.zip obs-settings-advisor`) and
  31. upload it under Settings > Capabilities > Skills. Code execution has to be enabled.
  32. Scripts on Claude.ai run in a cloud sandbox, not on your PC, so the skill will ask you to run the
  33. hardware script locally and paste the result, and to attach your OBS log file
  34. (OBS: Help > Log Files > Show Log Files).
  35. ## Usage
  36. Ask Claude about your OBS setup, for example:
  37. - "My Twitch stream drops frames in Apex. What should I change?"
  38. - "Which settings should I use to record Valorant at 240 fps?"
  39. - "I record Minecraft at 240 fps for motion blur. Are my OBS settings right?"
  40. - "Make me a blur config, a bit less blurry than the default."
  41. - "Turn my blur config into a Smoothie recipe."
  42. - "Here's my blur config, why do my clips look so unclear?"
  43. What the skill does:
  44. 1. Asks for what it can't detect: stream or record (and whether the recording is for motion
  45. blur), platform, upload speed, which games.
  46. 2. Runs a hardware script: CPU, RAM, GPU and driver, hardware encoder, displays, OBS version.
  47. 3. Looks up the current platform limits and OBS documentation.
  48. 4. Finds your newest OBS log and analyzes it: encoder, resolution, FPS, and skipped, lagged and
  49. dropped frames.
  50. 5. Gives one table of settings with a reason for each value, plus alternatives where there is a
  51. real tradeoff. If your upload or hardware can't do what you're asking for, it says so.
  52. 6. Ends with a short test: record 2-3 minutes of gameplay, then analyze the new log.
  53. 7. Optionally writes a `.blur-config.cfg` or a Smoothie recipe. It first checks that the OBS
  54. recording suits frame blending (FPS, rate control, encoder preset, no skipped frames), and it
  55. can review existing configs: old blur v1 configs whose keys v2 ignores, and Smoothie recipes
  56. with typos that stop Smoothie.
  57. ## Motion blur recordings
  58. For clips that blur or Smoothie turn into motion blur, the OBS recording is an intermediate file,
  59. and the skill sets it up that way:
  60. - 120 to 360 fps through "Fractional FPS Value" (the other FPS fields in OBS stop at 60 and 120),
  61. quality-based rate control, a fast encoder preset and NV12.
  62. - A test recording checked with `analyze_obs_log.py --goal blend`: skipped frames, slow encoder
  63. settings, FPS that don't divide evenly into the output FPS.
  64. - On Linux, a capture source that fits X11 or Wayland, including obs-vkcapture for games.
  65. - Then the blur config or Smoothie recipe, as a code block or, if you ask, as a file. Existing
  66. configs are never overwritten without your OK.
  67. ## Scripts
  68. The scripts also work without Claude. They print JSON and need nothing beyond the OS tools and
  69. Python 3.8+.
  70. | Script | Purpose |
  71. |---|---|
  72. | `detect_hardware.sh` / `.ps1` | Hardware and OBS version, on Linux also session type and capture tools (bash for macOS and Linux, PowerShell for Windows) |
  73. | `find_obs_logs.sh` / `.ps1` | Newest three OBS logs, and the newest one that contains a finished recording or stream |
  74. | `analyze_obs_log.py` | Turns an OBS log into JSON with frame statistics and detected problems |
  75. ```bash
  76. cd skills/obs-settings-advisor/scripts
  77. bash detect_hardware.sh
  78. bash find_obs_logs.sh
  79. python3 analyze_obs_log.py "~/.config/obs-studio/logs/<file>.txt"
  80. python3 analyze_obs_log.py "~/.config/obs-studio/logs/<file>.txt" --goal blend # recording for blur/Smoothie
  81. ```
  82. ```powershell
  83. cd skills\obs-settings-advisor\scripts
  84. powershell -NoProfile -ExecutionPolicy Bypass -File detect_hardware.ps1
  85. powershell -NoProfile -ExecutionPolicy Bypass -File find_obs_logs.ps1
  86. python analyze_obs_log.py "%APPDATA%\obs-studio\logs\<file>.txt"
  87. ```
  88. Output never contains your username, hostname, serial numbers, or MAC/IP addresses. Paths are
  89. printed as `~`, `$USER` or `%APPDATA%`, and the analyzer accepts them in that form.
  90. Problems the analyzer reports:
  91. | ID | Meaning |
  92. |---|---|
  93. | `encoder_overloaded` | Frames skipped because the encoder can't keep up |
  94. | `rendering_lag` | Frames lagged because the GPU is busy, usually with the game |
  95. | `network_dropped_frames` | Frames dropped because the upload can't sustain the bitrate |
  96. | `stream_disconnects`, `bitrate_congestion` | Connection lost or bitrate lowered during the stream |
  97. | `configured_encoder_missing`, `hardware_encoder_error` | Encoder failed to load or errored, usually a driver problem |
  98. | `obs_on_integrated_gpu` | OBS runs on the integrated GPU of a laptop that has a dedicated one |
  99. | `stream_not_cbr`, `stream_keyframe_interval` | Stream encoder not set to CBR or 2 s keyframes |
  100. | `fps_above_60`, `x264_with_hw_available`, `lookahead_under_load` | Settings that cost performance for little gain |
  101. | `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 |
  102. ## Repository layout
  103. ```text
  104. skills/obs-settings-advisor/
  105. SKILL.md instructions Claude follows
  106. scripts/ detection, log finder, log analyzer
  107. references/ encoders, platform limits, log patterns, sources, blur, Smoothie
  108. tests/ unit tests, sample OBS logs, macOS mocks
  109. ```
  110. ## Development
  111. ```bash
  112. python3 tests/validate_skill.py
  113. python3 -m unittest discover -s tests -v
  114. ```
  115. CI runs the tests, ShellCheck and PSScriptAnalyzer on Ubuntu, macOS and Windows, and runs the
  116. PowerShell scripts under both Windows PowerShell 5.1 and PowerShell 7.
  117. Sample logs and fixes for hardware that isn't covered yet are welcome. Remove usernames, paths,
  118. device IDs and stream URLs from logs before sharing them.
  119. ## License
  120. MIT. Not affiliated with the OBS Project, blur or Smoothie.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.