Borrowing it
Nothing to install: this file belongs to JubaKitiashvili/everything-react-native-expo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/JubaKitiashvili/everything-react-native-expo/main/.claude/skills/debug-video/SKILL.mdgit clone --depth 1 https://github.com/JubaKitiashvili/everything-react-native-expoWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/jubakitiashvili/everything-react-native-expo/debug-video)<a href="https://agentmods.dev/skills/jubakitiashvili/everything-react-native-expo/debug-video"><img src="https://agentmods.dev/badge/skills/jubakitiashvili/everything-react-native-expo/debug-video/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/jubakitiashvili/everything-react-native-expo/debug-video"><img src="https://agentmods.dev/badge/skills/jubakitiashvili/everything-react-native-expo/debug-video.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00047 | $0.01094 |
| Opus 5 | $0.00023 | $0.00547 |
| Sonnet 5 | $0.00009 | $0.00219 |
| Haiku 4.5 | $0.00005 | $0.00109 |
Grade A, and why
debug-video scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/debug-video — Video Visual Debugging
You are executing the /debug-video command. Extract key frames from a video recording and use the visual-debugger agent for temporal UI analysis.
Arguments
/debug-video <video-file> — analyze a screen recording
/debug-video <video-file> --max-frames 15 — limit extracted frames (default: 20)
/debug-video <video-file> --description "button disappears after tap" — with context
Supported Formats
All video formats supported: .mp4, .mov, .webm, .avi, .mkv, .gif
Process
Step 1: Extract Key Frames
Run the frame extractor:
node scripts/extract-video-frames.js "<video-path>" --max-frames 20
This outputs JSON with frame paths. If ffmpeg is not found, show the user install instructions from the error output.
Duration guidance:
- ≤ 30 seconds: optimal, full detail analysis
- 30-60 seconds: key moments only, still effective
-
60 seconds: warn user to trim to the relevant section
Step 2: Read All Extracted Frames
Read EVERY extracted frame image file using the Read tool. The frames are ordered chronologically — frame_001 is earliest, frame_N is latest.
Step 3: Temporal Analysis
Analyze the frames as a timeline, not individual screenshots. Look for:
| Category | What to Look For |
|---|---|
| Animation bugs | Element position/size changes unexpectedly between frames |
| Race conditions | Loading → content → loading again, or flash of wrong content |
| Gesture issues | Drag/swipe stuck mid-motion, element not following finger |
| Scroll jank | Content jumping, blank areas during scroll, inconsistent spacing |
| Keyboard overlap | Input hidden behind keyboard after tap sequence |
| Navigation glitches | Flash of wrong screen, transition tearing, double-render |
| Layout shifts | Content moving/resizing after data loads |
| State bugs | UI showing stale data, toggle not reflecting state |
| Disappearing elements | Element visible in frame N, gone in frame N+1 |
| Z-index issues | Element appearing behind/above where it shouldn't |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 134 lines · 47 tokens per session scan A 9c899ad494a6
debug-video is a skill published in the GitHub repository JubaKitiashvili/everything-react-native-expo (45 stars, last pushed 5mo ago), licensed MIT. It adds 47 tokens to every session and 1,094 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.