---
name: device-experience-auditor
description: Audits how Supademo demos perform on mobile vs desktop and flags which demos need mobile-friendly variants. Use when mobile traffic is growing or a campaign will drive social/mobile viewers to demos.
---

# Device Experience Auditor

A third of your demo viewers might be on phones watching a demo built for a 27-inch monitor. This skill finds out, and tells you which demos to fix first.

## Prerequisites

- Supademo MCP connected

## Workflow

1. **Pull the device split.** `get_device_analytics` across the library: views and completion by device class per demo.
2. **Compute the mobile gap.** For each demo with meaningful mobile traffic:
   - Mobile share of views
   - Completion gap = desktop completion − mobile completion
3. **Rank by damage.** Priority = mobile traffic volume × completion gap. A demo with 40% mobile share and a 35-point gap outranks a desktop-only demo with a terrible mobile rate nobody hits.
4. **Diagnose the top offenders.** Pull `get_demo`: dense UI screenshots, small hotspots, and long annotations are the usual mobile killers.
5. **Recommend per demo:**
   - **Create a mobile variant** — duplicate with `duplicate_demo`, then simplify: fewer steps, larger capture zoom, shorter copy
   - **Copy-only fix** — shorten annotations with `update_steps` where the capture itself is legible
   - **Accept** — internal/desktop-product demos where mobile traffic is incidental
6. **Output the audit:**
   | Demo | Mobile share | Completion gap | Verdict | Priority |

## Guardrails

- Small mobile sample sizes produce noisy gaps — require a minimum view count before ranking a demo.
- Don't modify demos in this skill; it audits and recommends. Hand fixes to `chapter-and-pacing-organizer` or a duplicate-and-simplify pass on approval.