skills/obs-stream-setup/SKILL.md
Generate OBS stream overlay assets (background, overlay, starting-soon, BRB screens) and configure OBS scenes via WebSocket. Use when the user asks to set up OBS, create stream overlays, design a live stream layout, make their stream look nicer, or mentions OBS scenes/sources. Also trigger when the user says "set up my stream", "create stream graphics", "OBS overlay", or wants branded live stream assets.
npx skillsauth add razbakov/skills obs-stream-setupInstall 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.
Generate a complete OBS stream package: HTML/CSS overlay assets rendered to PNG, then programmatically configure OBS scenes via WebSocket API.
4 HTML source files (editable, re-renderable):
overlay.html — transparent overlay with top bar, camera frame, lower third, LIVE badge, social handlesbackground.html — dark gradient background with geometric grid patternstarting-soon.html — pre-stream waiting screenbrb.html — break screen4 PNG assets (1920x1080):
obs-overlay.png — transparent PNG for layeringobs-background.png — solid backgroundobs-starting-soon.png — starting soon screenobs-brb.png — BRB screen3 OBS scenes (configured via WebSocket):
Before generating, ask for (or use defaults):
| Input | Example | Default |
|-------|---------|---------|
| Stream title | User-specified | required |
| Streamer name | From CLAUDE.md Personal Info | required |
| Subtitle | User-specified | required |
| Social handle | From CLAUDE.md Personal Info | required |
| Platform labels | "YouTube", "GitHub" | YouTube, GitHub |
| Color scheme | dark blue/purple | #0a0a14 → #1a1a3e, accent #7c4dff |
| Layout split | 65/35 | 65% screen, 35% camera |
mkdir -p <project>/obs-assets
Create 4 HTML files using the templates below. Replace placeholders with user inputs.
Key layout dimensions (1920x1080 canvas):
Top bar: y=0, h=56
Screen area: x=16, y=66, w=1224, h=940
Camera area: x=1264, y=66, w=640, h=940
Bottom bar: y=1032, h=48
Transparent background (background: transparent). Contains:
The overlay uses background: transparent on body so it renders as a transparent PNG and works as an OBS Browser Source.
Dark gradient background with:
Centered layout with:
Same as starting-soon but with:
cd <project>/obs-assets
npm install --no-save puppeteer obs-websocket-js
Create render.mjs:
import puppeteer from 'puppeteer';
import { fileURLToPath } from 'url';
import { dirname, join } from 'path';
const __dirname = dirname(fileURLToPath(import.meta.url));
async function render(htmlFile, outputFile, transparent = false) {
const browser = await puppeteer.launch({ headless: 'new' });
const page = await browser.newPage();
await page.setViewport({ width: 1920, height: 1080, deviceScaleFactor: 1 });
await page.goto(`file://${join(__dirname, htmlFile)}`, { waitUntil: 'networkidle0' });
await page.screenshot({
path: join(__dirname, outputFile),
omitBackground: transparent,
fullPage: false,
});
await browser.close();
console.log(`Rendered: ${outputFile} (transparent: ${transparent})`);
}
await render('overlay.html', 'obs-overlay.png', true);
await render('background.html', 'obs-background.png', false);
await render('starting-soon.html', 'obs-starting-soon.png', false);
await render('brb.html', 'obs-brb.png', false);
console.log('Done!');
Run: node render.mjs
The omitBackground: true flag is critical for the overlay — it produces a transparent PNG that OBS can layer on top of video sources.
OBS 28+ has a built-in WebSocket server. The setup script needs the password from the OBS config.
Read the password:
cat ~/Library/Application\ Support/obs-studio/plugin_config/obs-websocket/config.json
If the WebSocket server isn't enabled, tell the user: "In OBS, go to Tools → WebSocket Server Settings → Enable WebSocket Server"
Create setup-obs.mjs that:
ws://127.0.0.1:4455 with the passwordobs-background.png, stretched to 1920x1080macOS Screen Capture) — positioned at x=16,y=66, bounded 1224x940Camera) — positioned at x=1264,y=66, bounded 640x940overlay.html, 1920x1080 (browser source enables CSS animations like LIVE badge pulse)The script is idempotent — running it again updates transforms instead of duplicating sources.
Open the generated PNGs for the user to preview. Show the overlay and background separately so they can confirm the layout before applying to OBS.
| Role | Value |
|------|-------|
| Background dark | #0a0a14 |
| Background mid | #1a1a3e |
| Background light | #2d1b4e |
| Accent | #7c4dff |
| Accent light | #b388ff |
| Text primary | #e0e0f0 |
| Text muted | rgba(180, 170, 220, 0.8) |
| LIVE badge | #e53935 |
| Borders | rgba(120, 80, 220, 0.3-0.5) |
Edit the HTML files and re-render:
node render.mjs
The overlay in OBS uses a Browser Source pointing to overlay.html, so changes to the HTML take effect after refreshing the browser source in OBS (right-click → Refresh cache).
development
Seed a new or empty Instagram account with a 9-post grid (3×3) so the profile looks established the moment a new visitor lands. Designed for festivals, new businesses, product launches, conferences, communities — any time an empty IG profile would hurt conversion from external traffic (QR scans, flyer drops, cross-promo). Generates assets via /image-from-gemini (per content-publishing rules — never HTML), writes captions with hashtag sets, and outputs a posting order + cadence plan. Trigger generously: phrases like '9 posts for instagram', 'fill my IG', 'starter grid', 'launch grid', 'instagram seed', '9-post grid', 'IG account not to look empty', 'first instagram posts', 'feed bootstrap', '3x3 grid', 'instagram launch content'. Even if the user mentions only one piece (just the images, just the captions, just the order), use this skill — the grid only works as an integrated bundle.
testing
Translate one English blog post into multiple target languages via parallel sub-agents, preserving frontmatter conventions, hero image, and brand voice. Use when the user shares a published English post URL or markdown path and says 'translate it', 'add other languages', 'publish in DE/ES/RU/UK', 'translate to 5 languages', or asks for localized versions of a specific post.
development
Build a complete press kit for an event, product launch, or campaign — in multiple languages — and publish it as a shareable Google Drive folder ready to send to journalists, partners, or a delegate. Produces press releases (typically DE/EN/ES, or configurable), uploads press photos and flyers, creates an Overview document for at-a-glance briefing, and creates a Handover document with pending tasks, contacts, risks, and decisions so press distribution can be delegated. Use when the user says 'I need a press release', 'create a press kit', 'press release in X languages', 'set up a Drive folder for press', 'handover doc for someone else to run press', or has an upcoming announcement that needs to be sent to media. Trigger generously: even partial requests (just a press release, just a flyer folder) typically evolve into the full kit.
development
Track ticket sales for a live event (concert, festival, conference, workshop) with daily snapshots, generate a burndown chart comparing actual sales to ideal-linear targets and tier-cumulative milestones, and report whether the event is on pace. Use when the user asks how sales are going, wants to know if their event will sell out, asks for a daily sales report, wants to set up sales tracking for an upcoming event, or asks about ticket pace / velocity / projection. Trigger generously: phrases like 'how is concert sales going', 'burndown for my event', 'are we going to sell out', 'sales velocity', 'daily ticket chart', 'how many tickets do we need to sell', or any case where the user has a ticketed event with a fixed sales window and wants visibility on pacing.