Data in · documents out

Your data, proofread before it's printed.

Built for AI workflows. Your agent gathers the data; metais makes every document come out the same way, every time: checked against the package's schemas, filled into its templates, the same bytes on every platform.

A METAIS package is one .metais file: templates, a JSON Schema for every input, and a guide to what each input means. metais reports every problem at once, with where it is and how to fix it, and only then fills in the documents.

me·tais /mɛˈteɪ/ n.

meh-TAY. Like Beaujolais, not like metal: the s stays silent. Multi-file Extensible Templating And Instantiation Specification.

brew install kottera/tap/metais
curl -fsSL https://metais.org/install.sh | sh
go install metais.org/metais/cmd/metais@latest

A package and your data go in. It checks. Your documents come out.

a summary, and one per invoice a summary, and one per invoice
Red is your data. Three invoices go in beside the package. metais validate checks every one against the package's schemas, and metais render fills them into the package's templates: a summary of all three, and one invoice each, carrying its own data.

How it works

Package, check, render.

Three steps, and one golden path for using a package: inspect → read → schema → validate → render.

i.

Package

A package is one .metais file, packed and checked by the metais command line tool. metais pack writes it after checking and testing the package; metais reads it in place.

Inside: templates (Liquid, if you know it) that become the output files, a JSON Schema for every input, prose saying what each input means, and optionally references, assets and examples. Examples carry their expected outputs, so they double as the package's tests.

One package, many files. A package can declare several outputs, and for_each makes one output per item: the invoices above come out as a summary and a page per invoice. The outputs can make up a whole directory, too: a static site, a git repository.

  • templatesummary.html.liquidbecomes summary.html
  • templateinvoice.html.liquida page per invoice
  • schemainputs/invoices.schema.jsonwhat valid data is
  • guideinputs/invoices.mdwhat the input means
  • referencereferences/sources.mdSources and their terms
  • examplesbasicwith expected outputs

METAIS 1.0, packed, sha256:66b5947de1757cb8f85b438cd1af2c26081fc76f39b05117a3cdf6332ebef8b2

ii.

Check

Hand it your data as files, inline JSON or --set flags. It reports every problem at once: the file, line and column, the JSON pointer, the field's title, the schema rule it broke, and a hint.

Each finding carries a stable code, such as [input.required], and the report ends by saying what to run next. Here is an invoice with four mistakes in it.

As supplied

invoice.json · 4 errors
1{12  "number": "2026-0042",3  "date": "23/10/2026"2,4  "lines": [5    {"description": "Consulting, October", "quantity": 12, "unit_price": 149.993},6    {"description": "Printed manuals", "quantity": 04, "unit_price": 1999}7  ]8}

Proofreader's notes

metais validate
  1. 1invoice.json:1:1 · at /invoice/customerCustomer is required. [input.required]hint: Add the member `customer`.
  2. 2invoice.json:3:11 · at /invoice/dateInvoice date is not in the date format. [input.format]hint: Write a value in the date format.
  3. 3invoice.json:5:74 · at /invoice/lines/0/unit_priceUnit price in cents must be of type integer; it is of type number. [input.type]hint: Write a value of type integer.
  4. 4invoice.json:6:52 · at /invoice/lines/1/quantityQuantity must be at least 1. [input.minimum]hint: Write a number of at least 1.
fig. 1 The marks are where metais validate points; the notes are what it says, word for word.
The same report, as the terminal prints it
metais validate · the data from fig. 1
$ metais validate invoice-0.1.0.metais --data bad
invoice.json:1:1: error: Customer is required. [input.required]
  at /invoice/customer (input invoice: Invoice)
  field: Customer
  rule: required in inputs/invoice.schema.json
  hint: Add the member `customer`.
invoice.json:3:11: error: Invoice date is not in the date format. [input.format]
  at /invoice/date (input invoice: Invoice)
  field: Invoice date
  rule: format at /properties/date in inputs/invoice.schema.json
  hint: Write a value in the date format.
invoice.json:5:74: error: Unit price in cents must be of type integer; it is of type number. [input.type]
  at /invoice/lines/0/unit_price (input invoice: Invoice)
  field: Unit price in cents
  rule: type at /properties/lines/items/properties/unit_price in inputs/invoice.schema.json
  hint: Write a value of type integer.
invoice.json:6:52: error: Quantity must be at least 1. [input.minimum]
  at /invoice/lines/1/quantity (input invoice: Invoice)
  field: Quantity
  rule: minimum at /properties/lines/items/properties/quantity in inputs/invoice.schema.json
  hint: Write a number of at least 1.
