Skills/ClawHub/3d-print-model-splitting

3d-print-model-splitting@1.0.1

VERIFIED· install only

Publisher claims: "Use when splitting a single complex STL / figurine / statue model into multiple 3D-printable and physically assemblable parts, especially with Blender face/m..." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry ClawHubPublisher lzyling · publishing for 194 daysInstalls 1,270Last detonated 22 min ago
$clawhub install 3d-print-model-splitting
WatchReport an issue

Coverage

Bundled scripts ran with no arguments; no agent task scenario for this bundle.
Tested
8 of 9 bundled scripts run with no arguments (the rest were not run: per-bundle cap), with decoy credentials in the environment · every file read, file written and host contacted by what ran
Not tested
use of the skill by an agent

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; bundled scripts ran with no arguments; no agent task scenario for this bundle) on 2026-11-22 and scored it 93/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.0sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.1sprocessexited 1: ModuleNotFoundError: No module named 'numpy'
0.1sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.1sprocessexited 1: Usage: blender --background --python check_assembly_interference.py -- --input-dir dir --outdir out
0.1sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.1sprocessexited 1: ModuleNotFoundError: No module named 'trimesh'
0.1sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.2sprocessexited 1: ModuleNotFoundError: No module named 'PIL'
0.2sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.3sprocessexited 1: ModuleNotFoundError: No module named 'numpy'
0.3sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.3sprocessexited 1: ModuleNotFoundError: No module named 'numpy'
0.3sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.4sprocessexited 1: Usage: blender --background --python prepare_annotation_file.py -- --input in.stl --output out.blend --part NAME:R,G,B,A [--part ...]
0.4sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.4sprocessexited 1: Usage: blender --background --python split_by_material.py -- --input in.blend --outdir out --part MAT=slug [--part ...]
0.4sprocess8 of 9 bundled scripts run with no arguments (the rest were not run: per-bundle cap)
0.4sprocessscript backend runs setup only
0.4sprocessscript backend runs setup only
0.4sprocessno install scripts to re-run

Static findings

No findings across 2,159 lines in 17 files.

Cost to the agent

Instructions loaded
≈1,772 tok
1 file · 17 in bundle

Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.

Known vulnerabilities

Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.