automate-this
Analyze a screen recording of a manual process and produce targeted, working automation scripts. Extracts frames and audio narration from video files, reconstructs the step-by-step workflow, and proposes automation at multiple complexity levels using tools already installed on the user machine.
npx skills add github/awesome-copilot --skill automate-this --agent copilot
Same command for any agent — swap --agent for claude-code, codex, cursor.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Automate This Analyze a screen recording of a manual process and build working automation for it. The user records themselves doing something repetitive or tedious, hands you the video file, and you figure out what they're doing, why, and how to script it away. ## Prerequisites Check Before analyzing any recording, verify the required tools are available. Run these checks silently and only surface problems: ```bash command -v ffmpeg >/dev/null 2>&1 && ffmpeg -version 2>/dev/null | head -1 || echo "NO_FFMPEG" command -v whisper >/dev/null 2>&1 || command -v whisper-cpp >/dev/null 2>&1 || echo "NO_WHISPER" ``` - **ffmpeg is required.** If missing, tell the user: `brew install ffmpeg` (macOS) or the equivalent for their OS. - **Whisper is optional.** Only needed if the recording has narration. If missing AND the recording has an audio track, suggest: `pip install openai-whisper` or `brew install whisper-cpp`. If the user declines, proceed with visual analysis only. ## Phase 1: Extract Content from the Recording Given a video file path (typically on `~/Desktop/`), extract both visual frames and audio: ### Frame Extraction Extract frames at one frame every 2 seconds. This balances cov
- Prerequisites Check
- Phase 1: Extract Content from the Recording
- Frame Extraction
- Audio Extraction and Transcription
- Phase 2: Reconstruct the Process
- Phase 3: Environment Fingerprint
- Phase 4: Propose Automation
- Tier Structure
- Proposal Format
- Application-Specific Automation Strategies
- Making Proposals Targeted
- Phase 5: Build and Test
- Cleanup
command -v ffmpeg >/dev/null 2>&1 && ffmpeg -version 2>/dev/null | head -1 || echo "NO_FFMPEG" command -v whisper >/dev/null 2>&1 || command -v whisper-cpp >/dev/null 2>&1 || echo "NO_WHISPER" chmod 700 "$WORK_DIR" mkdir -p "$WORK_DIR/frames" ffmpeg -y -i "<VIDEO_PATH>" -vf "fps=0.5" -q:v 2 -loglevel warning "$WORK_DIR/frames/frame_%04d.jpg" ls "$WORK_DIR/frames/" | wc -l ffprobe -i "<VIDEO_PATH>" -show_streams -select_streams a -loglevel error | head -5 ffmpeg -y -i "<VIDEO_PATH>" -ac 1 -ar 16000 -loglevel warning "$WORK_DIR/audio.wav" Use whichever whisper binary is available if command -v whisper >/dev/null 2>&1; then
What does the automate-this skill do?
Analyze a screen recording of a manual process and produce targeted, working automation scripts. Extracts frames and audio narration from video files, reconstructs the step-by-step workflow, and proposes automation at multiple complexity levels using tools already installed on the user machine.
How do I install it?
Run `npx skills add github/awesome-copilot --skill automate-this --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.