Video Production Diagnostics

What it does

Guides diagnosis of technical video and audio issues (exposure, focus, color, noise, levels) by directly analyzing the file with available analysis tools, cross-referencing findings against the real hardware setup used during recording. It never assumes a cause without checking the file.

When to use it

• When a recorded video looks or sounds off and you don't know if it's the camera, the audio, or the edit.
• When you want to improve camera settings before the next recording.
• When producing recurring video content and need a consistent quality checklist.

Steps

1. Gather the video/audio file and the hardware setup data used.
2. Run technical analysis on the file (exposure, focus, audio levels, noise).
3. Compare findings against the reported camera and microphone setup.
4. Identify the most likely root cause, never assuming without file evidence.
5. Propose concrete setting adjustments for the next recording.
6. Document the diagnosis for future reference.

The skill

---
name: video-production-diagnostics
description: Diagnoses technical video/audio problems and camera settings by analyzing the actual file, cross-referenced with the hardware setup.
---

# Video Production Diagnostics

## What it does
Analyzes a real video or audio file to diagnose technical issues (exposure, focus, color, noise, levels) and cross-references them with the reported hardware setup, without assuming causes without evidence.

## When to use it
Use it when a recorded video has noticeable quality issues, or when you want to fine-tune camera and audio settings before the next recording session, including product demo or GoHighLevel tutorial recordings.

## Gathering evidence
1. Gather the original file and the hardware data used (camera, lens, microphone, lighting).

## Technical analysis
2. Analyze exposure, focus, and color balance of the video.
3. Analyze audio levels, noise, and clarity.

## Diagnosis
4. Cross-reference analysis findings with the reported setup to identify the most likely cause.
5. A cause is never assumed without the file analysis backing it up.

## Recommendations
6. Propose concrete camera or audio setting adjustments for the next recording.

## GoHighLevel angle
7. For GHL demo videos that will be reused across multiple clients, the quality diagnostic runs before approving the video as reusable material.

## Safety rules
1. Every deliverable (script, email, post, ad, design) is produced as a draft first.
2. Nothing is sent, published, or paid for without explicit human approval.
3. Never invent metrics, testimonials, customer names, or data not present in the provided sources.
4. No credential, API key, or token is ever written or pasted into chat; reference environment variables instead.

For Claude Code, save it as ~/.claude/skills/video-production-diagnostics/SKILL.md. In Cursor, ChatGPT or another assistant, paste it as project instructions.