streaming-obs-bootstrap

Rebuild and validate a reusable OBS streaming scene pack via agentic-obs and mcporter. Use when setting up or migrating streaming scenes (local or remote OBS...

Security Scan

The skill appears to implement the described OBS scene rebuild workflow, but there are a few inconsistencies and exposure risks (serving the entire workspace over HTTP, undocumented binary requirements, and direct DB updates) you should understand before running it.

Purpose & Capability

Name/description match the provided scripts and assets: the skill rebuilds OBS scenes via mcporter/agentic-obs and serves browser-overlay HTML. However, the skill metadata declares no required binaries or env vars while the scripts clearly assume mcporter, sqlite3 and python3 are present and will write into an agentic-obs SQLite DB (default $HOME/.agentic-obs/db.sqlite). The mismatch (declared requirements none vs. actual script dependencies) is an inconsistency to be aware of.

Instruction Scope

SKILL.md is specific and scoped to rebuilding scenes and running smoke tests, which matches the scripts. But start_overlay_server.sh launches a simple HTTP server that serves the entire workspace directory (default) on the LAN (port 8787), which can unintentionally expose any files in your workspace. obs_target_switch.sh directly updates the agentic-obs SQLite config (obs_host/obs_port), modifying another component's configuration file. Control-panel.html references a local screenshot endpoint (127.0.0.1:8765) that is not provided by the skill. These behaviors are within the claimed purpose but increase the attack surface and potential for accidental data exposure.

Install Mechanism

This is an instruction-only skill (no install spec), so nothing is downloaded or installed by the registry. That lowers supply-chain risk. However, the bundled scripts are executable and expect external binaries (mcporter, sqlite3, python3). The absence of an install step or declared binary requirements is a practical mismatch — the scripts can fail or behave unexpectedly if those tools aren't present or are different versions.

Credentials

The skill declares no required env vars or credentials, and it doesn't request secrets. Scripts reference optional env vars (OBS_AUDIO_INPUTS, MIC_DB, DESKTOP_DB, AGENTIC_OBS_DB, OPENCLAW_WORKSPACE, OVERLAY_PORT). The most impactful is AGENTIC_OBS_DB defaulting to $HOME/.agentic-obs/db.sqlite: the scripts will modify that DB if present. While that is relevant to the skill's purpose, it is privileged in the sense of altering another component's configuration and should be noted/confirmed.

Persistence & Privilege

always:false and normal autonomous invocation are used. The skill does modify the agentic-obs DB and writes a log and may create a streaming-tests directory under the workspace; it does not request permanent 'always' presence or modify other skills' configs. Modifying the agentic-obs DB is expected for setting target host/port but is a persistent change to another system's configuration and should be done with consent.

What to consider before installing

This skill largely does what it says (rebuild scenes and attach overlays via mcporter/agentic-obs) but take these precautions before running it: - Review and confirm dependencies: ensure mcporter, sqlite3 and python3 are the expected binaries on your machine. The registry metadata does not declare these but the scripts call them. - Inspect and control the overlay server: start_overlay_server.sh serves your entire workspace over HTTP on a LAN port (default :8787). If you run it, make sure no sensitive files are inside the workspace or run the server from a restricted or temporary directory. Consider using a reverse-proxy with auth or a firewall rule to limit access. - Back up agentic-obs DB: obs_target_switch.sh updates the agentic-obs SQLite DB (default $HOME/.agentic-obs/db.sqlite). Back up that DB before running or set AGENTIC_OBS_DB to a test DB to avoid accidental misconfiguration. - Run in an isolated/test environment first: rebuild/test the scenes and smoke-run in a staging VM or container to confirm behavior and side effects. - Check external endpoint expectations: the control panel references a local screenshot service (127.0.0.1:8765) that this skill does not provide — ensure that service is intentional and safe. If you want me to, I can produce a checklist of exact commands to run to test this skill safely (create a isolated workspace, set AGENTIC_OBS_DB to a temp DB, and run the scripts step-by-step).

Use this skill to quickly stand up a consistent streaming scene set on OBS and verify it with recording walkthroughs.

Prerequisites

• mcporter installed and configured with obs MCP server
• OBS WebSocket enabled on target host (default port 4455)
• Overlay files present in workspace (streaming/overlays)

Workflow

1. Set target OBS host (local or LAN host)
2. Start workspace HTTP server for overlays (LAN reachable)
3. Rebuild baseline scene pack
4. Attach overlay browser sources
5. Apply transition preset and optional audio baseline
6. Run recording smoke walkthrough and optional stream dry-run
7. Share output path and any troubleshooting notes

Commands

Run from workspace root.

# 1) Target OBS host
./skills/streaming-obs-bootstrap/scripts/obs_target_switch.sh <obs-host-ip> 4455

# 2) Start/verify overlay host server
./skills/streaming-obs-bootstrap/scripts/start_overlay_server.sh

# 3) Rebuild scenes + attach overlays
./skills/streaming-obs-bootstrap/scripts/rebuild_scenes.sh

# 4) Apply transition preset
./skills/streaming-obs-bootstrap/scripts/apply_transition_preset.sh Fade 300

# 5) Optional audio baseline (set OBS_AUDIO_INPUTS first)
# export OBS_AUDIO_INPUTS="Mic/Aux,Desktop Audio"
./skills/streaming-obs-bootstrap/scripts/apply_audio_baseline.sh

# 6) Run walkthrough recording (default 7s/scene)
./skills/streaming-obs-bootstrap/scripts/smoke_test_walkthrough.sh

# 7) Optional stream dry-run (default 15s)
./skills/streaming-obs-bootstrap/scripts/stream_dry_run.sh 15 "Intro" "Main Live"

Notes

• Never use /tmp for persistent overlay assets.
• Prefer http://<agent-lan-ip>:8787/... browser source URLs over file:// for remote OBS.
• Ensure HTML files declare UTF-8 and emoji-capable font stacks.

Troubleshooting

See:

• references/troubleshooting.md
• references/networking.md
• references/scene-map.md
• references/v0.2-features.md