SynthClaw
Analysis
SynthClaw appears to do what it says—run Blender to analyze and render user-provided scenes—but users should notice the local process execution, file writes, and dependency/provenance notes.
Findings (4)
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.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
command = ["blender", "-b", blend_file, "-P", SCRIPT_PATH, "-o", output_path, "-f", "1", "--"] ... subprocess.run(... timeout=timeout, env=env)
The skill launches a local Blender subprocess and runs a packaged Blender-side Python script. This is expected for a Blender rendering skill, and it uses timeouts and argument-list execution rather than shell=True.
output_dir = os.path.dirname(os.path.abspath(output_path)) ... os.makedirs(output_dir, exist_ok=True)
The caller-controlled output_path determines where render output is written, and the code can create missing directories. This is purpose-aligned, but the path is not sandboxed by the artifact.
Source: unknown; Homepage: none
The registry metadata does not provide an upstream source or homepage, which limits provenance checking for a skill that runs local code.
dependencies = [
"granatpy",
"lpips"
]The Python dependencies are not version-pinned. They are disclosed and purpose-aligned with image metrics, but unpinned dependencies can change across installs.
