---
name: screen-demo-production
description: "Create clear product demonstrations from real, privacy-safe screen recordings. Use when the user requests screen demo production. Select relevant methods for the requested outcome; unrelated tasks do not require this skill."
metadata:
  version: "1.0.0"
---

# Screen Demo Production

Create clear product demonstrations from real, privacy-safe screen recordings.

## OLLIE Runtime integration

Use this capability under the active OLLIE Operator. Read live Workspace Context and tenant bindings for client facts and required inputs. This generic package contains no client configuration. Consume ask-ollie-authority-core for authority, outloop-access-fallback for access and recovery, email-lifecycle-core for communication, and the bootstrapper Runtime Contract for ownership, scheduling and completion. Preserve domain constraints; this Skill creates no competing execution path. Use one method, combine skills, or fill missing steps with authorized tools as the task requires.

External access uses the active Workspace’s approved Outloop capabilities. Never request, read, embed or expose credentials. A service named in a method is a possible dependency, not an access grant. Local file and application work uses the host’s authorized tools.

## Required inputs

- Test environment
- Demonstration objective
- Approved recording region
- Output specifications

## Methods

### Define proof and test data

Define one demonstrable outcome and the evidence that proves it. Use a test workspace and synthetic records; never record credentials or private client views.

### Capture the actual flow

Capture a narrow relevant region and preserve the real action sequence. Keep labels outside important UI and avoid editing a failure into apparent success.

### Plan narration and emphasis

Plan narration and visual emphasis around actual timestamps. Keep supporting footage attributable and distinguish illustrative scenes from runtime proof.

### Inspect frames before sharing

Inspect all frames around transitions, popups and browser chrome for exposed information. Verify exported timing, legibility and audio before sharing.

## Completion

Verify findings against source evidence and read back the resulting artifact or authorized change. Report inputs used, methods selected, output location, assumptions and unresolved dependencies. Do not report a plan, queue entry, draft, test fixture or accepted request as a completed external action. Use the task’s requested format; if a tool is unavailable, finish independent work and identify the exact unfulfilled deliverable.

## Test before relying on it

Read [the synthetic evaluation cases](references/evaluation.md) for activation, output and isolation checks. These cases are test instructions, not evidence that a host or provider test has passed.