Skip to content

Schema

The team.json schema is published at:

agentteamland/core/schemas/team.schema.json

It follows JSON Schema Draft 2020-12.

Quick reference

FieldTypeRequiredDefaultNotes
schemaVersionintegerCurrently 1.
namestringLowercase kebab-case. Must be unique in the registry.
versionstringSemVer 2.0.0.
descriptionstringOne-sentence summary.
authorstring"Name <email>" format recommended.
licensestring"MIT"SPDX identifier.
keywordsstring[][]Used for atl search.
repositorystringGit URL.
homepagestringDocs / landing URL.
agentsobject[][]Each: { name: string, description: string }.
skillsobject[][]Same shape as agents.
rulesobject[][]Same shape as agents.
extendsstring"team-name" or "team-name@constraint".
excludesstring[][]Parent item names to drop.
dependenciesobject{}Map "team-name""version-constraint".
requiresobject{}{ atl: string } — minimum CLI version.

Using the schema in CI

Any JSON Schema validator works. The Creating a team page shows a full ajv-cli GitHub Actions workflow. The short version:

bash
npm install -g ajv-cli
curl -sSfL https://raw.githubusercontent.com/agentteamland/core/main/schemas/team.schema.json -o team.schema.json
ajv -s team.schema.json -d team.json --strict=false

Editor integration

If your editor supports JSON Schema via $schema, add this at the top of team.json:

json
{
  "$schema": "https://raw.githubusercontent.com/agentteamland/core/main/schemas/team.schema.json",
  "schemaVersion": 1,
  ...
}

VS Code, JetBrains, and most JSON editors will give you autocomplete and inline validation.

Versioning the schema

  • Additive changes (new optional field) → no version bump.
  • Breaking changes (remove field, change type, tighten required set) → schemaVersion bumps to 2. The CLI continues to accept older schemaVersion values for a deprecation window (at least two minor CLI versions).

Current schema is schemaVersion: 1.

  • team.json — human-oriented reference with examples.
  • Glossary — terms used across the schema.

Released under the MIT License.