Agent skill · Data & Analytics

matlab-point-cloud-file-io

Read and write 3-D point cloud data using Lidar Toolbox file I/O. Covers PLY, PCD, LAS/LAZ, PCAP (Velodyne/Ouster/Hesai), E57, and IDC (Ibeo) formats. Use when loading point clouds from disk, saving to disk, choosing the correct reader or writer for a file format, extracting or preserving lidar point attributes, reading Ibeo IDC sensor recordings, or converting between formats.

matlabgithub.com/matlabGitHub ↗
claude-codecodexcopilotNOASSERTION
Install
npx skills add matlab/matlab-agentic-toolkit --skill matlab-point-cloud-file-io --agent claude-code

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

Facts
Files in the skill folder: 5
SKILL.md size: 14 KB
Bundled scripts: none
Version: 1.0
Declared author: MathWorks
Path: skills-catalog/image-processing-and-computer-vision/matlab-point-cloud-file-io/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

# Point Cloud File I/O Read and write 3-D point cloud data in MATLAB using Lidar Toolbox file I/O functions, covering PLY, PCD, LAS/LAZ, sensor PCAP, E57, and IDC (Ibeo) formats. ## When to Use - Loading a point cloud file from disk into a `pointCloud` object - Saving a `pointCloud` object to disk in any supported format - Deciding which reader or writer function to use for a given file format - Reading LAS/LAZ files with selective filtering (ROI, classification, GPS time) - Extracting or preserving lidar point attributes (classification, GPS timestamps, scan angle) - Reading Velodyne, Ouster, or Hesai PCAP sensor recordings frame-by-frame - Reading multi-scan E57 files with indexed access - Reading Ibeo IDC sensor recordings with message-based access - Converting between point cloud formats (e.g., LAS to PLY, PCD to LAZ) ## When NOT to Use - Streaming live sensor data in real time (use `velodynelidar`, `ousterlidar`, `sicklidar`) - Processing or filtering point clouds after reading (use `pcdownsample`, `pcdenoise`) - Reading or writing surface meshes (use `readSurfaceMesh`, `writeSurfaceMesh`) - Saving point cloud variables to MAT-files (use `save`) - Visualizing point clouds (use

What's inside
Steps it walks through
  1. When to Use
  2. When NOT to Use
  3. Must-Follow Rules
  4. Preflight Procedure
  5. Key Functions
  6. Decision Framework
  7. Gotchas
  8. pcread called on LAS/LAZ file
  9. Compressed encoding on PLY file
  10. Using pcwrite for LAS/LAZ output
  11. Losing attributes with two-argument writePointCloud
  12. Accessing classification from the wrong object
  13. Reading all PCAP frames without a loop
  14. Patterns
Ships with 4 files
  • manifest.yaml
  • references/INDEX.md
  • references/quick-ref/las-io.md
  • references/quick-ref/pcap-readers.md
More from matlab-agentic-toolkit
All skills →
About this skill
What does the matlab-point-cloud-file-io skill do?

Read and write 3-D point cloud data using Lidar Toolbox file I/O. Covers PLY, PCD, LAS/LAZ, PCAP (Velodyne/Ouster/Hesai), E57, and IDC (Ibeo) formats. Use when loading point clouds from disk, saving to disk, choosing the correct reader or writer for a file format, extracting or preserving lidar point attributes, reading Ibeo IDC sensor recordings, or converting between formats.

How do I install it?

Run `npx skills add matlab/matlab-agentic-toolkit --skill matlab-point-cloud-file-io --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