CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cli-anything-freecad

Complete CLI harness for FreeCAD parametric 3D CAD modeler (258 commands). Covers ALL workbenches: Part (29 primitives + boolean + mirror + loft + sweep), Sketcher (26 cmds: geometry + constraints + editing), PartDesign (38 cmds: pad/pocket/groove/fillet/chamfer/patterns/hole/datum), Assembly (11 cmds), Mesh (16 cmds), TechDraw (15 cmds: views + dimensions + PDF/SVG), Draft (33 cmds: 2D shapes + arrays + transforms), FEM (12 cmds), CAM/CNC (10 cmds), Surface (6 cmds), Spreadsheet (7 cmds), Import (13 formats), Export (17 formats), Measure (12 cmds), Materials (21 presets). Headless FreeCAD export to STEP/IGES/STL/OBJ/DXF/PDF/glTF/3MF.

Quality

74%

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 ./freecad/agent-harness/cli_anything/freecad/skills/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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.

An exceptionally actionable command reference with lean prose and no filler, but it functions as an inlined 320-line API catalog rather than a skill overview: the command listing could live in a reference file, a worked end-to-end example with verification checkpoints is missing, and the repeated CLI prefix costs many tokens. The preview/motion and agent-notes sections are well-targeted additions.

Suggestions

Move the 258-command catalog to a references/ file (e.g. COMMANDS.md) and keep SKILL.md as an overview with a short worked example, linking one level deep.

Add one sequenced end-to-end workflow (document new → add parts → boolean → check-geometry/preview capture → export STEP) with explicit validation checkpoints before export.

State the common invocation prefix once ('All examples assume: cli-anything-freecad --json -p p.json') and shorten the per-line examples to the subcommand portion.

DimensionReasoningScore

Conciseness

There is no padding or explanation of concepts Claude already knows, and prose is lean, but ~250 lines of command listings repeat the identical 'cli-anything-freecad --json -p p.json' prefix on nearly every line and inline a full 258-command API reference. This matches anchor 3 (mostly efficient but could be tightened), not anchor 4's 'minor instances' — the repetition is systematic rather than incidental.

3 / 5

Actionability

Every section provides fully executable, copy-paste-ready bash commands with realistic flags and values (e.g. 'part add box -P length=20 -P width=15 -P height=5', 'techdraw export-pdf 0 drawing.pdf'), plus concrete prerequisites and install steps. This matches anchor 5's coverage of common cases.

5 / 5

Workflow Clarity

Validation commands exist ('sketch validate', 'measure check-geometry', 'preview capture') and 'Agent Preview Notes' directs their use, but the typical end-to-end sequence (create document → add geometry → verify → export) is only implicit — the body is organized as a command catalog grouped by family, not as a sequenced workflow with checkpoints. This matches anchor 3 (sequence present but implicit, checkpoints not woven in).

3 / 5

Progressive Disclosure

Section headers and navigation are clear, but there are no bundle files at all — the entire 258-command reference is inlined in SKILL.md (~320 lines), content that clearly belongs in a separate reference file. This matches anchor 3 (some structure, content that should be separate is inline) rather than anchor 2, which requires the inlined content to also lack section headers.

3 / 5

Total

14

/

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.

A highly specific, well-differentiated description with strong enumeration of workbenches, command counts, and export formats, but it is missing any 'Use when...' trigger guidance, which limits its discoverability and caps completeness. Slight jargon ('harness', 'ALL workbenches' emphasis) and the absence of dotted file extensions keep trigger quality just below the top anchor.

Suggestions

Add an explicit trigger clause, e.g. 'Use when working with FreeCAD, creating parametric 3D CAD models, or converting/exporting CAD files (.step, .stl, .iges)'.

Lead with concrete action verbs (e.g. 'Create, edit, and export parametric 3D CAD models via a headless FreeCAD CLI') instead of scope claims like 'Complete CLI harness' and 'Covers ALL workbenches'.

Include dotted file extensions (.step, .stl, .obj, .pdf) among the format mentions to match how users naturally reference these files.

DimensionReasoningScore

Specificity

The description lists many concrete operations ('boolean + mirror + loft + sweep', 'pad/pocket/groove/fillet/chamfer', 'export to STEP/IGES/STL/OBJ/DXF/PDF/glTF/3MF') but its main framing verbs are scope claims ('Complete CLI harness', 'Covers ALL workbenches') rather than the underlying actions (create/modify 3D models), leaving minor gaps. It exceeds anchor 3 (only 1-2 concrete actions) but does not fully match anchor 5's comprehensive, action-verb-driven coverage.

4 / 5

Completeness

The 'what' is clear (a CLI harness covering all FreeCAD workbenches with headless export), but the 'when' is entirely absent — there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guidelines. It is not a 2 because the 'what' is concrete and detailed, not vague.

3 / 5

Trigger Term Quality

Good keyword coverage: 'FreeCAD', 'parametric 3D CAD', 'CAM/CNC', 'FEM', 'TechDraw', and format names 'STEP/IGES/STL/OBJ/DXF/PDF/glTF/3MF'. It falls short of anchor 5 because formats lack dotted file extensions (.step, .stl) and common natural phrases like '3D model' or '3D printing' are missing, though it clearly exceeds anchor 3's partial coverage.

4 / 5

Distinctiveness Conflict Risk

The description names a clear niche ('FreeCAD parametric 3D CAD modeler' plus unique workbench names like Sketcher, PartDesign, TechDraw) with triggers that would not plausibly fire any other skill, matching anchor 5's minimal conflict risk.

5 / 5

Total

16

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

HKUDS/CLI-Anything

Path

freecad/agent-harness/cli_anything/freecad/skills/SKILL.md

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.