yaps-video-clipping9.59 KB
View saved version →
---
name: yaps-video-clipping
description: Safely remove dead air and long pauses from talking-head MP4 or other readable video files with Yaps Auto Cut, review or tune a cut plan, and export a separate tightened MP4. Use for remove dead space, cut silences, tighten pauses, shorten a talking-head video, make a social cut, clip out long gaps, review an Auto Cut project, or rerender an existing Yaps cut. Do not use for selecting semantic highlights, rearranging scenes, adding captions, or destructive source replacement.
---
# Yaps Video Clipping
Create a reviewable Auto Cut project, inspect the proposed removals, and render a new MP4. Preserve the source video and existing outputs throughout.
## Runtime compatibility
Do not guess whether the host can reach the user's computer from a product name or user-agent. Before account, dependency, or input checks, resolve the local Yaps CLI through the plugin runner. The runner validates it with a bounded, read-only `status` command. A cloud shell that cannot see the installed Yaps app is not local access.
If the CLI is unreachable, do not claim Yaps is uninstalled. Explain that the current AI session cannot reach the local Yaps engine. Direct the user to Claude Code or the Claude desktop app on the machine with Yaps, or to [ChatGPT desktop](https://chatgpt.com/download/) for a local-capable Work or Codex session. They can also open **Yaps → Media → Auto Cut**. If they are already local, offer [Download or update Yaps](https://yaps.ai/download) and retry. Stop until reachability is restored.
## Private operational diagnostics
Run every Yaps CLI command through the plugin's `scripts/yaps-plugin-runner.mjs`:
```text
node <plugin-root>/scripts/yaps-plugin-runner.mjs --action cut.command --stage execution -- yaps cut presets --pretty
```
The runner preserves normal output and exit status. Its on-device diagnostic breadcrumb may contain only plugin ID/version, host, action, stage, attempt/outcome, duration, and a fixed error category. It must never contain prompts, arguments, stdout/stderr, credentials, filenames or paths, transcript text, or media contents. If Node or the runner is unavailable, continue directly; diagnostics must never prevent the requested feature from working.
## CLI discovery contract
Always invoke Yaps through `scripts/yaps-plugin-runner.mjs`; do not locate the binary by hand. The runner honors an explicit path or `YAPS_CLI_BINARY`, then checks `PATH`, then verified Yaps locations on macOS, Windows, and official Linux deb/rpm packages. It rejects the macOS GUI executable and unverified Linux AppImages. Never ask the user to install a separate CLI, edit `PATH`, or configure MCP. Repeat the runner's specific recovery guidance if discovery fails.
Use the following prefix as `<yaps>` for every command below:
```text
node "<plugin-root>/scripts/yaps-plugin-runner.mjs" --action cut.command --stage execution -- yaps
```
## Availability and account access
Require Yaps desktop 2.3.848 or newer. Run `<yaps> --help` and `<yaps> cut --help` before account, dependency, or input checks. If `cut` is unavailable, ask the user to update Yaps; do not replace this workflow with ad-hoc FFmpeg commands.
Never request credentials or payment details. Yaps no longer has a free tier. Auto Cut requires an active free trial or Yaps Pro, and only Yaps may determine trial eligibility. Run `<yaps> auth status --pretty`; continue only when `authenticated` is true and `status` is `active`. For sign-in or entitlement issues, direct the user to the Yaps account screen. Do not expose email addresses, billing dates, SKUs, or internal plan keys. Describe paid access only as **Yaps Pro**.
For `desktop_account_unavailable`, open Yaps and retry in a local session
under the same operating system account. If Yaps already shows active access,
keep the current sign-in and trial or Yaps Pro access.
The runner follows Yaps's canonical settings file and can safely wake a verified installed app when a
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.
