From obs-mgmt
Install a third-party OBS Studio plugin from a release URL, GitHub repo, or local archive. Resolves the correct plugin install location based on install type (native vs Flatpak vs Snap), unpacks the artifact, sets file permissions, and prompts the user to restart OBS to load the new plugin. Supports .deb, .tar.gz/.tar.xz, .zip, and prebuilt directories.
npx claudepluginhub danielrosehill/claude-code-plugins --plugin obs-mgmtThis skill uses the workspace's default tool permissions.
Installs a third-party OBS plugin into the active OBS install's plugin directory.
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Share bugs, ideas, or general feedback.
Installs a third-party OBS plugin into the active OBS install's plugin directory.
setup and detect-install have run.backup-config is strongly recommended before installing plugins, especially on Flatpak/Snap. Offer to run it first.| Install type | Per-user plugin dir |
|---|---|
| native (apt/dnf/pacman) | ~/.config/obs-studio/plugins/<plugin-name>/bin/64bit/ (binary) and ~/.config/obs-studio/plugins/<plugin-name>/data/ (assets) |
| Flatpak | ~/.var/app/com.obsproject.Studio/config/obs-studio/plugins/<plugin-name>/... |
| Snap | Strict confinement blocks most third-party plugins. Warn the user; they may need to switch to native or Flatpak. |
| AppImage | Per-user dir as native, but plugin must match the AppImage's bundled OBS ABI. |
System-wide install (/usr/lib/.../obs-plugins/) requires sudo and is not the default — only do it on explicit request.
Accept any of:
.deb, .tar.gz, .zip).https://github.com/<owner>/<repo>) — fetch the latest release via gh release view --repo <owner>/<repo> and pick the Linux asset matching the install type.Confirm OBS is not running.
Download / locate the artifact. Verify checksum if the release page publishes one.
Inspect the artifact:
file <artifact>
tar -tzf <artifact> | head -30 # for tarballs
unzip -l <artifact> | head -30 # for zips
dpkg -c <artifact> | head -30 # for debs
Flag anything suspicious (writes outside the plugin dir, setuid bits, unexpected absolute paths) and stop for user confirmation.
Install per artifact type:
.deb (native only, Debian/Ubuntu): sudo apt install ./<file>.deb — apt resolves any system deps.~/.config/obs-studio/plugins/.cp -r.Verify the binary lands at <plugin-dir>/<plugin-name>/bin/64bit/<plugin>.so.
Set permissions: chmod 644 on .so and data files, 755 on directories.
Tell the user to restart OBS, and to check Help → Log Files → View Current Log for plugin-load errors after restart.
Useful plugins worth mentioning when the user asks "what should I install":
Always link to the plugin's official GitHub release page rather than third-party mirrors.
To remove a plugin: stop OBS, delete the <plugin-dir>/<plugin-name>/ folder, restart OBS. For .deb installs, use sudo apt remove <pkg> instead.