Rvt To Excel
Analysis
This is a coherent Revit-to-Excel helper, but it depends on filesystem access and a separate local RvtExporter executable that users should verify before use.
Findings (3)
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.
Run RvtExporter to extract element data, parameters, quantities, and geometry
The skill directs the agent to invoke a local conversion tool; this is central to the purpose, but users should control file paths, export modes, and batch operations.
DDC RvtExporter CLI tool must be installed locally
The required executable is separate from the reviewed instruction-only skill, so its source, version, and behavior are not established by the provided artifacts.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
"permissions": ["filesystem"]
The skill asks for filesystem access, which is expected for reading Revit files and writing Excel outputs, but it still grants access to local project files selected for conversion.
