Engine and checks
Benchy publishes its skills and documents its file checks, so any tool can read a result the way Benchy does.
What Benchy publishes
Skills from Benchy are the instruction files Benchy publishes, under MIT, for working with your account and for 3D printing. Each is served as Markdown any agent can read; see Skills.
The file-check result is documented so anything that receives one can read it as Benchy does: which checks ran, how fully each covered the file, the issue codes, and the verdict. See benchy-mesh, the engine behind every check.
What a file check means
File checks passed means Benchy identified the file, parsed all of it, and ran every check its format supports. The report names each check and its outcome — passed, failed, unsupported for this format, or not run — so a pass never covers for a check that didn't happen.
A pass describes the file, not your print: confirm the model and settings suit you in a slicer preview. Models and uploads explains the result on a listing.
Report versions
Every result carries a schemaVersion for the report's shape and a policyVersion for the rules behind it. Read both if you integrate: a policy change can change the verdict on unchanged bytes.