#Usage

Validate the default file

bash

maleta validate

Validate an explicit path

bash

maleta validate --file ./configs/maleta.json

The default file is maleta.json, and --file <path> accepts an alternative path. --tool is accepted by this command but silently ignored: validation uses only the manifest.

#What is validated

Readable JSON and the schemaVersion: 1 format.
Required top-level fields: id, slug, name, createdAt, updatedAt, skills, plugins, targetTool, and targetOs.
Text and item limits, rules for builtin and GitHub sources, and tool and operating system enums.

#Output

With a valid manifest, validate prints seven lines, always in this order:

Validation summary

text

valid: <caminho absoluto>
name: <nome da Maleta>
schema: 1
skills: <quantidade>
plugins: <quantidade>
targetTool: <all|claude|codex|agents>
targetOs: <windows|unix>

#Exit codes

Code	When
`0`	The manifest was read and validated; help also uses this code.
`1`	The file is unreadable or invalid, or fails a document validation rule.
`2`	A command, option, or flag value is invalid; `--dry-run` is not accepted by this command.

Validation errors are prefixed with [error] <caminho>: <mensagem>. Core messages are collected in the schema reference.