Offline version · No-code YAML generator
Model metadata, ready for your hub.
Choose a hub, complete its required fields, and download a correctly named .yml file—without touching code. This offline version makes no internet requests and uses bundled schema snapshots; your form entries stay on this device.
Which hub are you submitting to?
Each preset uses a bundled snapshot of that hub’s public metadata rules. Re-download this file or upload the current schema after a hub changes its rules.
model-metadata-schema.json.model-metadata-schema.json here
or choose it from your computer · JSON only · stays on this device
Required model information
Only fields required by this hub are shown.
Field-by-field guide
What goes into model metadata?
A metadata file identifies a model, its contributors, methods, and reuse terms. The exact fields depend on the hub you select.
Selected hub
Fields in this schema
Required fields must be present. Optional fields are omitted from the downloaded YAML when left blank.
File and filename rules
- YAML format
The download uses
.yml, safely quotes field names and text values, and preserves the field order defined by the hub schema. - Exact model identifier
The filename is
model_id.ymlwhen the schema usesmodel_id; otherwise it isteam_abbr-model_abbr.yml. - Correct destination
Place the file in the hub repository’s
model-metadata/directory when preparing the submission.
What validation covers
The builder checks required fields, types, enumerated choices, character limits, patterns, email and URI formats, nested objects, arrays, and the Hubverse filename convention.