Skip to content This library is free, offered as dana. If it helps your work, donate here →
penguin tree ai
← back to libraryDonate here

This is one of 3,622 free prompts in the penguin tree ai library. Sign up once and the whole library opens, with new prompts by email.

open the library →

AV system troubleshooting guide builder

Generates hardware-specific AV troubleshooting documentation covering symptom-to-cause diagnostic trees, tiered escalation paths, room-type quick-fix cards, and end-user vs. technician instruction sets for platforms…

download .md

Purpose

Produce a hardware-specific troubleshooting guide that maps real AV failure symptoms to root causes and step-by-step fixes — organized by escalation tier and split into end-user and technician versions — so support tickets resolve faster and fewer failures reach the AV team. Eliminates the tribal-knowledge problem where only one person knows how to fix a given room.

When to Use

Invoke this skill when the user asks to:

  • Document how to troubleshoot a specific AV platform (Crestron, Extron, Q-Sys, Shure, Logitech, Neat)
  • Build a support runbook for conference rooms, boardrooms, or huddle spaces
  • Create end-user "no video / no audio / can't join" quick-fix instructions
  • Standardize AV incident response and escalation across a support team
  • Reduce repeat AV tickets by giving front-line staff a diagnostic reference
  • Onboard new IT/AV staff with room-specific fix procedures

Inputs Required

Before starting, collect:

  • AV platform(s): Primary control/audio/video systems in scope (e.g., Crestron control + Shure ceiling mics + Logitech Rally)
  • Room type: Huddle room / medium conference / boardroom / classroom / auditorium
  • Meeting platform: Zoom Rooms / Microsoft Teams Rooms / Google Meet / mixed
  • Displays and I/O: Display type, input sources (HDMI, USB-C, wireless), and connection method
  • Support tiers available: Who handles Tier 1 (end user/receptionist), Tier 2 (IT), Tier 3 (AV specialist/vendor)
  • Common failure history: Any recurring issues this room or fleet already experiences
  • Access to tools: Whether staff have access to control processor web UI, Q-Sys Designer, DSP config, or vendor portals

If failure history is not provided, cover the standard high-frequency failure set for the platform and note the assumption.

Instructions

Step 1: Build the Symptom Index

List the failure symptoms exactly as an end user reports them — not as an engineer diagnoses them. Group into five categories:

  • No display / no video: Blank screen, wrong input, flickering, "no signal"
  • No audio / audio quality: No far-end audio, echo, low mic volume, feedback, dropouts
  • Camera / video conferencing: No camera, frozen video, wrong framing, camera not detected
  • Control / room system: Touch panel unresponsive, room won't wake, controls do nothing
  • Connectivity / meeting join: Can't start or join, calendar not syncing, device offline

Each symptom becomes an entry in the diagnostic tree in Step 2.

Step 2: Write Symptom-to-Cause Diagnostic Trees

For each symptom, build a decision tree with this structure:

  1. First check (30 seconds): The single most common cause and its fix (e.g., wrong source selected, cable unseated, display powered off)
  2. Second check: Next most likely cause with a yes/no branch
  3. Third check: Platform-specific check using the actual hardware (e.g., verify signal on the Extron switcher front panel, check mic mute LED on Shure, confirm device status in Logitech Sync)
  4. Escalate if: The exact condition that means Tier 1 should stop and escalate

Use real platform terminology and interface locations — name the actual menus, LEDs, ports, and status indicators the technician will see. Never write "check the settings" without saying which settings and where.

Step 3: Define Escalation Tiers

Map each fix to a tier and state the handoff clearly:

  • Tier 1 (End user / front desk): Physical checks, power cycles, source selection, mute toggles — nothing requiring credentials or config tools
  • Tier 2 (IT support): Device reboots via admin portal, network/DNS checks, meeting-platform account issues, firmware status, cable/adapter replacement
  • Tier 3 (AV specialist / vendor): DSP/gain structure changes, control programming, matrix routing config, hardware RMA, Q-Sys/Crestron code For each escalation, specify what information Tier 1/2 must capture before handing off (room ID, symptom, steps already tried, timestamps).

Step 4: Create Quick-Fix Cards

Produce 6–10 one-line quick-fix cards for the highest-frequency issues — each in the format: Symptom → Do this → If it still fails, escalate to [tier]. These are laminate-ready references for the room or help desk.

Step 5: Split Into End-User and Technician Versions

  • End-user version: Plain language, no jargon, physical actions only, maximum 4 steps per issue, reassuring tone
  • Technician version: Full diagnostic trees, interface paths, config references, escalation criteria, and information-capture requirements

Step 6: Add Preventive Maintenance & Room Health Checks

List a short recurring checklist (daily/weekly/monthly) specific to the platform — firmware currency, cable inspection, mic/camera test, calendar sync verification, control processor uptime.

Output Format

  • Structure: Symptom index → diagnostic trees by category → escalation tier matrix → quick-fix cards → end-user version → technician version → preventive maintenance
  • Length: 1,100–1,600 words
  • Format: Structured document — numbered diagnostic steps, a tier matrix table, and card-style quick fixes
  • Sections: Symptom Index, Diagnostic Trees (5 categories), Escalation Tier Matrix, Quick-Fix Cards, End-User Guide, Technician Guide, Preventive Maintenance
  • Tone: AV operations lead — precise, procedural, action-first; assumes the reader is standing in front of the equipment

Quality Checklist

Before delivering output, verify:

  • [ ] Every symptom is phrased as an end user would report it, not as an engineer would diagnose it
  • [ ] Each diagnostic tree includes a specific "escalate if" condition — not open-ended
  • [ ] Platform-specific interface elements are named (actual menus, LEDs, ports, portals) — no vague "check the settings"
  • [ ] Each fix is assigned to Tier 1, 2, or 3, and Tier 1 fixes require no credentials or config tools
  • [ ] At least 6 quick-fix cards use the Symptom → Do this → Escalate format
  • [ ] End-user steps contain no jargon and cap at 4 steps per issue

Notes

  • The most common AV ticket is "no far-end audio" or "wrong input" — front-load these in the quick-fix cards for maximum ticket deflection
  • Always capture "steps already tried" at escalation; the single biggest time waste is Tier 2 repeating Tier 1's checks
  • If the room mixes vendors (e.g., Crestron control over a Q-Sys DSP with Shure mics), note the integration boundaries — most confusing failures happen where two systems hand off signal
  • Keep the end-user version and technician version as clearly separate documents; mixing them causes end users to attempt config changes they shouldn't touch

How to use this skill

This file is a Claude Code skill in Anthropic's standard format — markdown with YAML frontmatter at the top.

Installing in Claude Code:

  • ~/.claude/skills/<folder-name>/SKILL.md — auto-loads in every session anywhere on your machine (recommended for skills you'll use across multiple projects)
  • <your-project>/.claude/skills/<folder-name>/SKILL.md — auto-loads only when working in that project (recommended for project-specific skills)

Restart Claude Code or open a new session to register.

Using in Claude.ai, ChatGPT, Gemini, or other AI tools:

  1. Drag this file into a new chat, or copy and paste its contents
  2. Send your task or request as your next message — the AI will apply the skill where it fits

For Claude Code skill details: https://docs.anthropic.com/en/docs/claude-code/skills