Skip to content
Skills Library
AI & agents · Tool integration

arize-toolkit-cli

/arize-toolkit-cli

Manage Arize platform resources using the arize_toolkit CLI. Use when users want to list, create, update, or delete Arize resources (models, monitors, prompts, evaluators, custom metrics, dashboards, spaces, organizations, users, or data imports) via the command line, configure CLI profiles, or perform platform administration tasks. Triggers on "list models", "create monitor", "arize_toolkit", "CLI", "arize cli", or any request to manage Arize platform resources from the terminal. Always use the "arize_toolkit" command, never "ax".

Licence
MIT
Last repository change
26.05.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
3
Deprecation

No signals detected. Repository changed on 26.05.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Manage Arize platform resources using the arize_toolkit CLI. Use when users want to list, create, update, or delete Arize resources (models, monitors, prompts, evaluators, custom metrics, dashboards, spaces, organizations, users, or data imports) via the command line, configure CLI profiles, or perform platform administration tasks. Triggers on "list models", "create monitor", "arize_toolkit", "CLI", "arize cli", or any request to manage Arize platform resources from the terminal. Always use the "arize_toolkit" command, never "ax".

Triggers from the description

list modelscreate monitorarize_toolkitCLIarize cli
Original author description

Manage Arize platform resources using the arize_toolkit CLI. Use when users want to list, create, update, or delete Arize resources (models, monitors, prompts, evaluators, custom metrics, dashboards, spaces, organizations, users, or data imports) via the command line, configure CLI profiles, or perform platform administration tasks. Triggers on "list models", "create monitor", "arize_toolkit", "CLI", "arize cli", or any request to manage Arize platform resources from the terminal. Always use the "arize_toolkit" command, never "ax".

How it works

  1. Workflow
  2. Step 1: Check Setup
  3. Step 2: Resolve Configuration
  4. Step 3: Run Commands
  5. Step 4: Summarize Output
  6. Common Workflows
  7. Tips
  8. Troubleshooting
  9. References
Original SKILL.md headings · 225 lines, 874 words
SKILL.md preview
---
name: arize-toolkit-cli
description: Manage Arize platform resources using the arize_toolkit CLI. Use when users want to list, create, update, or delete Arize resources (models, monitors, prompts, evaluators, custom metrics, dashboards, spaces, organizations, users, or data imports) via the command line, configure CLI profiles, or perform platform administration tasks. Triggers on "list models", "create monitor", "arize_toolkit", "CLI", "arize cli", or any request to manage Arize platform resources from the terminal. Always use the "arize_toolkit" command, never "ax".
---

# Arize Toolkit CLI

Manage Arize platform resources from the command line using `arize_toolkit`.

---

## Workflow

```
1. Check Setup → 2. Resolve Config → 3. Run Command → 4. Summarize Output
```

---

## Step 1: Check Setup

Verify the CLI is installed:

```bash
arize_toolkit --version
```

If not installed:

```bash
pip install arize_toolkit[cli]
```

---

## Step 2: Resolve Configuration

The CLI resolves configuration in this priority order:

1. **CLI flags**: `--api-key`, `--org`, `--space`, `--app-url`
1. **Environment variables**: `ARIZE_DEVELOPER_KEY`, `ARIZE_ORGANIZATION`, `ARIZE_SPACE`, `ARIZE_APP_URL`
1. **Config profile**: `~/.arize_toolkit/config.toml`

### Check if a profile exists

```bash
arize_toolkit config list
```

### If no profile, initialize one

Ask the user for their API key, organization name, and space name, then create the profile:

```bash
arize_toolkit config init --api-key "API_KEY" --org "ORG_NAME" --space "SPACE_NAME"
```

### First-time Arize setup

If the user doesn't have an Arize account yet, walk them through these steps:

