cli-anything-openscreen

Edit screen recordings with a stateful CLI using FFmpeg and Openscreen JSON.

1|Updated Jun 13, 2025
One-click install
npx skills add https://github.com/quazfenton/binG --skill cli-anything-openscreen-quazfenton
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cli-anything-openscreen
Source: https://github.com/quazfenton/binG/tree/main/.agents/skills/CLI-Anything-main/CLI-Anything-main/openscreen/agent-harness/cli_anything/openscreen/skills
Command: npx skills add https://github.com/quazfenton/binG --skill cli-anything-openscreen-quazfenton

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Edit screen recordings with a stateful CLI to apply zoom, trims, annotations, and polished exports, enabling automation and reproducible video edits without a GUI.

Core Features & Use Cases

  • Stateful zoom and trim editing of screen captures
  • Batch processing and automation for video editing workflows
  • FFmpeg-backed rendering with Openscreen JSON project format for reproducible exports

Quick Start

Install and run the tool to begin interactive editing of a captured video.

Frequently Asked Questions about cli-anything-openscreen

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate screen recording edits with a CLI instead of a GUI?

You can automate screen recording edits through a stateful CLI that applies zoom, speed ramps, trims, and annotations. This enables repeatable, scriptable video processing across multiple projects without requiring manual GUI interaction.

Can I batch process multiple video files for editing workflows?

Batch processing and automation for video editing workflows are supported. You can apply stateful zoom and trim editing across multiple screen captures to produce polished demos repeatedly.

Does ffmpeg work with the Openscreen JSON project format for video rendering?

FFmpeg-backed rendering works with the Openscreen JSON project format to ensure reproducible exports. This combination allows stateful CLI editing sessions to persist and render consistently across developer pipelines.

What is the best way to add zoom and speed ramps to screen captures programmatically?

The best way to add zoom and speed ramps programmatically is using a stateful CLI designed for screen recordings. It applies these effects via ffmpeg-backed rendering and saves edits in the Openscreen JSON project format.

Do I need interactive session persistence for reproducible video exports?

Interactive session persistence is required for reproducible video exports because it maintains the stateful editing context. This ensures that zoom, trims, and annotations render consistently every time the project is processed.