plugins/multimedia/skills/format-explain/SKILL.md
This skill should be used when the user asks "what does this mediainfo mean", "explain this video format", "what is BT.709", "what is H.264", "container vs codec", "why is this 10bit", "what does limited range mean", or wants educational explanations of video technical concepts.
npx skillsauth add robbyt/claude-skills format-explainInstall 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.
Provide clear, educational explanations of video technical concepts. Route to detailed references for in-depth information.
Container formats (mkv, mp4, webm, avi, mov):
Video codecs (H.264/AVC, H.265/HEVC, VP9, AV1):
Key insight: A file's extension (.mkv, .mp4) tells you the container, not the codec. An mkv and mp4 can contain identical H.264 video.
Codec/Format (H.264, H.265): The specification/standard for how video is encoded Encoder (x264, x265, NVENC): Software that creates video in that format
Different encoders produce different quality at same bitrate:
What it is: Pixel dimensions (1920x1080, 3840x2160) What it's not: Quality
Resolution indicates the pixel grid size, not visual fidelity. A badly encoded 4K video can look worse than a well-encoded 1080p video.
Native vs upscaled: Many "4K" releases are upscaled from lower resolution masters. The file has 4K pixels but no more detail than the source.
Common rates:
23.976 vs 24: Nearly identical to viewers. The fractional rate exists for NTSC compatibility reasons from analog TV era.
CFR vs VFR:
8-bit: Standard, 256 levels per color channel, 16.7 million colors 10-bit: HDR standard, 1024 levels per channel, 1 billion+ colors 12-bit: Professional/mastering, rarely seen in distribution
10-bit for 8-bit content: Encoders sometimes use 10-bit encoding for 8-bit sources because it improves compression efficiency (fewer banding artifacts).
What it measures: Data per second (Mbps, kbps) What it indicates: How much data the encoder used, not necessarily quality
Higher bitrate ≠ better quality. An inefficient encode at 20 Mbps can look worse than an efficient encode at 8 Mbps.
VBR vs CBR:
Quality-based encoding setting used by x264/x265:
CRF automatically adjusts bitrate based on scene complexity.
Defines how YCbCr values convert to/from RGB:
Wrong matrix = incorrect colors. HD content played as BT.601 will have shifted hues.
Limited range (16-235): Standard for video, leaves headroom Full range (0-255): Uses entire value range
Most video content is Limited range. Playing Limited as Full = washed out. Playing Full as Limited = crushed blacks/clipped whites.
4:4:4: Full color resolution (rare, large files) 4:2:2: Half horizontal color resolution (professional) 4:2:0: Quarter color resolution (standard for distribution)
Human eyes are less sensitive to color detail than brightness, so 4:2:0 looks nearly identical to 4:4:4 for most content.
SDR (Standard Dynamic Range): Traditional brightness levels, ~100 nits peak HDR (High Dynamic Range): Extended brightness, 1000+ nits peak, wider color gamut
HDR requires:
Not all "HDR" releases are legitimate. Some are inverse tonemapped from SDR sources.
| Question | Short Answer | |----------|--------------| | "Is mkv better than mp4?" | Different containers, neither is "better" - mkv supports more features | | "Should I reencode to H.265?" | Only if you need smaller files and accept quality loss | | "Is 4K always better than 1080p?" | No - depends on source quality and encoding | | "Why is my file so large?" | Check codec (NVENC vs x264), bitrate settings, or CRF value | | "What's the best format?" | Depends on use case. H.264/mkv for compatibility, H.265 for size |
For detailed explanations:
${CLAUDE_PLUGIN_ROOT}/references/quality-myths.md - Common misconceptions debunked${CLAUDE_PLUGIN_ROOT}/references/color-space.md - Full color space details${CLAUDE_PLUGIN_ROOT}/references/encoding-commands.md - Practical command examplestools
Real-time web research using Google Search via Google's Antigravity (`agy`) CLI — the replacement for the deprecated `gemini-cli`. Trigger when user needs current information ("search with agy", "search with Google Antigravity", "find current info about X with agy", "what's the latest on Y"), library/API research, security vulnerability lookups, or comparisons requiring recent data.
tools
Get Google Antigravity's (`agy`) review of Claude's implementation plans. Trigger when user wants a second opinion on a plan ("have agy review this plan", "get a second opinion from Google Antigravity", "critique this plan with agy"), or after Claude creates a plan file that needs validation before implementation. Replaces the deprecated gemini-cli plan-review workflow.
tools
Get Google Antigravity's (`agy`) code review of git changes after Claude makes edits. Trigger when user wants a second opinion on code changes ("have agy review my changes", "get code review from Google Antigravity", "review this diff with agy"), or as a final check before committing. Replaces the deprecated gemini-cli diff-review workflow.
tools
Deep architectural analysis of the current workspace using Google Antigravity (`agy`). Trigger when the user needs an architecture overview ("analyze this codebase with agy", "map dependencies with Google Antigravity"), is onboarding to unfamiliar code, exploring legacy systems, or hunting technical debt. Replaces the deprecated gemini-cli `codebase_investigator` workflow.