一键导入
overcast-media-bug-triage
Analyze screen recordings, product demos, customer support videos, and audio notes into actionable, cited bug reports for coding agents.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Analyze screen recordings, product demos, customer support videos, and audio notes into actionable, cited bug reports for coding agents.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | overcast-media-bug-triage |
| description | Analyze screen recordings, product demos, customer support videos, and audio notes into actionable, cited bug reports for coding agents. |
Use this skill when media evidence should become a bug report, reproduction
steps, or engineering triage notes. Use the broad overcast skill and
overcast/reference/verbs.md for exact command flags.
overcast doctor --json
overcast case init --json
overcast case setup --yes --json
overcast watch ./screen-recording.mp4 --json
overcast listen ./screen-recording.mp4 --describe --json
overcast see frame://<record-id>@<seconds> --ocr --json
overcast note "observed UI state or suspected failure" --ref <record-id> --at <time-range> --json
overcast ask "summarize the bug with reproduction steps and citations" --json
overcast brief --full --export ./bug-brief.md --json # --full: this flow wants the verbatim evidence timeline (the default brief is short)
Use watch for screen recordings and demos. Add listen --describe when
spoken narration, audio cues, or support-call context matters. Use see --ocr
on key frames when UI text, error messages, button labels, or form values are
important.
Produce a cited bug summary with:
record.id and media.at;see --ocr;Keep observed media facts separate from engineering inference. Add human
observations with note. Prefer ask and brief for synthesis; use
case memory get to page large watch or listen fields when exact
timeline text is needed.
Give any agent senses (video/audio/image understanding) and OSINT reach (search/capture/monitor) organized around an investigation case. Use when the user wants to analyze a video/audio/image, scan or monitor sources for a target, or ask/brief over accumulated findings. Drives the `overcast` CLI (built on pi + the tinycloud/Cloudglue perception backend); see reference/verbs.md for the full verb surface.
Install and configure overcast for this harness: install the CLI, verify the system ffmpeg, and configure reusable provider profiles. Use once per machine/profile before driving the `overcast` skill.
Turn a case into a visual evidence board — materialize face and object crops, link the same person across clips, connect themes, and render the corkboard as a CSI brief plus a live monitor wall.
Make unreadable footage legible — denoise/upscale a marked moment, re-run OCR and detection on the enhanced output, and record what was recovered with honest provenance (interpolation is a lead, not proof).
Work out where a photo or clip was taken — check embedded EXIF/GPS first, then pull signage, landmarks, and terrain clues, reverse-image-search the strongest ones, and corroborate to a location with cited evidence.
Run a standing surveillance watch on public sources for a target — auto-sense new media, auto-suggest matches into a triage queue, and keep a live control-room wall — so new evidence surfaces itself over time.