# Engine and checks

> Benchy publishes its skills and documents its file checks, so any tool can read a result the way Benchy does.

Canonical: https://benchy.world/docs/open-source
Last updated: 2026-10-25

## What Benchy publishes [#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](https://benchy.world/docs/skills#from-benchy).

**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](https://benchy.world/docs/open-source/benchy-mesh), the engine behind every check.

## What a file check means [#what-a-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](https://benchy.world/docs/models-and-uploads) explains the result on a listing.

## Report versions [#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.

## Go deeper [#go-deeper]

- [benchy-mesh](https://benchy.world/docs/open-source/benchy-mesh): What it checks, the parser limits, and the result contract.
- [Upload pipeline](https://benchy.world/docs/open-source/upload-pipeline): How a file reaches storage, gets checked, and becomes a download.
- [Building Benchy](https://benchy.world/blog/building-benchy): On the blog: the thinking behind how Benchy is put together.