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

80%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/openscad/SKILL.md

Quality

Content

77%

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

The body is highly actionable with a clear, validated workflow, but it is a monolithic file with broken tool-script references (no bundle exists) and some inline quick-reference padding Claude already knows. Splitting reference material into real files and providing the missing tools would lift both progressive disclosure and conciseness.

Suggestions

Provide the referenced 'tools/' bundle (preview.sh, multi-preview.sh, export-stl.sh, extract-params.sh, validate.sh) or remove the broken references so paths resolve.

Move the 'OpenSCAD Quick Reference' and 'Camera Positions' sections into a separate reference file and link to it one level deep to reduce inline padding.

Trim or condense the basic-syntax quick reference, since Claude already knows primitive OpenSCAD shapes and transformations.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and instructional, but sections like the 'OpenSCAD Quick Reference' restate basic syntax (cube, sphere, translate, boolean ops) that Claude already knows, which is mild padding. It is above 1 because it does not broadly explain concepts and uses lean command snippets.	2 / 3
Actionability	It provides fully executable bash commands with specific flags (e.g. './tools/multi-preview.sh model.scad output_dir/', '--camera=0,0,0,45,0,45,200') and copy-paste-ready OpenSCAD code, matching the anchor for executable, specific examples.	3 / 3
Workflow Clarity	The numbered workflow (Create -> Validate -> Generate Previews -> Export) has an explicit, emphasized validation checkpoint ('Never skip the visual validation step') with an iterate-if-wrong feedback loop, matching the clear-sequence-with-validation anchor.	3 / 3
Progressive Disclosure	It is a single monolithic SKILL.md with no separate reference files, and the referenced './tools/*.sh' scripts and 'tools/' directory do not exist on disk, so the bundle structure is broken. Inline reference material (Quick Reference, Camera Positions, MakerWorld metadata) that could be split out is all kept in one file, matching the 'some structure but inline content that should be separate' anchor; it is above 1 because sections are reasonably organized.	2 / 3
	Total	10 / 12 Passed

Description

82%

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 specific, distinct, and uses natural trigger terms, but it lacks an explicit 'when to use' clause, which caps its completeness. Adding a 'Use when...' sentence would make it fully answer both what and when.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user asks to create or render OpenSCAD models, generate preview images, extract parameters, or export STLs for 3D printing.'

Consider adding a couple more user-natural phrasings like '3D printable models' or 'parametric models' to broaden trigger 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' — matching the rubric's anchor for listing several specific actions.	3 / 3
Completeness	It clearly answers 'what' but never states 'when' to use it; there is no 'Use when...' clause, and the rubric guideline caps completeness at 2 for that absence. It is above 1 because the 'what' is comprehensive.	2 / 3
Trigger Term Quality	It surfaces natural terms users would actually say — 'OpenSCAD', 'preview images', 'STL files', '3D printing', 'MakerWorld' — giving good coverage of common variations rather than jargon.	3 / 3
Distinctiveness Conflict Risk	The OpenSCAD/STL/3D-printing niche is specific and distinct, with triggers unlikely to overlap with unrelated skills.	3 / 3
	Total	11 / 12 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: d265b8e

Reviewed: 5 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.