arize-dataset

Creates, manages, and queries Arize datasets and examples. Covers dataset CRUD, appending examples, exporting data, and file-based dataset creation using the ax CLI. Use when the user needs test data, evaluation examples, or mentions create dataset, list datasets, export dataset, append examples, da

By github · 1,144 installs

npx skills add github/awesome-copilot --skill arize-dataset

Source repository · Upstream listing

Arize Dataset Skill SPACE — All space flags and the ARIZE SPACE env var accept a space name (e.g., my workspace ) or a base64 space ID (e.g., U3BhY2U6... ). Find yours with ax spaces list . 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, follow references/ax profiles.md to create/update it. If the user doesn't have their key, direct them to https://app.arize.com/admin API Keys Space unknown → run ax spaces list to pick by name, or ask the user Project unclear → ask the user, or run ax projects list o json limit 100 and present as selectable options Security: Never read .env files or search the filesystem for credentials. Use ax profiles for Arize credentials and ax ai integrations for LLM provider keys. If credentials are not available through these channels, ask the user. List Datasets: ax datasets list Browse datasets in a space. Output goes to stdout. Flags Flag Type Default Description space string from profile Filter by space limit, l int 15 Max results (1 100) cursor string none Pagination cursor from previous response o, output string table Output format: table, json, csv, parquet, or file path p, profile string default Configuration profile Get Dataset: ax datasets get Quick metadata lookup returns dataset name, space, timestamps, and version list. Flags Flag Type Default Description NAME OR ID string required Dataset name or ID (positional) space string none Space name or ID (required if using dataset name instead of ID) o, output string table Output format p, profile string default Configuration profile Response fields Field Type Description id string Dataset ID name string Dataset name space id string Space this dataset belongs to created at datetime When the dataset was created updated at datetime Last modification time versions array List of dataset versions (id, name, dataset id, created at, updated at) Export Dataset: ax datasets export Download all examples to a file. Use all for datasets larger than 500 examples (unlimited bulk export). Flags Flag Type Default Description NAME OR ID string required Dataset name or ID (positional) space string none Space name or ID (required if using dataset name instead of ID) version id string latest Export a specific dataset version all bool false Unlimited bulk export (use for datasets 500 examples) output dir string . Output directory stdout bool false Print JSON to stdout instead of file p, profile string default Configuration profile Agent auto escalation rule: If an export returns exactly 500 examples, the result is likely truncated — re run with all to get the full dataset. Export completeness verification: After exporting, confirm the row count matches what the server reports: Output is a JSON array of example objects. Each example has system fields ( id , created at , updated at ) plus all user defined fields: Create Dataset: ax datasets create Create a new dataset from a data file. Flags Flag Type Required Description name, n string yes Dataset name space string yes Space to create the dataset in file, f path yes Data file: CSV, JSON, JSONL, or Parquet o, output string no Output format for the returned dataset metadata p, profile string no Configuration profile Passing data via stdin Use file to pipe data directly — no temp file needed: To add rows to an existing dataset, use ax datasets append json '[...]' instead — no file needed. Supported file formats Format Extension Notes CSV .csv Column headers become field names JSON .json Array of objects JSON Lines .jsonl One object per line (NOT a JSON array) Parquet .parquet Column names become field names; preserves types Format gotchas: CSV : Loses type information — dates become strings, null becomes empty string. Use JSON/Parquet to preserve types. JSONL : Each line is a separate JSON object. A JSON array ( [{...}, {...}] ) in a .jsonl file will fail — use .json extension instead. Parquet : Preserves column types. Requires pandas / pyarrow to read locally: pd.read parquet("examples.parquet") . Append Examples: ax datasets append Add examples to an existing dataset. Two input modes use whichever fits. Inline JSON (agent friendly) Generate the payload directly no temp files needed: From a file To a specific version Flags Flag Type Required Description NAME OR ID string yes Dataset name or ID (positional); add space when using name space string no Space name or ID (required if using dataset name instead of ID) json string mutex JSON array of example objects file, f path mutex Data file (CSV, JSON, JSONL, Parquet) version id string no Append to a specific version (default: latest) o, output string no Output format for the returned dataset metadata p, profile string no Configuration profile Exactly one of json or file is required. Validation Each example must be a JSON object with at least one user defined field Maximum 100,000 examples per request Schema validation before append: If the dataset already has examples, inspect its schema before appending to avoid silent field mismatches: Fields are free form: extra fields in new examples are added, and missing fields become null. However, typos in field names (e.g., queston vs question ) create new columns silently verify spelling before appending. Delete Dataset: ax datasets delete Flags Flag Type Default Description NAME OR ID string required Dataset name or ID (positional) space string none Space name or ID (required if using dataset name instead of ID) force, f bool false Skip confirmation prompt p, profile string default Configuration profile Workflows Find a dataset by name All dataset commands accept a name or ID directly. You can pass a dataset name as the positional argument (add space SPACE when not using an ID): Create a dataset from file for evaluation 1. Prepare a CSV/JSON/Parquet file with your evaluation columns (e.g., input , expected output ) If generating data inline, pipe it via stdin using file (see the Create Dataset section) 2. ax datasets create name "eval set v1" space SPACE file eval data.csv 3. Verify: ax datasets get DATASET NAME space SPACE 4. Use the dataset name to run experiments Add examples to an existing dataset Download dataset for offline analysis 1. ax datasets list space SPACE find the dataset name 2. ax datasets export DATASET NAME space SPACE download to file 3. Parse the JSON: jq '.[] .question' dataset /examples.json Export a specific version Iterate on a dataset 1. Export current version: ax datasets export DATASET NAME space SPACE 2. Modify the examples locally 3. Append new rows: ax datasets append DATASET NAME space SPACE file new rows.csv 4. Or create a fresh version: ax datasets create name "eval set v2" space SPACE file updated data.json Pipe export to other tools Dataset Example Schema Examples are free form JSON objects. There is no fixed schema columns are whatever fields you provide. System managed fields are added by the server: Field Type Managed by Notes id string server Auto generated UUID. Required on update, forbidden on create/append created at datetime server Immutable creation timestamp updated at datetime server Auto updated on modification (any user field) any JSON type user String, number, boolean, null, nested object, array Related Skills arize trace : Export production spans to understand what data to put in datasets → use arize trace arize experiment : Run evaluations against this dataset → next step is arize experiment arize prompt optimization : Use dataset + experiment results to improve prompts → use arize prompt optimization Troubleshooting Problem Solution ax: command not found See references/ax setup.md 401 Unauthorized API key is wrong, expired, or doesn't have access to this space. Fix the profile using references/ax profiles.md. No profile found No profile is configured. See references/ax profiles.md to create one. Dataset not found Verify dataset ID with ax datasets list File format error Supported: CSV, JSON, JSONL, Parquet. Use file to read from stdin. platform managed column Remove id , created at , updated at from create/append payloads reserved column Remove time , count , or any source record field Provide either json or file Append requires exactly one input source Examples array is empty Ensure your JSON array or file contains at least one example not a JSON object Each element in the json array must be a {...} object, not a string or number Save Credentials for Future Use See references/ax profiles.md § Save Credentials for Future Use.