skills.rest
ElbertePlinio
ElbertePlinioCOMMUNITY
Explore all skills by this author →
Website𝕏@ElbertePlinioGitHub

capture

Enforce standardized pre-flight checks and recording parameters for terminal and browser automation workflows.

Updated Jul 13, 2026
Search Tags:#workflow automation#session recording#terminal capture#browser viewport#droid-control#keystroke logging#recording validation
One-click install
npx skills add https://github.com/ElbertePlinio/dotfiles --skill capture-elberteplinio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: capture
Source: https://github.com/ElbertePlinio/dotfiles/tree/main/private_dot_factory/plugins/marketplaces/factory-plugins/plugins/droid-control/skills/capture
Command: npx skills add https://github.com/ElbertePlinio/dotfiles --skill capture-elberteplinio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates inconsistent, broken, or low-quality recordings for droid-control automation workflows by enforcing standardized pre-flight checks, consistent capture parameters, and validated output collection, ensuring all session recordings are ready for immediate composition and review.

Core Features & Use Cases

  • Standardized Capture Setup: Enforces consistent terminal dimensions, layout-matched browser viewport sizing, and required color environment variables to avoid desaturated terminal recordings and letterboxed video.
  • End-to-End Recording Workflow: Guides users through pre-flight checks, interaction script execution with verification steps, keystroke logging, and raw output validation for terminal, browser, and desktop GUI sessions.
  • Failure Recovery: Provides explicit steps to recover from stuck recording sessions without losing usable output, including session bail-out, state verification, and re-recording protocols.
  • Use Case: A developer comparing two branches of a CLI tool can use this skill to record identical interaction sequences on both branches with matching terminal dimensions, producing consistent, side-by-side composable clips for review.

Quick Start

Use the capture skill to record a 120x36 terminal session of your droid-dev branch with forced 24-bit color output and save the recording as a .cast file for later composition.

Frequently Asked Questions about capture

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

FAQPage Schema
How do I standardize terminal dimensions and color output for session recording?▼

Standardizing terminal session recording requires enforcing consistent terminal dimensions and forced 24-bit color output via environment variables for PTY-based terminals, preventing desaturated recordings and ensuring validated raw output for composition.

What is the best way to record browser viewport sessions for demo video composition?▼

Recording browser viewport sessions for demo composition involves applying layout-matched browser viewport sizing during pre-flight checks, eliminating letterboxed video and ensuring captured browser automation recordings are ready for composited demo video generation.

How do I ensure consistent CLI recordings when comparing two git branches?▼

Ensuring consistent CLI recordings when comparing branches requires executing identical interaction sequences on both branches with matching terminal dimensions, producing consistent, side-by-side composable clips for review using standardized pre-flight checks.

Can I generate keystroke overlays for composited demo videos from terminal captures?▼

Generating keystroke overlays for composited demo videos is supported from terminal captures, where the workflow includes keystroke logging during interaction script execution to produce overlay data for composited video output.

Why does my droid-control workflow produce inconsistent or low-quality recordings?▼

Inconsistent or low-quality recordings in droid-control workflows occur when pre-flight checks and recording parameters are not standardized, which applying forced color output, matched viewport sizing, and validated raw output collection resolves.

How do I recover from a stuck terminal or browser recording session without losing output?▼

Recovering from a stuck recording session without losing usable output involves following explicit failure recovery steps including session bail-out, state verification, and re-recording protocols, ensuring usable raw output is preserved before attempting a new capture.

Related Skills

Explore More Software Engineering Skills→
TheBushidoCollectiveTheBushidoCollective
187

ink-hooks-state

Manage state and side effects in Ink React terminal applications with hooks.

Official
Advanced
RenyEnnosRenyEnnos
1

remotion

Assemble Stitch screens into Remotion walkthrough videos with configurable timing.

Community
Advanced
browser-usebrowser-use
615

browser-use-terminal

Automate browser tasks via Python scripts and direct CDP control of Chrome.

Official
Advanced
epologeeepologee
3

screen-recording

Record browser viewport sessions to video files with Playwright.

Community
Intermediate