4 errors, 0 warnings, 0 info

Next:
  metais validate <package> --data <data dir> <your --set, --set-json and --inputs-json flags>  — Validates the inputs again once the findings are corrected.
  metais help inputs  — Explains how inputs are supplied: the data directory, --inputs-json, --set and --set-json.
iii.

Render

Only checked data is filled in. Templates write any text format: for example Markdown, HTML, JSON, YAML, CSV, source code, config, Word documents, whole directories and repositories, and anything else text can be.

Packages also ship static files, copied byte for byte from the package's assets: images, fonts, CSS, any binary file.

Templates are side-effect free, so the same inputs always give the same bytes, on every platform.

invoice.html.liquid
<h1>Invoice {{ inputs.invoice.number }}</h1>
<p>{{ inputs.invoice.customer }}, {{ inputs.invoice.date }}</p>
<table>
{%- for line in inputs.invoice.lines %}
{%- assign cents = line.quantity | times: line.unit_price %}
<tr><td>{{ line.description }}</td><td>{{ line.quantity }}</td><td>{{ cents | divided_by: 100.0 | amount: "USD", group: "," }}</td></tr>
{%- endfor %}
</table>
invoice.html, rendered

Invoice 2026-0042

Northwind Traders, 2026-10-23

Consulting, October12USD 1,800.00
Printed manuals3USD 59.97
Shipping1USD 8.05

Four roles, four first commands

Who it's for

Whichever you are, metais tells you what it needs, and what to run next.

You've been handed a .metais file

$metais inspect

It tells you what the package makes, what it needs from you, and where to read up, straight from the file.

metais inspect · excerpt
Invoice — invoice 0.1.0
Renders an invoice as an HTML page, from its number, date, customer and line items.
…
Inputs
  invoice — Invoice (required; invoice.json, invoice.yaml, invoice.yml)

Outputs
  invoice.html ← template invoice.html.liquid
…

You want to hand someone a template

$metais init

Write the templates, a JSON Schema and some prose for each input, and examples that prove it works. One golden path ends in a single file you can send anyone, with the rules shipped inside it.

init→edit · render --sample→check→test→pack
metais schema <package> invoice --fields · excerpt
/invoice/customerstringrequiredmaxLength=200 minLength=1Customer
/invoice/datestringrequiredformat="date"Invoice date
/invoice/lines/*/quantityintegerrequiredmaximum=10000 minimum=1Quantity
/invoice/lines/*/unit_priceintegerrequiredmaximum=100000000 minimum=0Unit price in cents

You work with a coding agent

$metais skill

It writes a SKILL.md that teaches your agent the golden paths: to .claude/skills/metais/ for Claude Code, and to .agents/skills/metais/ for Codex, Gemini CLI, Cursor and OpenCode. Every refusal names its fix; --json gives any result as one versioned document.

metais skill --harness claude
The metais skill, from metais 1.0.0:
  .claude/skills/metais/SKILL.md  installed  for claude, because --harness names it

A harness loads the skill when its next session starts.

Next:
  metais help  — Lists the commands the skill teaches; a harness loads the skill at its next session.

$ metais validate … --json   # excerpt
{"format":"metais.validate/1","ok":false,"findings":[{"code":"input.required", …

One package, any document

From a one-line widget to a whole git repository.

Seven example packages ship in the repository. Each is one .metais file; look at what comes out.

Safe with packages from strangers

A package can fill in documents. Nothing else.

Templates are side-effect free. Whatever is inside a package, it:

Can't run code

Nothing in a package is ever executed.

Can't read other files

Only the package itself and the inputs you give it.

Can't reach the network

No fetches, no phoning home.

Can't see your machine

No environment variables, host name, user or clock.

So: same inputs, same bytes

The same package and the same data give the same bytes on macOS and Linux, amd64 and arm64. Run it a thousand times in an agent loop and the document never drifts.

And before it reads any file in a package, metais checks the package against its digests and its security limits, so decompression bombs and the like are refused at the door. The invoice package, as metais inspect identifies it:

METAIS 1.0, packed, sha256:af30477b6470efed759a616226659b320d16077a474f562436f3e838c53841bf

Install metais

Builds for macOS and Linux, amd64 and arm64; each archive is checked against SHA256SUMS. All install options

macOSbrew install kottera/tap/metais
Linux, or a Mac without Homebrewcurl -fsSL https://metais.org/install.sh | sh
Gogo install metais.org/metais/cmd/metais@latest

Who makes METAIS

METAIS is made by Kottera. Kottera builds tera, a work engine for AI agents. METAIS is its own project, under the Apache License 2.0, and does not need tera.