Agent skill · Media & Video

matlab-use-cameras

Connect to and acquire images from cameras in MATLAB using Image Acquisition Toolbox. Use this skill when the user wants to: use a webcam, acquire images, capture video, stream from a camera, connect to a GigE Vision camera, preview live video, list available cameras, configure camera properties, use a CoaXPress frame grabber, or use a Camera Link frame grabber. Covers USB webcams, GigE Vision, USB3 Vision, CoaXPress, Camera Link, and GenICam-compliant cameras. Always prefer videoinput from Image Acquisition Toolbox over webcam support package or gigecam.

matlabgithub.com/matlabGitHub ↗
claude-codecodexcopilotNOASSERTION
Install
npx skills add matlab/matlab-agentic-toolkit --skill matlab-use-cameras --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 11 KB
Bundled scripts: none
Version: 1.0
Declared author: MathWorks
Path: skills-catalog/test-and-measurement/matlab-use-cameras/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 868
Language: MATLAB

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Using Cameras in MATLAB Use Image Acquisition Toolbox's `videoinput` as the primary interface for all camera workflows. Other interfaces (`webcam`, `gigecam`) are secondary and should only be used when explicitly requested or when `videoinput` is unavailable. ## When to Use - User wants to connect to a camera (webcam, USB, GigE, USB3 Vision, CoaXPress, Camera Link) - User wants to acquire images or video frames - User wants to preview live camera feed - User wants to list or enumerate available cameras - User wants to acquire images from a CoaXPress frame grabber - User wants to acquire images via a Camera Link frame grabber - User asks "how do I use my webcam/camera in MATLAB?" - User mentions Image Acquisition Toolbox ## When NOT to Use - User explicitly requests `webcam()` from the webcam support package - User is on MATLAB Online (where `videoinput` is not available — use `webcam()`) - User is doing image processing on existing files (no camera involved) - User is working with non-imaging hardware (oscilloscopes, data acquisition boards) ## Conventions ### API Priority Rules These rules are critical. Follow them unless the user explicitly requests otherwise. 1. **Always use `

What's inside
Steps it walks through
  1. When to Use
  2. When NOT to Use
  3. Conventions
  4. API Priority Rules
  5. When to use webcam() instead
  6. Required support packages
  7. Workflow
  8. 1. Enumerate devices
  9. 2. Connect to camera
  10. 3. Configure properties
  11. 4. Preview live video
  12. 5. Acquire frames
  13. 6. Clean up
  14. Key Functions
Ships with 2 files
  • manifest.yaml
  • references/gentl-setup.md
More from matlab-agentic-toolkit
All skills →
About this skill
What does the matlab-use-cameras skill do?

Connect to and acquire images from cameras in MATLAB using Image Acquisition Toolbox. Use this skill when the user wants to: use a webcam, acquire images, capture video, stream from a camera, connect to a GigE Vision camera, preview live video, list available cameras, configure camera properties, use a CoaXPress frame grabber, or use a Camera Link frame grabber. Covers USB webcams, GigE Vision, USB3 Vision, CoaXPress, Camera Link, and GenICam-compliant cameras. Always prefer videoinput from Image Acquisition Toolbox over webcam support package or gigecam.

How do I install it?

Run `npx skills add matlab/matlab-agentic-toolkit --skill matlab-use-cameras --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 matlab/matlab-agentic-toolkit, a repository with 868 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.

Keep going