macos-screen-recorder
macOS screen recorder that captures the main display PLUS system audio via ScreenCaptureKit — no BlackHole/loopback driver, no sudo, just the standard Screen Recording permission. CLI-driven; fills the headless-screen-recording-with-system-sound gap QuickTime and `screencapture -v` can't.
- License 许可
- MIT
- 最近更新
- 2026-10-22
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- macos-screen-recorder
- risk
- critical
- tags
- [ "macos", "screen-recording", "system-audio", "screencapturekit", "cli", "swift" ]
- tools
- [ "claude-code", "antigravity", "cursor", "gemini-cli", "codex-cli" ]
- author
- Conner K Ward
- plugin
- { "setup": { "docs": "SKILL.md", "type": "manual", "summary": "Screen/audio/input capture requires sensitive macOS permissions; keep out of plugin-safe bundles." }, "targets": { "codex": "blocked", "claude": "blocked" } }
- source
- community
- license
- MIT
- date_added
- 2026-06-16
- description
- macOS screen recorder that captures the main display PLUS system audio via ScreenCaptureKit — no BlackHole/loopback driver, no sudo, just the standard Screen Recording permission. CLI-driven; fills the headless-screen-recording-with-system-sound gap QuickTime and `screencapture -v` can't.
- source_repo
- connerkward/macos-screen-recorder-system-audio
- source_type
- community
03 SKILL.md 正文
When to Use
Use when you need to script a screen recording WITH system sound on macOS from the CLI (demos, captures, voice-demo recording) — the case QuickTime and screencapture -v can't cover without a virtual audio device.
Source: connerkward/macos-screen-recorder-system-audio (MIT).
macos-screen-recorder (sck-record)
sck-record.swift → compiled sck-record (binary gitignored; built by setup-machine, or
swiftc -O sck-record.swift -o sck-record). Records the main display + system audio via
ScreenCaptureKit.
./sck-record <out.mp4> <seconds>
The one true differentiator: system audio from the CLI with zero install — no BlackHole / loopback virtual device, no sudo; only the standard Screen Recording permission (granted once to whatever app shells out). It is not a general "better than OBS/Screen Studio" tool — it fills exactly the headless-CLI-with-system-audio gap.
sck-record is the raw capture primitive — it records, nothing more. To polish a
recording afterward (idle speed-up, auto-zoom, keystroke chips, smoothed cursor,
vertical export), pair it with
screenstudio-alternative-skill:
record with sck-record --no-cursor <out.mp4> <seconds>, then run its post-production
pass on the resulting mp4. (Auto-zoom and keystroke overlays additionally need an
input-event log captured during recording, which that skill supplies; sck-record's
pixels alone cover idle speed-up, cursor smoothing, and vertical export.)
Limitations
- macOS only; it depends on ScreenCaptureKit and the user's Screen Recording permission.
- The recorder captures raw display and system audio but does not provide editing, auto-zoom, captions, or social-format polish by itself.
- Input-event overlays require a separate event log captured during recording; pixels alone cannot reconstruct keystrokes or precise click metadata.
04 同仓库更多 Skills
testing-best-practices
Laravel test design and review. Use when selecting coverage, naming or structuring tests, choosing assertions or test data, isolating dependencies, testing HTTP or security boundaries, improving suite performance, or reviewing test value. Use framework guidance or search-docs for Pest and PHPUnit syntax.
tailwindcss-development
Always invoke when the user's message includes 'tailwind' in any form. Also invoke for: building responsive grid layouts (multi-column card grids, product grids), flex/grid page structures (dashboards with sidebars, fixed topbars, mobile-toggle navs), styling UI components (cards, tables, navbars, pricing sections, forms, inputs, badges), adding dark mode variants, fixing spacing or typography, and Tailwind v3/v4 work. The core use case: writing or fixing Tailwind utility classes in HTML templates (Blade, JSX, Vue). Skip for backend PHP logic, database queries, API routes, JavaScript with no HTML/CSS component, CSS file audits, build tool configuration, and vanilla CSS.
laravel-best-practices
Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. This includes creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries. Triggers for N+1 and query performance issues, caching strategies, authorization and security patterns, validation, error handling, queue and job configuration, route definitions, and architectural decisions. Also use for Laravel code reviews and refactoring existing Laravel code to follow best practices. Covers any task involving Laravel backend PHP code patterns.
infer-conventions
Use this skill to analyze how a Laravel application is actually written and record its conventions as shared rules. Trigger when the user wants to detect, infer, document, or standardize project conventions or coding style, set up or grow `.ai/rules`, resolve mixed or conflicting patterns (e.g. "are we using Form Requests or inline validation?"), or onboard agents and teammates to "how we do things here". Covers: a systematic sweep of ~49 Laravel convention dimensions (validation, models, architecture, testing, frontend, database, console), open-ended house-pattern discovery, conflict reporting, and recording rules scoped to the right paths via the Boost `record-rule` MCP tool. Only run this skill when the user explicitly asks for it; never start a sweep as part of another task. Do not use for one-off code review, enforcing formatting a linter already handles, or editing `.ai/rules` files by hand.
inertia-react-development
Develops Inertia.js v2 React client-side applications. Activates when creating React pages, forms, or navigation; using <Link>, <Form>, useForm, or router; working with deferred props, prefetching, or polling; or when user mentions React with Inertia, React pages, React forms, or React navigation.
deploying-to-cloud
Deploys and manages Laravel applications on Laravel Cloud using the `cloud` CLI. Use when the user wants to deploy an app, ship to Cloud, create or manage applications, environments, databases, caches, object storage, queues, domains, instances, background processes, secrets, compute, scheduled tasks, or Laravel Cloud infrastructure; or check billing, usage, or spend. Triggers on deployment, shipping, Cloud management, environment setup, database provisioning, billing or usage queries, the `cloud` CLI, and Laravel Cloud deployment troubleshooting.