Offered by Dead Brands
A short, checkable list of real stream problems — nothing guessed, nothing inflated.
Use it over MCP: connect to https://mcp.deadbrands.co/hub/mcp and call skills_get with slug stream-watch-eyes.
# Stream-Watch Eyes
- Version: 1.0
- Date: 2026-10-21
- Status: experimental science
## Purpose
This skill watches a live bot-game stream like a careful spectator: eyes on picture, gameplay, sound, and buffering, noting only problems that can actually be checked. It never guesses or diagnoses a server. Each event gets a timestamp, a visible symptom, and a duration, so a human can verify it from the recording.
## Superpower
A short, checkable list of real stream problems — nothing guessed, nothing inflated.
## When to use
- During a scheduled live bot-game stream, as a dedicated watching shift.
- When spectators report freezing, silence, or a broken game view.
- For a short review of a recorded stream segment.
## When NOT to use
- Never watch a real person's private stream, camera, or personal account.
- Never monitor people, collect viewer identities, or track chat users.
- Never use it during a match you are also playing, refereeing, or scoring.
- Never substitute it for a human decision about taking a stream down.
## Tools & APIs
- The stream's public viewing page, watched as a spectator.
- A local watch log: plain text, one line per event.
- A clock and stopwatch for timestamps and durations.
- Planned, not yet available: a stream-event checklist form (time, symptom, duration, severity). Not an existing server tool.
- No login bypass, viewer-data collection, or automated stream control.
## Inputs
- Stream identifier and scheduled start time.
- Expected game(s) on screen.
- Watch window and watcher name.
- Any spectator report to verify, quoted with its time if available.
## Outputs
- A watch log: one entry per event, with start time, symptom, duration, severity.
- A count by category: visual, gameplay, sound, buffering.
- Verification per spectator report: confirmed, not seen, unclear.
- A handoff line naming the single most urgent event, if any.
## Example invocation
> Watch the 18:00 stream for 30 minutes. Log every freeze longer than 5 seconds, every silent stretch longer than 10 seconds, and every moment the game view is missing or wrong. Report only events you saw, with timestamps.
## Steps
1. Note stream start, expected game, and watch window before watching.
2. Watch in 10-minute blocks, writing up each block immediately.
3. For each problem, record start time, plain-word symptom, and duration.
4. Classify it: visual (frozen, black, wrong scene), gameplay (stuck bots, wrong score), sound (silent, distorted, out of sync), or buffering (spinner, stutter).
5. Rate severity: minor, major, or critical (stream unwatchable).
6. Count events by category, verify spectator reports, hand off the worst event first.
## Safety limits
- Report only what was seen/heard on the public stream, with timestamps.
- Never record viewer names, chat identities, or anything about spectators.
- Never claim a cause ("server down") when only a symptom ("black screen") was seen.
- Never touch stream controls, settings, or accounts while watching.
## Failure modes
- Multitasking produces vague entries with no usable timestamp.
- Lumping short freezes into one event inflates severity.
- Reporting a spectator's claim as confirmed without seeing it yourself.
- Chasing a cause instead of describing the symptom delays the handoff.
## Test checklist
- [ ] Every entry has start time, symptom, duration, category.
- [ ] No entry claims an unobserved cause.
- [ ] Buffering, sound, visual, gameplay counted separately.
- [ ] Each spectator report marked confirmed, not seen, or unclear.
- [ ] No viewer identity or private information in the log.