# Create ScreenCI Product Videos

Browser demonstrations can be difficult to script, narrate, and record consistently. This skill builds and verifies ScreenCI scripts, then records and uploads finished videos.

## Install

```bash
npx skillstore add screenci/screenci
```

## Metadata

- Status: approved
- Slug: screenci-screenci
- Skillstore revision: r2
- Version status: missing
- Tree hash: 9815fd18240a5119c95aad31a865f97df449a347918ce4d1e80cc5a985a46ba1
- Author: screenci
- GitHub username: screenci
- License: MIT
- Repository: https://github.com/screenci/screenci/tree/main/skills/screenci/
- Ref: ebdfe608f5de2b66ff37ab4af12af8ac4f5e8006
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: filesystem, external\_commands, network
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/screenci-screenci
- Manifest: https://skillstore.pages.dev/api/skills/screenci-screenci/manifest

## Capabilities

- Creates or edits Playwright-style ScreenCI scripts under the recordings directory.
- Adds required narration cues and coordinates speech with visible browser actions.
- Uses hide, zoom, audio, values, and overlay helpers to shape recordings.
- Runs filtered or complete ScreenCI tests and repairs failing selectors or flows.
- Records successful scripts, saves local artifacts, and returns the uploaded result link.

## Use Cases

- Publish a release walkthrough: Create a narrated browser video that demonstrates a completed feature and its expected user flow.
- Build a support tutorial: Turn a repeatable customer workflow into a focused video with clear narration and controlled framing.
- Record a validated test flow: Convert stable Playwright interactions into a tested ScreenCI recording with visible navigation and reusable selectors.

## Prompt Templates

### Record a basic flow

```
Create a ScreenCI video for [flow] in this initialized project. Test it locally, ask before upload, then report the recording link.
```

### Improve narration and framing

```
Update [recording file] with continuous narration. Hide setup, use stable zoom for forms, and keep navigation visible after the start page.
```

### Repair a failing recording

```
Run the ScreenCI test for [recording file]. Fix selectors, timing, narration cues, and navigation until the test passes without forced actions.
```

### Build an advanced product tour

```
Create a multilingual ScreenCI tour for [journey]. Add selected overlays and audio, validate every route, request upload approval, and report all artifacts.
```

## Limitations

- Requires an initialized ScreenCI project, Node.js 18 or later, and working local dependencies.
- Every successful recording is uploaded to ScreenCI, including anonymous trial recordings.
- Reliable output depends on stable selectors, available test data, authentication, and predictable application state.
- Organization uploads require a shared ScreenCI secret stored in the project environment file.

## Best Practices

- Test every recording locally before starting capture or upload.
- Remove secrets and private customer data from all visible pages and test fixtures.
- Request explicit approval immediately before any recording leaves the device.

## Anti Patterns

- Do not upload authenticated browser sessions without reviewing every visible state.
- Do not pass shared secrets through command-line arguments or include them in scripts.
- Do not rely on forced clicks, arbitrary delays, or unstable selectors to hide test failures.

## Security Audit

- Audited at: 2026-07-23T19:40:55.313\+00:00
- Summary: The skill intentionally runs ScreenCI commands and uploads browser recordings to an external service. Most shell findings are Markdown or API references, but actual npm and npx commands, command-line secret handling, and upload behavior are confirmed risks. The unmatched prompt-wrapper closing tags and the instruction to upload without confirmation add high-confidence semantic concerns.

## Stats

- Views: 0
- Downloads: 3
- Favorites: 0
- Popularity score: 0