Agent skill

Ccap

by wysaid in wysaid/CameraCapture

Install or use the ccap CLI for camera capture, webcam inspection, device listing, frame capture, and video metadata.

MITAuto-check passedMobile

Install Ccap

skills CLI
$ npx skills add wysaid/CameraCapture --skill ccap -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install wysaid/CameraCapture ccap --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/wysaid/CameraCapture.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/ccap .claude/skills/ccap && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
ccap
GitHub stars
191
Token cost
~1.4k tokens
SKILL.md length
665 words
Files
4 (incl. references)
Skills in repo
1
Repo updated
First seen
Licence
MIT

At a glance

Install or use the ccap CLI for camera capture, webcam inspection, device listing, frame capture, and video metadata.

  • Works in 6 steps: Determine whether the task is… → Reuse an existing ccap binary if one is… → If installation is needed, follow the… → …
  • You need to work with CameraCapture on macOS
  • SKILL.md covers Typical Triggers, What This Skill Is For, What This Skill Is Not For and Default Behavior, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Ccap is an agent skill from wysaid/CameraCapture. Install or use the ccap CLI for camera capture, webcam inspection, device listing, frame capture, and video metadata. Use when you need to work with CameraCapture on macOS, Linux, or Windows, especially for listing devices, checking device capabilities, capturing frames, inspecting video files, or choosing between existing install, Homebrew, source build, and release-binary fallback.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `PUBLISHING.md`, `references/commands.md` and `references/install.md`).

It sits in Mobile. It works with Linux, Homebrew, macOS and iOS. The repository describes itself as: ccap (C)amera(CAP)ture is a simple and easy-to-use C/C++ camera capture library designed to provide you with simple and efficient camera data access. It currently supports… The licence is MIT.

When your agent uses it

  • You need to work with CameraCapture on macOS
  • Especially for listing devices
  • Checking device capabilities
  • Capturing frames

Example prompts

  • “/ccap”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Determine whether the task is installation, device inspection, capture, or video inspection.
  2. Reuse an existing ccap binary if one is already available.
  3. If installation is needed, follow the environment decision tree instead of inventing a platform-specific path.
  4. Prefer a JSON-capable command when the task can be solved with structured output.
  5. Verify the selected workflow with a minimal command before attempting larger capture or preview runs.
  6. If the environment blocks the task, report the exact blocker: missing binary, missing permission, no device, unsupported platform path, or…

What it can do on your machine

Read from SKILL.md and the folder at commit d187600. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Ccap loads about 1.4k tokens when it runs, and up to ~2.1k if it reads all its reference files. Until then it costs about 98 tokens; SKILL.md has 665 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~98
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from wysaid/CameraCapture at commit d187600, republished under its MIT licence (© wysaid). 665 words, ~1,386 tokens.

Download SKILL.mdSave it as .claude/skills/ccap/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
ccap
description
Install or use the ccap CLI for camera capture, webcam inspection, device listing, frame capture, and video metadata. Use when you need to work with CameraCapture on macOS, Linux, or Windows, especially for listing devices, checking device capabilities, capturing frames, inspecting video files, or choosing between existing install, Homebrew, source build, and release-binary fallback.
argument-hint
install | list-devices | device-info | capture | record | video-info

ccap

Use this skill when an agent needs to install or operate ccap as a practical vision-input CLI.

This skill is packaged as a standalone skill folder so it can be reused as a standard agent skill entry.

Typical Triggers

Use this skill when the user asks for things like:

  • "list my cameras"
  • "show device capabilities"
  • "capture one frame from webcam 0"
  • "record 5 seconds from webcam 0"
  • "save webcam stream to mp4"
  • "inspect this mp4"
  • "install ccap on this machine"
  • "use CameraCapture from the CLI"

What This Skill Is For

  • Installing ccap on the current machine
  • Reusing an existing ccap installation when already available
  • Building ccap from source when local development tools exist
  • Falling back to a release binary when no build toolchain is available but a matching release asset exists
  • Listing camera devices
  • Inspecting device capabilities
  • Capturing one or more frames with the CLI
  • Recording camera streams to MP4/MOV with the CLI
  • Reading video metadata

