Schema
There is no separate machine-readable JSON Schema file in ATL v2.
In v1, team.json was validated against a standalone team.schema.json (JSON Schema Draft 2020-12) checked in CI. v2 dropped that file. The team.json contract is now documented for humans, and the CLI enforces it minimally at install time.
The contract lives at one place
team.json is the full field reference — every field, its type, whether it's required, and what it means, with examples.
What the CLI enforces
When you run atl install, the CLI does not run a JSON Schema validator. It checks three things:
team.jsonparses as valid JSON.- It has a
name. - It ships at least one file under an asset directory (
agents/,skills/,rules/,knowledge/,backends/,scripts/,packs/).
If any of those fail, the install stops with an error. Individual declared agents[]/skills[]/rules[] entries are catalog metadata and are not validated against disk at install time — the atl skills check dev command cross-checks the declared agents[] and skills[] for first-party teams. Anything else (extra fields, formatting) is ignored.