CtrlK
BlogDocsLog inGet started
Tessl Logo

cli-hub-matrix-3d-cad

Capability-based multi-tool matrix for 3D modeling, CAD, point clouds, rendering, GPU debugging, and fabrication. Covers mesh/parametric/photogrammetry and the path from idea to printed part or game-ready asset.

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 ./cli-hub-matrix/3d-cad/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 a concise, well-structured capability matrix with executable install/preflight commands and useful agent guidance including a manifold-validation checkpoint; its main gaps are abstract recipe pipelines without copy-paste steps and the absence of any actual bundle reference files.

Suggestions

Turn the Recipes into executable sequences with concrete commands and explicit validate→fix→retry checkpoints between stages (e.g., manifold check before slicing, slicer dry-run before printing).

Move the per-capability provider tables or extended preflight probes into references/ files and link to them one level deep, so SKILL.md stays a lean overview.

Add a brief validation/verification step to each recipe's final stage (e.g., verify gcode loads in the slicer preview, confirm exported glTF opens in Godot).

DimensionReasoningScore

Conciseness

Lean and dense — compact provider tables, executable install/preflight blocks, and terse agent guidance with no explanation of concepts Claude already knows; every section earns its tokens.

5 / 5

Actionability

Provides executable install and preflight commands plus concrete provider tables with env vars and quality tiers; not 5 because the Recipes section lists abstract pipelines ('parametric CAD → mesh → slice → gcode') rather than copy-paste commands for the common cases.

4 / 5

Workflow Clarity

Recipes are sequenced with capability chains and agent guidance includes a validation checkpoint ('Check manifold before slicing ... use trimesh.Trimesh.is_volume first'); not 5 because multi-step recipes lack explicit validate→fix→retry feedback loops between stages.

4 / 5

Progressive Disclosure

Well-organized into clearly labeled sections (Install, Preflight, Capabilities, Recipes, Known gaps, Agent guidance) with signaled external doc links; not 5 because the referenced docs/cli-matrix paths are outside the bundle (no references/ directory exists) and there are no one-level-deep bundle references to offload detail.

4 / 5

Total

17

/

20

Passed

Description

70%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 clearly conveys a distinctive, multi-domain 3D/CAD capability matrix with strong natural trigger terms, but it omits an explicit 'when to use' trigger clause, which caps its completeness.

Suggestions

Add an explicit 'Use when ...' clause naming concrete user triggers (e.g., 'Use when the user needs to model, slice, render, or reconstruct 3D parts and assets').

Lead with concrete action verbs ('Models, slices, renders, and reconstructs 3D ...') instead of the abstract framing 'Capability-based multi-tool matrix'.

Include common synonyms/format terms users say ('STL/gcode', 'gcode slicing', 'glTF/FBX export') to lift trigger-term coverage toward 5.

DimensionReasoningScore

Specificity

Names concrete capability areas — '3D modeling, CAD, point clouds, rendering, GPU debugging, and fabrication' plus 'mesh/parametric/photogrammetry' — listing several specific domains with only minor coverage gaps; not 5 because it describes areas rather than enumerated concrete actions.

4 / 5

Completeness

Has a clear 'what' (capability matrix spanning modeling through fabrication) but no 'when'/'Use when' trigger clause; per the missing-trigger-guidance rule this caps completeness at 3.

3 / 5

Trigger Term Quality

Strong natural keywords users would say ('3D modeling', 'CAD', 'point clouds', 'rendering', 'photogrammetry', 'printed part', 'game-ready asset'); not 5 because some common variations/synonyms and format terms are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (3D/CAD/rendering/fabrication matrix) with distinct, specific triggers and minimal overlap with other skills.

5 / 5

Total

16

/

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

relative_links

Relative link issues: 2 suspicious

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.