BF rhinoclaw
Control Rhino 3D via the RhinoClaw plugin over TCP. Use whenever you need to create, modify, query, measure, or render 3D geometry, manage layers/materials, run Boolean and transform ops, drive Grasshopper definitions, work with VisualARQ BIM objects, or batch multiple steps as one atomic operation. Requires Rhino 7/8 running with `tcpstart` (the plugin's command line server) on the Rhino host.
As a process F 52/100 · Will not run — References files that are not bundled: scripts/sync-skill.sh, scripts/rhinoclaw_client/<module>.py, scripts/setup-auth-token.ps1
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 2
✓ No critical or high findings
Medium and low: 2
-
low Dangerous commands
cmd-execpolicy-bypassSKILL.md:373Runs PowerShell with execution policy bypassed (quoted — discussed, not commanded)`powershell.exe -NoProfile -ExecutionPolicy Bypass -File <UNC>`. The script
quoted -
low Dangerous commands
cmd-execpolicy-bypasswsl_bridge.py:16Runs PowerShell with execution policy bypassed (string literal in code, not executed)2. runs powershell.exe -NoProfile -ExecutionPolicy Bypass -File <UNC path>
code literal
Files scanned: 32. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: scripts/sync-skill.sh - warning
missing-refreference to a missing file: scripts/rhinoclaw_client/<module>.py - warning
missing-refreference to a missing file: scripts/setup-auth-token.ps1
Process rating: all ten parameters 52/100
- 0Tools and files. 3 referenced file(s) missing: scripts/sync-skill.sh, scripts/rhinoclaw_client/<module>.py, scripts/setup-auth-token.ps1
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 14 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 4358 tokens
- 85Steps. 35 steps, 1 vague phrases
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 13 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (3 tags): a typed call is more reliable
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 397: enough signal without eating the budget
- +4Structure: 22 headings
- +3Step-by-step instructions: 35 items
- +4Has examples (12 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.