ApexDocsOpen Apex
Developer

Agent tools: SOS, brand, schema, and skills

Use Apex CLI agent-oriented commands for brand context, SOS handoffs, command schema introspection, and local skill installation.

These commands are designed for automation and external agent workflows. They expose public CLI behavior only; internal dashboards, internal API routes, and operations runbooks are not part of this reference.

Brand context

bash
apex brand
apex brand --json

apex brand reads the current shop brand context. Human output prints the prompt-ready brand block when one exists. JSON output returns brandContext, or null with a message when no profile exists yet.

Use this before generating customer-facing experiment copy so external agents inherit the same brand grounding as Apex-managed workflows.

SOS tickets

bash
apex sos create \
  --type qa \
  --experiment 00000000-0000-4000-8000-000000000040 \
  --sub-class "tracking evidence missing" \
  --loom https://www.loom.com/share/example \
  --description @sos-description.md
 
apex sos mine --json
CommandFlagsBehavior
apex sos create--type <type>, --loom <url>, --experiment <id>, --sub-class <text>, --description <text-or-@file>, optional [description] argumentCreates or reuses an Apex SOS ticket through the API.
apex sos mineNone beyond global flagsLists tickets created by the current API key.

SOS type values are full_handover, design, development, qa, config, and bug. The default type is qa.

Schema introspection

bash
apex schema --json

apex schema prints the current command tree, aliases, argument metadata, options, descriptions, default values, and nested commands. Agents should call this before scripting unfamiliar commands.

Skill files

bash
apex skills
apex skills --install
apex skills --install --target ./.claude/skills --json

apex skills prints the package paths for the CLI AGENTS.md contract and the bundled apex-cli skill. With --install, it copies both files into <target>/apex-cli. The default target is .claude/skills.

Agent contract reminders

  • Use apex, not inferred fuzzy command names.
  • Prefer --json and parse the envelope, not human tables.
  • Treat .apex/ folders as CLI-owned metadata.
  • Treat preview tokens and API keys as secrets.
  • Do not edit generated QA or launch state directly; use apex experiments qa.