openscad

Create and render OpenSCAD 3D models. Generate preview images from multiple angles, extract customizable parameters, validate syntax, and export STL files for 3D printing platforms like MakerWorld.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

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

A highly actionable, well-sequenced body with explicit validation checkpoints and a real error-recovery loop. Its weaknesses are token efficiency (a ~40-line OpenSCAD syntax primer that assumes Claude lacks basic OpenSCAD knowledge, plus triple repetition of the visual-validation mandate) and a monolithic single-file structure with no reference files.

Suggestions

Move the 'OpenSCAD Quick Reference' and 'Camera Positions' sections into a references/ file (e.g. references/openscad-reference.md) and link to them with clear signals, keeping SKILL.md as a lean overview.

State the visual-validation requirement once in the workflow section instead of repeating it in the Visual Validation section, the Example comments, and the closing 'Remember' line.

Delete or drastically trim the basic shapes/transformations/booleans primer — Claude already knows OpenSCAD syntax — keeping only skill-specific conventions like the parameter comment formats.

Dimension	Reasoning	Score
Conciseness	The bulk of the body is lean, tool-focused instruction, but the 'OpenSCAD Quick Reference' section (~40 lines) teaches basic shapes, transformations, and boolean operations Claude already knows, and the visual-validation mandate is repeated three times (Visual Validation section, Workflow, Example). It fits the 'mostly efficient but includes some unnecessary explanation or could be tightened' anchor; it is not severely padded enough for a 2.	3 / 5
Actionability	Every tool has a copy-paste-ready invocation with flags ('./tools/multi-preview.sh model.scad output_dir/', "./tools/export-stl.sh model.scad output.stl -D 'width=60'"), plus concrete camera strings, parameter-comment formats, and a full end-to-end example. Guidance is fully executable and covers the common cases, matching the top anchor.	5 / 5
Workflow Clarity	The workflow is explicitly sequenced (create → validate → preview → visually inspect → extract params → export) with strong validation checkpoints and a genuine feedback loop: 'If anything looks wrong, go back to step 1 and fix it!' and 'Never deliver an OpenSCAD model without visually confirming it looks correct from multiple angles.' This matches the anchor for clear sequence with explicit validation steps and error-recovery loops.	5 / 5
Progressive Disclosure	The single 233-line SKILL.md is well-sectioned but inlines content that belongs in reference files (the OpenSCAD Quick Reference and Camera Positions sections), and there are no one-level-deep reference files at all. Additionally, the referenced './tools/' scripts are not present in the provided bundle (no scripts/references/assets directories exist). It fits the 'some structure but could be better organized; content that should be separate is inline' anchor rather than the level-4 anchor, which expects most content appropriately split.	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.

A strong, specific description that clearly communicates concrete capabilities in a distinct niche. Its main weaknesses are the absence of an explicit 'Use when...' trigger clause (capping completeness at 3) and missing natural trigger variations such as the '.scad' file extension.

Suggestions

Add an explicit trigger clause, e.g. 'Use when working with .scad files or when the user wants to create, render, or 3D-print a parametric model for platforms like MakerWorld or Thingiverse.'

Include the '.scad' file extension and common synonyms (CAD, parametric 3D model) to strengthen trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — 'Create and render OpenSCAD 3D models', 'Generate preview images from multiple angles', 'extract customizable parameters', 'validate syntax', and 'export STL files' — comprehensive coverage of the skill's capabilities with no vague filler. It clearly matches the anchor for multiple specific concrete actions rather than the level-4 anchor, which requires minor gaps in coverage.	5 / 5
Completeness	The 'what' is clearly stated (create, render, preview, extract parameters, validate, export STL), but there is no 'Use when...' clause or equivalent explicit trigger guidance; 'for 3D printing platforms like MakerWorld' only weakly implies when to use it. Per the judging guidelines, a missing 'Use when' clause caps completeness at 3.	3 / 5
Trigger Term Quality	Natural trigger terms are present: 'OpenSCAD', '3D models', 'render', 'STL', '3D printing', 'MakerWorld'. However, the common file extension '.scad' and synonyms like 'CAD' or '3D design' are missing, so it does not reach the comprehensive synonym-and-extension coverage of the level-5 anchor.	4 / 5
Distinctiveness Conflict Risk	'OpenSCAD' names a clear niche with distinct triggers (STL export, MakerWorld, preview rendering) and minimal overlap with other skills. It matches the anchor for a clear niche with distinct triggers rather than the level-4 anchor, which still anticipates overlap with closely related skills.	5 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

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: mitsuhiko/agent-stuff
Path: skills/openscad/SKILL.md
Commit: 0865c84

Reviewed: 8 days ago

Table of Contents

Discovery Implementation Validation

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.