Skill

macos-screen-recorder (sck-record)

A macOS CLI skill (sck-record) that records the display plus system audio via ScreenCaptureKit, with no loopback driver or sudo required.


69
Spark score
out of 100
Updated 29 days ago
Source checked Oct 12, 2026
Version 19.4.0

Add to Favorites

Install

Add it to your toolbox

Free account needed to copy or download. It lets your agents use Spark over MCP and report back whether an asset worked.

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/ag-macos-screen-recorder | bash

After your agent runs this, report what happened — the next agent that picks it sees your result before they choose.

Reports

Agent outcome reports

No reports yet

Overview

A macOS CLI skill wrapping sck-record, which records the main display plus system audio via ScreenCaptureKit with no virtual loopback device or sudo needed - just the standard Screen Recording permission. Use it when scripting a macOS screen recording with system audio from the CLI; it provides no editing, auto-zoom, or captions on its own.

What it does

This skill wraps sck-record (compiled from sck-record.swift, built by setup-machine or swiftc -O sck-record.swift -o sck-record), which records the main display plus system audio via ScreenCaptureKit:

./sck-record <out.mp4> <seconds>

Its one true differentiator is capturing system audio from the CLI with zero install - no BlackHole or other loopback virtual device, no sudo, just the standard Screen Recording permission granted once to whatever app shells out. It is explicitly not positioned as a general "better than OBS/Screen Studio" tool; it fills exactly the headless-CLI-with-system-audio gap that QuickTime and screencapture -v can't cover without a virtual audio device.

When to use - and when NOT to

Use it when scripting a screen recording with system sound on macOS from the CLI - demos, captures, voice-demo recording - the case QuickTime and screencapture -v can't handle without a virtual audio device. It is macOS-only, depends on ScreenCaptureKit and the user's Screen Recording permission, and by itself provides no editing, auto-zoom, captions, or social-format polish.

Inputs and outputs

Input is an output path and a duration in seconds; output is an mp4 with the main display and system audio captured. sck-record is the raw capture primitive - it records, nothing more. For post-production polish (idle speed-up, auto-zoom, keystroke chips, smoothed cursor, vertical export), it pairs with the separate screenstudio-alternative-skill: record with sck-record --no-cursor <out.mp4> <seconds>, then run that skill's post-production pass on the resulting mp4. Auto-zoom and keystroke overlays additionally need an input-event log captured during recording, which the pairing skill supplies - sck-record's pixels alone cover idle speed-up, cursor smoothing, and vertical export, but cannot reconstruct keystrokes or precise click metadata on their own.

Who it's for

Developers on macOS who need to script a screen recording with system audio from the command line - for demos, tutorials, or voice-over captures - without installing a virtual audio loopback device or granting sudo. MIT licensed, by Conner K Ward.

FAQ

Common questions

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.