Menu
Use when the user wants to convert a video or audio file's stereo audio to mono, or fix audio that only plays in one ear.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| disable-model-invocation | true |
| name | convert-audio-mono |
| description | Use when the user wants to convert a video or audio file's stereo audio to mono, or fix audio that only plays in one ear. |
This skill converts the stereo audio channel of a media file (typically video or audio) to mono. It optimizes the process by copying the video stream without re-encoding to preserve video quality, and handles silent channels by extracting the active channel rather than a simple downmix.
Use when a video or audio file's sound plays in only one ear/channel, or when a mono mix is requested.
ffmpeg -i <input> -filter_complex "[0:a]astats=metadata=1" -f null - to identify the peak and RMS volume of each channel.
Note: Do not use reset=1 in the filter, as it resets stats per frame.-af "pan=mono|c0=c0" (or FL)-af "pan=mono|c0=c1" (or FR)-ac 1ffmpeg -i <input> -c:v copy -af "<filter>" -c:a aac -b:a 256k <output>-c:v copy.-ac 1 downmix of a one-eared track averages it with silence, dropping the overall volume by 6 dB. Always analyze first and use the pan filter for single-channel isolation.Explain the core concepts, library design patterns, system architecture, or host environment internals involved in a plan or git diff.
Glossary: capture stable, repository-wide terms and concepts in `.jai/glossary.md` when they emerge. Use when a term or concept should become canonical repository context.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Review open GitHub pull requests for mergeability. Use when you want a triage verdict on PRs created on mobile or without careful review. Pass a PR number to review one PR, or no argument to review all open PRs in parallel.
Capture an Architecture Decision Record (ADR) for a significant decision made in the current project. Store in the project's adrs/ folder. Use when the user asks to record a decision, log an ADR, or capture why something was built a certain way. PROACTIVELY suggest capturing an ADR whenever a non-obvious architectural choice is made — technology selection, structural trade-offs, rejected alternatives — especially after a discussion where context and reasoning were developed. A good prompt — "Want me to capture this as an ADR?"
Aggressive maintainability review focused on structural simplification, deleting complexity, type safety compiler soundness, resource leaks, accessibility, localization, and concurrency. Activate this skill ANY TIME the user asks for a code review or when you need to perform a senior-level, thorough analysis of code changes.