arize-dataset

# Arize Dataset Skill ## Concepts - **Dataset** = a versioned collection of examples used for evaluation and experimentation - **Dataset Version** = a snapshot of a dataset at a point in time; updates can be in-place or create a new version - **Example** = a single record in a dataset with arbitrary user-defined fields (e.g., `question`, `answer`, `context`) - **Space** = an organizational container; datasets belong to a space System-managed fields on examples (`id`, `created_at`, `updated_at`) are auto-generated by the server -- never include them in create or append payloads. ## Prerequisites Proceed directly with the task — run the `ax` command you need. Do NOT check versions, env vars, or profiles upfront. If an `ax` command fails, troubleshoot based on the error: - `command not found` or version error → see references/ax-setup.md - `401 Unauthorized` / missing API key → run `ax profiles show` to inspect the current profile. If the profile is missing or the API key is wrong: check `.env` for `ARIZE_API_KEY` and use it to create/update the profile via references/ax-profiles.md. If `.env` has no key either, ask the user for their Arize API key (https://app.arize.com/admin > API Keys) - Space ID unknown → check `.env` for `ARIZE_SPACE_ID`, or run `ax spaces list -o json`, or ask the user - Project unclear → check `.env` for `ARIZE_DEFAULT_PROJECT`, or ask, or run `ax projects list -o json --limit 100` and present as selectable options ## List Datasets: `ax datasets li...