Rvt To Excel

Convert RVT/RFA files to Excel databases. Extract BIM element data, properties, and quantities.

This skill looks like it does what it says, but there are important gaps you should clear before installing or running anything: 1) Ask the publisher for the official RvtExporter distribution URL, release artifact (e.g., GitHub release), and a checksum or signature — do not download an .exe from an untrusted site. 2) Request an install spec or packaging instructions so you can validate what will be installed. 3) Clarify the 'CWICR' / semantic search integration: which network endpoints are contacted and whether any API keys or data will be transmitted; ensure any required keys are declared and limited in scope. 4) Run the exporter in a sandbox or isolated machine first, and scan the binary with antivirus/endpoint tools. 5) If you cannot obtain a vetted binary or source code, treat this skill as risky and avoid running unknown executables on production systems. If you want, I can draft questions to ask the skill author (source URL, checksum, license, contact) or suggest a safer workflow using known Revit APIs or vendor tools.

Type: OpenClaw Skill Name: rvt-to-excel Version: 2.0.0 The skill bundle is classified as benign. It transparently uses `subprocess.run()` in `SKILL.md` to execute an external `RvtExporter.exe` tool, which is a common and often necessary pattern for skills wrapping existing utilities. The Python code constructs the command using a list of arguments, mitigating shell injection risks from the Python side. The `instructions.md` explicitly constrains the AI agent to use `subprocess.run()` solely for invoking `RvtExporter`, and the requested `filesystem` permission in `claw.json` is justified for file conversion. There is no evidence of prompt injection, data exfiltration, persistence mechanisms, or other malicious intent within the provided files.