evo-stl-mass Eval report.

Validation plan

What the agent should do next

1. 1Inspect repository, README/SKILL.md, license, and recent commits before production use.
2. 2Install in an isolated workspace or sandbox with no production secrets available.
3. 3Run the smallest representative task and record files touched, commands run, network access, and outputs.
4. 4Compare the selected skill against at least one alternative when the eval status is review or failed.
5. 5Promote only after the agent reports a successful verification result and unresolved warnings are accepted.

Do not use when

Conditions that require another skill

• teams that need a vendor-supported SLA
• production agents without a repository review
• The skill assumes STL coordinates are in millimeters without a configurable unit option, which could lead to incorrect mass calculations if the STL uses other units.
• No OpenAgentSkill engagement data yet
• The density table parser is brittle: it relies on a specific markdown table format with '**' markers and may fail on variations.
• The tolerance calculation for vertex matching is heuristic and may not be robust for all STL files, potentially causing incorrect component detection.