What This Skill Is Not For

  • Editing CameraCapture library internals
  • Assuming camera access permission is already granted
  • Assuming preview is safe in CI, SSH, or headless environments
  • Assuming all platforms support video-file playback equally

Default Behavior

  • Prefer the ccap CLI over internal source files.
  • Prefer --json when the command supports it.
  • Prefer non-preview workflows unless the task explicitly needs preview.
  • Treat camera devices, permissions, GUI support, and backend support as environment-dependent.

Procedure

  1. Determine whether the task is installation, device inspection, capture, or video inspection.
  2. Reuse an existing ccap binary if one is already available.
  3. If installation is needed, follow the environment decision tree instead of inventing a platform-specific path.
  4. Prefer a JSON-capable command when the task can be solved with structured output.
  5. Verify the selected workflow with a minimal command before attempting larger capture or preview runs.
  6. If the environment blocks the task, report the exact blocker: missing binary, missing permission, no device, unsupported platform path, or unavailable release asset.

Environment Decision Tree

  1. Check whether ccap is already installed and runnable.
  2. If running on macOS and brew exists, prefer Homebrew installation.
  3. Otherwise, if CMake and a compiler are available, build from source.
  4. Otherwise, if network access is available and a matching GitHub Release asset exists, download and use that binary.
  5. If none of the above is possible, stop and report the missing prerequisite instead of guessing.

See installation details.

Show full SKILL.md (268 more words)Show less

Stable Command Patterns

Use these first before improvising:

  • List devices: ccap --list-devices --json
  • Device info: ccap --device-info 0 --json
  • Video info: ccap -i /path/to/video.mp4 --json
  • Capture one frame: ccap -d 0 -c 1 -o ./captures
  • Record camera stream: ccap -d 0 --record ./camera_capture.mp4 --timeout 5
  • Capture one frame from a named device: ccap -d "OBS Virtual Camera" -c 1 -o ./captures

More examples and fallback notes are in command reference.

Operational Rules

  • If a command supports --json, prefer parsing JSON over scraping text output.
  • If device enumeration succeeds but opening the device fails, treat that as a permission or device-access issue.
  • If camera permission is denied, report the authorization requirement instead of repeated retries.
  • If there is no camera device, consider a video-file workflow if that satisfies the task.
  • If the environment is headless or remote, do not enable preview by default.
  • If video playback is unsupported on the current platform or build, report it explicitly.
  • If recording is requested, verify writer support first (CCAP_ENABLE_VIDEO_WRITER=ON and supported platform: Windows/macOS).
  • --record is camera-mode only. If input is a video file (-i), report that recording is ignored.

Response Expectations

  • Prefer reporting the exact command used.
  • Prefer reporting whether the output is structured JSON or plain text.
  • If installation was performed, state which path was chosen: existing binary, Homebrew, source build, or release binary.
  • If the task failed, report the smallest actionable next step instead of a vague failure summary.

Verification

After installation or selection of an existing binary, verify with one or more of:

bash
ccap --version
ccap --list-devices
ccap --list-devices --json
ccap -i /path/to/video.mp4 --json

Source Of Truth

Before guessing flags, build steps, or platform behavior, consult:

© wysaid, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references) in skills/ccap of wysaid/CameraCapture.

  • SKILL.md
  • PUBLISHING.md
  • references/commands.md
  • references/install.md

Open the folder on GitHubat commit d187600

Compare with similar skills

Ccap next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Ccap compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Ccap this skillwysaid/CameraCapture191—~1.4kAutomated safety check: PassMIT
Install Mimi Remotegaixianggeng/mimi-remote104—~2.8kAutomated safety check: PassGPL-3.0
Engine Whats Newflutter/flutter179k—~978Automated safety check: PassBSD-3-Clause
OdevioOdevio/Odevio-CLI423—~7.6kAutomated safety check: PassMIT
Jetpack Composedarriousliu/PiPixiv262—~1.5kAutomated safety check: PassApache-2.0
Maui AI DebuggingRedth/Maui.Gtk101—~4.1kAutomated safety check: PassMIT

