CtrlK
BlogDocsLog inGet started
Tessl Logo

cli-anything-cloudcompare

Command-line interface for CloudCompare — Agent-friendly harness for CloudCompare, the open-source 3D point cloud and mesh processing software. Supports 41 commands across 9 groups: project management, session control, point cloud operations (subsample, filter, segment, analyze), mesh operations, distance computation (C2C, C2M), transformations (ICP, matrix), export (LAS/LAZ/PLY/PCD/OBJ/STL/E57), and interactive REPL.

64

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./cloudcompare/agent-harness/cli_anything/cloudcompare/skills/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an exceptionally actionable CLI reference: every command has executable examples, options, and error-handling guidance, with four complete worked workflows. Its main weaknesses are that the full command reference is inlined in SKILL.md rather than split into reference files, and validation/verification guidance is centralized in an 'For AI Agents' checklist instead of embedded as checkpoints inside the workflows.

Suggestions

Move the per-command reference (groups 1–8) into references/ files (e.g. references/cloud-commands.md, references/export-commands.md) and keep SKILL.md as an overview with installation, global options, and links to each group.

Embed validation checkpoints directly inside each Typical Workflow step (e.g. after each operation: 'check exit code 0' and 'run cloud list to confirm the new index') instead of only listing them in the 'For AI Agents' section.

Remove redundancy: drop the 'Supported File Formats' table or the inline preset lists, and fold the Version table into the Installation section, since both currently state the same information twice.

DimensionReasoningScore

Conciseness

Almost no explanation of concepts Claude already knows — the body is command syntax, options, and examples throughout. Minor trimmable redundancy: the 'Supported File Formats' table duplicates the inline export preset lists ('las, laz, ply, pcd, xyz, asc, csv, bin, e57' / 'obj, stl, ply, bin'), and the Version table repeats prerequisite info. Fits the 4 anchor ('efficient; minor instances of over-explanation') rather than the lean 5 anchor.

4 / 5

Actionability

Every command ships a copy-paste-ready bash invocation with concrete values (e.g. 'cloud subsample 0 -o /data/sub_random.las -m random -n 100000') plus an explicit 'Options:' line, and the four Typical Workflows are complete end-to-end scripts. Fully matches the 5 anchor ('copy-paste ready code or commands; specific examples cover the common cases').

5 / 5

Workflow Clarity

Four clearly sequenced workflows with state-tracking comments ('# note index → 0'), an Error Handling section (exit codes plus recovery hints), and agent directives ('Check return codes', 'Verify output files exist after export operations', 'Use cloud list --json to discover valid indices'). Matches the 4 anchor — clear sequence with most checkpoints present — but validation is presented as general guidance rather than explicit inline checkpoints within each workflow step, so the 5 anchor (embedded feedback loops) is not met.

4 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), and ~600 lines of full command reference are inlined monolithically in SKILL.md. Navigation is good (9 clearly headed groups), placing it above the 2 anchor's 'minimal structure', but 'content that should be separate is inline' — a 41-command API reference of this size belongs in references/ files with SKILL.md as an overview — matching the 3 anchor.

3 / 5

Total

16

/

20

Passed

Description

75%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is highly specific and distinctive, enumerating concrete capabilities and file formats across the tool's full command surface. Its main weaknesses are the complete absence of an explicit 'Use when...' trigger clause and a few missing natural synonyms like 'LiDAR'.

Suggestions

Add an explicit trigger clause, e.g. 'Use when working with point clouds, LiDAR scans, or 3D meshes — or when the user mentions CloudCompare, .las/.laz/.ply/.e57 files, registration, or ground filtering.'

Include common natural synonyms such as 'LiDAR', '3D scanning', and 'registration/alignment' that users would say when needing this skill.

Trim the repeated 'CloudCompare' mention ('Command-line interface for CloudCompare — Agent-friendly harness for CloudCompare') to save tokens for trigger terms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions with comprehensive coverage — 'subsample, filter, segment, analyze', 'distance computation (C2C, C2M)', 'transformations (ICP, matrix)', 'export (LAS/LAZ/PLY/PCD/OBJ/STL/E57)', 'interactive REPL' — across all 9 command groups. It exceeds the 4 anchor ('several specific actions; minor gaps') because coverage spans the tool's whole surface.

5 / 5

Completeness

The 'what' is clear and detailed ('41 commands across 9 groups: ...'), but there is no 'Use when...' clause or equivalent explicit trigger guidance anywhere in the description. Per the judging guidelines, a missing 'Use when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Good natural keyword coverage: 'point cloud', 'mesh', 'CloudCompare', 'ICP', 'REPL', and file extensions LAS/LAZ/PLY/PCD/OBJ/STL/E57. A few common terms users would actually say are missing, such as 'LiDAR', '3D scanning', and 'registration', so it fits the 4 anchor rather than the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

Names a specific niche tool ('Command-line interface for CloudCompare ... the open-source 3D point cloud and mesh processing software') with distinct triggers (C2C/C2M, ICP, point-cloud file extensions), so it occupies a clear niche with minimal conflict risk — matching the 5 anchor.

5 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (790 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository
HKUDS/CLI-Anything
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.