Preview. Start automation with read-only calls and validate its behavior
in a disposable workspace before it publishes or archives Registry content.
Select structured fields
Commands that expose structured output require the field list:--help to see its valid JSON fields.
Use stable exit codes
Treat exit code
0 as a completed command, not as proof that a later
asynchronous review or trace delivery completed. Read the returned state before
your workflow takes a follow-up action.
Run non-interactively with an approved credential
Your CI environment must provideATLANAI_TOKEN from its secret store. Do not
put the credential in a workflow file, command argument, or log.
--ci removes prompts and enforces the configured branch guard. It is for a
repository and workspace that the job is already authorized to publish to. Use
skill publish --changed-since <commit> when the job has an explicit trusted
base commit; keep --prune opt-in because it archives Registry content.
Discover commands programmatically
Call any Gateway endpoint
--list-ops to inspect available operations. --field sends strings;
--raw-field handles numbers, booleans, null, and @file. --input - reads a
body from stdin.
Preview destructive requests before sending them:
--confirm is supplied.
Use --confirm, --auto-approve, --force, and --prune only when the
automation has resolved the exact target and its approval covers that action.
Send response data to stdout, keep diagnostics on stderr, and select fields
before parsing output in another program.