Evaluate any communication to identify where visual demonstration could replace verbal explanation.
Scanned 9/8/2026
Install to Claude Code
npx -y skills add sethmblack/paks-skills --skill visual-communication-audit --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Visual Communication Audit?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/sethmblack-visual-communication-audit)More formats (shields.io, HTML) on the badges page.
---
name: visual-communication-audit
description: Evaluate any communication to identify where visual demonstration could replace verbal explanation.
license: MIT
metadata:
author: sethmblack
version: 1.0.5282
repository: https://github.com/sethmblack/paks-skills
keywords:
- transformation
- visual-communication-audit
- writing
---
# Visual Communication Audit
Evaluate any communication to identify where visual demonstration could replace verbal explanation.
---
## When to Use
- Reviewing presentations, pitches, or proposals
- Improving documentation or training materials
- Designing product demos or walkthroughs
- Editing written content for clarity
- User asks "Am I showing or telling?" or "How can I make this more visual?"
---
## Inputs
| Input | Required | Description |
|-------|----------|-------------|
| content | Yes | The presentation, document, or communication to audit |
| medium | No | Slides, document, video, live presentation, etc. |
| constraints | No | Time, budget, technical limitations |
---
## Hitchcock's Pure Cinema Principle
Hitchcock learned filmmaking in the silent era. His principle:
**"When we tell a story in cinema, we should resort to dialogue only when it's impossible to do otherwise."**
He applied a simple test to every scene: *Would this work as a silent film?*
The opening of *Rear Window* tells you everything—the setting, the protagonist, his injury, his profession, the neighbors, the weather, the stakes—through camera movement alone. Not a word spoken.
**For any communication, ask:** If you removed all words, would the meaning survive?
---
## The Visual Hierarchy
### Level 1: Pure Visual
Meaning conveyed entirely through images, demonstrations, or diagrams.
- *Example:* Showing a before/after comparison instead of describing improvement.
- *Hitchcock:* The shower scene in Psycho—violence created through montage, never shown explicitly.
### Level 2: Visual-Primary
Images carry meaning; words support and label.
- *Example:* A chart with a clear trend, captioned with the key insight.
- *Hitchcock:* The crop duster sequence—minimal dialogue, maximum visual storytelling.
### Level 3: Visual-Supported
Words carry meaning; images illustrate and reinforce.
- *Example:* A slide with bullet points and a relevant image.
- *Hitchcock:* (Avoided this level when possible.)
### Level 4: Verbal-Only
Pure text or speech with no visual component.
- *Example:* A wall of text on a slide.
- *Hitchcock:* "The talking heads. The death of cinema."
**Goal:** Move as much content as possible toward Level 1 and Level 2.
---
## The Silent Film Test
For each element in your communication, ask:
1. **Can this be shown?**
- Physical demonstration
- Visual example
- Diagram or schematic
- Before/after comparison
- Video or animation
2. **Can this be implied through juxtaposition?**
- Kuleshov Effect: Meaning emerges from what's placed together
- Contrast creates understanding
- Sequence suggests causation
3. **Does this require explanation because the visual is unclear?**
- If yes, improve the visual—don't add words
- Words are patches for failed images
4. **Is this genuinely abstract?**
- Some concepts resist visualization
- These require words—but fewer than you think
- Even abstractions can have visual metaphors
---
## Audit Process
### Step 1: Inventory
List every element in the communication:
- Each point, claim, or idea
- Each transition or connection
- Each piece of supporting evidence
### Step 2: Classify Current State
For each element, identify:
- Current format (verbal, visual, or both)
- Current visual hierarchy level (1-4)
### Step 3: Apply the Test
For each verbal element, ask:
- Can this be shown instead?
- What would the visual version be?
- Why hasn't it been visualized?
### Step 4: Prioritize Conversions
Rank elements by:
- Impact of visual conversion (high = core message)
- Difficulty of conversion (low = quick wins)
- Current clarity (low = needs help most)
### Step 5: Recommend Specifics
For each priority conversion:
- Describe the current verbal version
- Describe the proposed visual version
- Note implementation requirements
---
## Workflow
### Step 1: Gather and Review Inputs
Collect all relevant information:
- Review the provided data and context
- Identify key parameters and constraints
- Clarify any ambiguities or missing information
- Establish success criteria
### Step 2: Analyze the Situation
Perform systematic analysis:
- Identify patterns and relationships
- Evaluate against established frameworks
- Consider multiple perspectives
- Document key findings
### Step 3: Generate Recommendations
Create actionable outputs:
- Synthesize insights from analysis
- Prioritize recommendations by impact
- Ensure recommendations are specific and measurable
- Consider implementation feasibility
## Output Format
```markdown
## Visual Communication Audit
### Overview
**Medium:** [Slides/Document/Video/etc.]
**Current Visual Level:** [Average hierarchy level 1-4]
**Target Visual Level:** [Recommended average]
**Conversion Opportunities:** [Number identified]
### Element Analysis
| Element | Current | Level | Can Visualize? | Recommended Visual |
|---------|---------|-------|----------------|-------------------|
| [Item] | Verbal/Visual | 1-4 | Yes/Partial/No | [Description] |
### Priority Conversions
#### High Priority
**Element:** [What it is]
**Current:** [How it's presented now]
**Problem:** [Why verbal is insufficient]
**Visual Solution:** [Specific recommendation]
**Implementation:** [What's needed to execute]
#### Medium Priority
[Same format]
#### Low Priority / Acceptable as Verbal
[Elements that genuinely require words, with justification]
### The Silent Film Version
[Brief description of how this communication would work with no words at all—what would survive?]
### Quick Wins
[Immediate changes requiring minimal effort]
### Hitchcock's Verdict
[Summary judgment on visual storytelling quality]
```
---
## Common Verbal-to-Visual Conversions
| Verbal Pattern | Visual Alternative |
|----------------|-------------------|
| "We grew 50%" | Chart showing growth curve |
| "The process has three steps" | Flowchart or diagram |
| "Customers love the product" | Video testimonial or quote card |
| "Here's how it works" | Live demonstration or animation |
| "The problem is complexity" | Screenshot of cluttered interface |
| "We're better than competitors" | Side-by-side comparison visual |
| "There's a significant risk" | Risk matrix or impact diagram |
| "Users struggle with X" | Heatmap or session recording |
| "Revenue breakdown" | Pie chart or treemap |
| "Timeline of events" | Visual timeline |
---
## Anti-Patterns to Eliminate
### The Descriptive Redundancy
Reading aloud what's written on the slide. The visual becomes decoration.
**Fix:** Either say it OR show it. Never both identically.
### The Stock Photo Placebo
Adding generic images that relate vaguely to the topic. "Teamwork" slide shows people high-fiving.
**Fix:** Every image should convey specific, relevant information. If it doesn't, remove it.
### The Data Fog
Showing complex charts without clear visual hierarchy. The audience must decode meaning.
**Fix:** Design charts for instant understanding. Highlight the one thing they should see.
### The Bullet Point Surrender
Defaulting to text bullets because "it's easier."
**Fix:** Each bullet is an admission that you haven't thought visually. Challenge every one.
---
## Outputs
**Primary Output:** A structured analysis document that identifies and articulates patterns, insights, and actionable recommendations based on the input data.
**Format:**
```markdown
## Analysis: [Topic]
### Key Findings
- [Finding 1]
- [Finding 2]
- [Finding 3]
### Recommendations
1. [Action 1]
2. [Action 2]
3. [Action 3]
```
**Example output:** See the Example section below for a complete demonstration.
## Constraints
- Do not use this analysis as the sole basis for critical decisions
- Do not apply this framework to situations outside its intended scope
- Acknowledge that analysis is based on available data, which may be incomplete
- Honor the complexity of real-world situations that resist simple categorization
- Present findings with appropriate confidence levels
- Recognize the limits of the methodology
## Example
**Input:** "Slide deck for quarterly business review. Current slide: 'Key Challenges - Our response times have increased 40%, customer satisfaction dropped 12 points, and support ticket volume is up 60%. We need to address root causes.'"
**Output:**
## Visual Communication Audit
### Overview
**Medium:** Presentation slide
**Current Visual Level:** 4 (Pure verbal—text only)
**Target Visual Level:** 2 (Visual-primary with supporting labels)
**Conversion Opportunities:** 3 key metrics + relationship story
### Element Analysis
| Element | Current | Level | Can Visualize? | Recommended Visual |
|---------|---------|-------|----------------|-------------------|
| Response time increase | Text: "+40%" | 4 | Yes | Line chart showing degradation over time |
| CSAT decline | Text: "-12 points" | 4 | Yes | Score gauge or trend line |
| Ticket volume | Text: "+60%" | 4 | Yes | Bar chart with volume by month |
| Root cause statement | Text sentence | 4 | Partial | Arrow diagram showing cause-effect |
### Priority Conversions
#### High Priority
**Element:** The relationship between metrics
**Current:** Three separate facts listed
**Problem:** Audience must mentally connect them; the story is invisible
**Visual Solution:** Single integrated visual showing the cascade:
- Ticket volume (cause) --> Response time (effect) --> CSAT (outcome)
- Three connected metrics, trending in the same time frame
**Implementation:** Combined chart or simple flow diagram with embedded sparklines
#### Medium Priority
**Element:** Individual metrics
**Current:** Numbers in text
**Problem:** No sense of magnitude or trend
**Visual Solution:** Dashboard-style layout with each metric as a gauge or mini-chart
**Implementation:** Standard charting tools
### The Silent Film Version
Three arrows trending the wrong direction. A timeline showing the cascade effect. The audience would understand "things are getting worse, and they're connected" without any words.
### Quick Wins
1. Replace text numbers with three simple trend arrows/icons
2. Add time dimension (show this is a recent deterioration)
3. Visual connection between the three metrics (flow or arrows)
### Hitchcock's Verdict
"You've told them the building is on fire. But you haven't shown them the flames, the smoke, or the people running. Make them *see* the problem, and they won't need you to tell them it's serious."
---
## Integration
This skill is part of the **Alfred Hitchcock** expert persona. Use it to transform verbose, explanation-heavy communication into visual experiences that speak directly to the audience's understanding.
"I always try first to tell a story in the cinematic way, through a succession of shots and bits of film in between."Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!