1. **Create an account** — sign up at https://app.arize.com/auth/join
2. **Get an API key** — after logging in, navigate to **Settings → API Keys** in the Arize UI (see [API key docs](https://arize.com/docs/ax/security-and-settings/api-keys))
3. **Find organization and space names** — from the Arize landing page, use the upper-left dropdown to select an organization, then pick a space. These are the `--org` and `--space` values for the CLI.
4. **Initialize the CLI profile** with the values from steps 2-3:
   ```bash
   arize_toolkit config init --api-key "API_KEY" --org "ORG_NAME" --space "SPACE_NAME"
   ```
5. **For on-prem deployments** — add `--app-url` pointing to the base URL of the Arize instance:
   ```bash
   arize_toolkit config init --api-key "API_KEY" --org "ORG_NAME" --space "SPACE_NAME" --app-url "https://arize.your-company.com"
   ```

---

## Step 3: Run Commands

### Global Options (apply to all commands)

| Flag | Description |
|------|-------------|
| `--profile NAME` | Use a specific config profile |
| `--json` | Output as JSON instead of Rich tables |
| `--api-key KEY` | Override API key |
| `--org NAME` | Override organization |
| `--space NAME` | Override space |
| `--app-url URL` | Override app URL |

### Command Groups

| Group | Alias | Description |
|-------|-------|-------------|
| `config` | | Manage CLI configuration profiles |
| `spaces` | | Manage Arize spaces |
| `orgs` | | Manage organizations |
| `users` | | Manage users and space membership |
| `models` | `projects` | Manage models/projects |
| `monitors` | | Create and manage monitors |
| `prompts` | | Manage LLM prompt templates |
| `custom-metrics` | | Manage custom metrics |
| `evaluators` | | Manage LLM and code evaluators |
| `dashboards` | | Manage dashboards |
| `imports` | | Manage data import jobs (files/tables) |
| `traces` | | Query and inspect traces and spans |

See [references/COMMANDS.md](references/COMMANDS.md) for full command reference.

---

## Step 4: Summarize Output

- When `--json` is used, pipe through `jq` for filtering
- Present results clearly to the user
- For list commands, summarize count and key details
- For create/update/delete, confirm the action completed

---

## Common Workflows

### List all models in a space

```bash
arize_toolkit models list
```

### Get model performance metrics

```bash
arize_toolkit models performance accuracy production --model-name "my-model" --granularity day
```

### Create a performance monitor with email alerts

```bash
arize_toolkit monitors create-performance "My Monitor" \
  --model "my-model" \
  --environment production \
  --performance-metric accuracy \
  --threshold 0.9 \
  --operator lessThan \
  --email alerts@example.com
```

### Copy a monitor to another model

```bash
arize_toolkit monitors copy "My Monitor" --model "source-model" --new-model "target-model"
```

### Create a prompt template

```bash
arize_toolkit prompts create "my-prompt" \
  --messages '[{"role": "system", "content": "You are helpful."}, {"role": "user", "content": "{{query}}"}]' \
  --input-variable-format mustache
```

### Create a prompt from a file

```bash
arize_toolkit prompts create "my-prompt" --messages @prompt_messages.json
```

### List recent traces for a model

```bash
arize_toolkit traces list --model-name "my-agent"
```

### Get all spans for a trace

```bash
arize_toolkit traces get TRACE_ID --model-name "my-agent"
```

### Export trace spans to CSV with all attributes

```bash
arize_toolkit traces get TRACE_ID --model-name "my-agent" --csv spans.csv
```

### Export traces to CSV with filtered attributes

```bash
arize_toolkit traces list --model-name "my-agent" --csv traces.csv
arize_toolkit traces get TRACE_ID --model-id "ID" --columns "input.value,output.value" --csv spans.csv
```

### Export data as JSON for scripting

```bash
arize_toolkit --json models list | jq '.[].name'
```

### Use a different profile

```bash
arize_toolkit --profile staging monitors list --model-name "my-model"
```

---

## Tips

- Use `--json` flag for scripting and piping to `jq`
- Use `@filepath` syntax for complex JSON arguments (schema, messages, templates, code)
- `models` and `projects` are interchangeable aliases
- All destructive commands (delete) prompt for confirmation
- `spaces switch` and `spaces create` automatically persist the new space/org to your config profile, so subsequent commands use the new space
- Use `--help` on any command for full usage details: `arize_toolkit monitors create-performance --help`

---

## Troubleshooting

| Issue | Solution |
|-------|----------|
| `command not found` | Install with `pip install arize_toolkit[cli]` |
| Authentication error | Check API key: `arize_toolkit config show` |
| Wrong space/org | Use `--space` / `--org` flags or switch profile |
| Complex JSON args | Use `@file.json` syntax instead of inline JSON |

---

## References

- [references/COMMANDS.md](references/COMMANDS.md) - Full command reference with all options
Files in this package (2)
  • SKILL.md 7 KB
  • references/COMMANDS.md 9 KB

Versions

The database has no other skills named arize-toolkit-cli.

Database snapshot: 13.11.2026 · package version 34221ea374e6 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100arize-graphql-analytics
    Query and analyze data from the Arize platform using GraphQL, or help build/validate GraphQL queries and mutations. Use when users want to explore spaces, models, monitors, datasets, any Arize platform data, OR when they need help writing, formatting, or debugging GraphQL…
  • 100manage-gemini-tracing
    Set up and configure Arize tracing for Gemini CLI sessions. Use when users want to set up tracing, configure Arize AX or Phoenix for Gemini, enable/disable tracing, or troubleshoot tracing issues. Triggers on "set up gemini tracing", "configure Arize for Gemini", "configure…
  • 100manage-codex-tracing
    Set up and configure Arize tracing for OpenAI Codex CLI sessions. Use when users want to set up Codex tracing, configure Arize AX or Phoenix for Codex, enable/disable tracing, or troubleshoot Codex tracing issues. Triggers on "set up codex tracing", "configure Arize for Codex",…
  • 100arize-link
    Generates deep links to the Arize UI for projects, traces, spans, sessions, datasets, experiments, labeling queues, evaluators, and annotation configs. Discovers organization and project IDs with the ax CLI and produces clickable URLs for sharing Arize resources with team…
  • 100arize-admin
    Manages Arize users, organizations, spaces, projects, roles, role bindings, resource restrictions, and API keys via the ax CLI. Use for enterprise admin workflows: inviting and offboarding users, onboarding new teams, creating custom roles for SAML/SSO mappings, assigning roles…
  • 100arize-traces
    Retrieve and debug trace data from the Arize ML observability platform. Use when users want to list recent traces, look up a specific trace by trace ID, get all spans within a trace, analyze trace performance (latency, tokens, cost), or export trace data. Triggers on "list…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.