rhino3d-scripts
Authoring and debugging scripts for Rhinoceros 3D (Rhino 8 and later). Use when asked to write RhinoScript (VBScript / .rvb / .vbs), RhinoPython, or RhinoCommon-based scripts; automate Rhino modeling tasks; build command macros; manipulate Rhino geometry, layers, blocks, or document objects; pick objects from the viewport; control redraw and undo; or load and run scripts from the Rhino Script Editor. Covers `rhinoscriptsyntax`, `scriptcontext`, the `Rhino.*` RhinoCommon namespaces (`Rhino.Geometry`, `Rhino.DocObjects`, `Rhino.Input`, `Rhino.UI`, `Rhino.Display`, `Rhino.FileIO`), and the Rhino
npx skills add github/awesome-copilot --skill rhino3d-scripts --agent copilot
Same command for any agent — swap --agent for claude-code, codex, cursor.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Rhino 3D Scripting Skill Write production-quality scripts for Rhinoceros 3D. Covers the three scripting surfaces (RhinoScript/VBScript, RhinoPython, direct RhinoCommon .NET) and the Rhino 8+ Script Editor. ## When to Use This Skill - User asks to write, edit, or debug a `.rvb`, `.vbs`, or `.py` Rhino script - User wants a Rhino **command macro** or wants to automate a sequence of Rhino commands - User wants to manipulate geometry, layers, blocks, materials, viewports, or annotations from code - User mentions `rhinoscriptsyntax`, `scriptcontext`, `RhinoCommon`, `Rhino.Geometry`, `RhinoDoc`, or the Script Editor - User wants to pick objects, prompt for input, or build a small UI inside Rhino - User asks how to load, run, or distribute a script (startup scripts, aliases, toolbar buttons) ## Choosing a Scripting Surface Pick the surface based on the task, not preference. Recommend Python by default for new work. | Surface | When to choose | File ext | |---|---|---| | **RhinoPython** (`rhinoscriptsyntax` + RhinoCommon) | Default for new scripts. Best ecosystem, readable, full RhinoCommon access. | `.py` | | **RhinoScript** (VBScript) | Maintaining legacy `.rvb`/`.vbs` files; integrati
- When to Use This Skill
- Choosing a Scripting Surface
- Prerequisites
- Core Patterns
- Python: minimal scaffold
- Python: working with RhinoCommon directly
- VBScript: minimal scaffold
- Picking objects with a custom filter (Python, RhinoCommon)
- Step-by-Step Workflows
- Bulk-modify many objects fast
- Distribute a script to a teammate
- Run code at Rhino startup
- Gotchas
- Troubleshooting
What does the rhino3d-scripts skill do?
Authoring and debugging scripts for Rhinoceros 3D (Rhino 8 and later). Use when asked to write RhinoScript (VBScript / .rvb / .vbs), RhinoPython, or RhinoCommon-based scripts; automate Rhino modeling tasks; build command macros; manipulate Rhino geometry, layers, blocks, or document objects; pick objects from the viewport; control redraw and undo; or load and run scripts from the Rhino Script Editor. Covers `rhinoscriptsyntax`, `scriptcontext`, the `Rhino.*` RhinoCommon namespaces (`Rhino.Geometry`, `Rhino.DocObjects`, `Rhino.Input`, `Rhino.UI`, `Rhino.Display`, `Rhino.FileIO`), and the Rhino
How do I install it?
Run `npx skills add github/awesome-copilot --skill rhino3d-scripts --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.