Similar skills

  • Install Mimi Remote

    gaixianggeng/mimi-remote

    安装、配置、配对、迁移、升级、诊断、回滚或卸载 Mimi Remote;在 macOS 上安装和维护 Mimi Remote Mac 菜单栏 App / DMG,或通过 Homebrew、Linux user-systemd 部署 agentd;从源码构建 iPhone/iPad App;配置 Codex 主通道和可选 Claude Code 实验 Runtime。用户提出“安装 Mimi…

    104 GitHub stars~2.8k tokensUpdated today
    MobileAuto-check passed
  • Engine Whats New

    flutter/flutter

    Generates the "what's new" release summary and diff file for changes in the Flutter engine (//engine/src/flutter) between two releases (e.g., 3.47 vs 3.44).

    179k GitHub stars~978 tokensUpdated today
    MobileAuto-check passed
  • Odevio

    Odevio/Odevio-CLI

    Take a Flutter project to an iPhone or the App Store with Odevio - build, sign and publish iOS apps from Windows, Linux or macOS with no Mac and no Xcode.

    423 GitHub stars~7.6k tokensUpdated 13 days ago
    MobileAuto-check passed
  • Jetpack Compose

    darriousliu/PiPixiv

    Jetpack Compose expert skill for Android UI development. An agent skill from darriousliu/PiPixiv.

    262 GitHub stars~1.5k tokensUpdated today
    MobileAuto-check passed
  • Maui AI Debugging

    Redth/Maui.Gtk

    End-to-end workflow for building, deploying, inspecting, and debugging .NET MAUI and MAUI Blazor Hybrid apps as an AI agent.

    101 GitHub stars~4.1k tokensUpdated 5 mo ago
    MobileAuto-check passed
  • Wally Release

    RunanywhereAI/wally

    Cut an Wally product release (independent of SDK version) — version bump, release:patch label, merge, auto-tag, bottles.

    1.6k GitHub stars~1.3k tokensUpdated today
    Auto-check passed

Categories

Questions about Ccap

What does Ccap do?

Install or use the ccap CLI for camera capture, webcam inspection, device listing, frame capture, and video metadata. Ccap is an agent skill from wysaid/CameraCapture. Install or use the ccap CLI for camera capture, webcam inspection, device listing, frame capture, and video metadata.

When should I use Ccap?

Ccap fits situations like: you need to work with CameraCapture on macOS; especially for listing devices; checking device capabilities; capturing frames.

How do I install Ccap in Claude Code?

Run `npx skills add wysaid/CameraCapture --skill ccap -a claude-code`. Or copy the skill folder (skills/ccap in wysaid/CameraCapture) into .claude/skills/ccap in your project. Claude Code loads it when a task matches its description.

How do I install Ccap in Codex?

Run `npx skills add wysaid/CameraCapture --skill ccap -a codex`. Or copy the skill folder (skills/ccap in wysaid/CameraCapture) into .agents/skills/ccap in your project. Codex loads it when a task matches its description.

Can I use Ccap in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add wysaid/CameraCapture --skill ccap -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ccap, .gemini/skills/ccap, .github/skills/ccap and .opencode/skills/ccap in your project.

What does Ccap need to run?

SKILL.md names no scripts, command-line tools or credentials: Ccap is instructions for the agent only.

Does Ccap access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Ccap safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Ccap use?

Ccap is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Ccap use?

About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 714 tokens, read only when the agent opens those files.

What are the alternatives to Ccap?

Skills that share tags, products or a category with Ccap: Install Mimi Remote (gaixianggeng/mimi-remote, 104 stars), Engine Whats New (flutter/flutter, 179k stars), Odevio (Odevio/Odevio-CLI, 423 stars) and Jetpack Compose (darriousliu/PiPixiv, 262 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ccap?

wysaid (a GitHub user) maintains it in wysaid/CameraCapture, which has 191 GitHub stars. The repository was last updated on June 25, 2026.

Source: wysaid/CameraCapture on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.