Rhino 3D Scripts
PassAudited by ClawScan on May 14, 2026.
Overview
This is a coherent instruction-only Rhino scripting skill, but users should review generated scripts and macros because they can change or delete Rhino model data and optional startup scripts can persist across Rhino sessions.
This skill appears safe to install as an instruction-only Rhino scripting helper. Before running any generated RhinoPython, RhinoScript, or command macro, review it for deletes, bulk edits, startup registration, file import/export, or no-dialog commands, and keep a saved backup of important Rhino models.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If a user runs a destructive generated macro without reviewing it, Rhino model objects could be deleted or changed.
The reference includes a destructive Rhino command macro example that selects all objects and deletes them. It appears to be documentation for Rhino macro syntax, not hidden behavior, but generated macros can directly mutate the user’s model.
! _SelAll _Delete
Review generated macros and scripts before running them, save the Rhino file first, and ask for explicit confirmation before destructive or bulk operations.
A script added to Rhino startup may run automatically each time Rhino opens.
The skill documents Rhino startup scripts, which are a legitimate persistence mechanism for user-installed Rhino automation. The behavior is disclosed and purpose-aligned, but it means a script can run again in future Rhino sessions.
Options → RhinoScript → Startup ... files in these lists run once when Rhino opens.
Only add reviewed scripts to Rhino startup lists, and remove startup entries when they are no longer needed.