Official agent skill

Arize Experiment

by github in github/awesome-copilot

Creates, runs, and analyzes Arize experiments for evaluating and comparing model performance.

OfficialMITAuto-check: notesMarketing & SEO

Install Arize Experiment

skills CLI
$ npx skills add github/awesome-copilot --skill arize-experiment -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install github/awesome-copilot arize-experiment --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/arize-experiment .claude/skills/arize-experiment && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
arize-experiment
GitHub stars
40k
Used in
1 other repo
Token cost
~4.6k tokens
SKILL.md length
1,366 words
Files
3 (incl. references)
Skills in repo
417
Repo updated
First seen
Licence
MIT

At a glance

Creates, runs, and analyzes Arize experiments for evaluating and comparing model performance.

  • Works in 6 steps: Find or create a dataset → Export the dataset examples → Call the real model API for each example… → …
  • The user mentions create experiment
  • SKILL.md covers Concepts, Prerequisites, List Experiments: ax… and Get Experiment: ax experiments…, plus 8 more sections
  • Calls jq, python3 and pip; needs CUSTOM_API_KEY and CURSOR_TOKEN

What it does

Arize Experiment is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. Creates, runs, and analyzes Arize experiments for evaluating and comparing model performance. Covers experiment CRUD, exporting runs, comparing results, and evaluation workflows using the ax CLI. Use when the user mentions create experiment, run experiment, compare models, model performance, evaluate AI, experiment results, benchmark, A/B test models, or measure accuracy.

Its SKILL.md is about 4.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/ax-profiles.md` and `references/ax-setup.md`). Compatibility notes: Requires the ax CLI and a configured Arize profile.

It sits in Marketing & SEO, covering A/B testing. The repository describes itself as: Community-contributed instructions, agents, skills, and configurations to help you make the most of GitHub Copilot. The licence is MIT.

When your agent uses it

  • The user mentions create experiment
  • Model performance
  • Experiment results
  • A/B test models

Example prompts

  • “/arize-experiment”

Requirements

  • Python 3
  • A credential in CURSOR_TOKEN
  • A credential in OPENAI_API_KEY
  • Compatibility (from SKILL.md): Requires the ax CLI and a configured Arize profile.

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Find or create a dataset
  2. Export the dataset examples
  3. Call the real model API for each example and collect outputs. Use ax datasets export --stdout to pipe examples directly into an inference…
  4. Verify the runs file
  5. Create the experiment
  6. Verify: ax experiments get "gpt-4o-baseline" --dataset DATASET_NAME --space SPACE

What it can do on your machine

Read from SKILL.md and the folder at commit 727ff2e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • jq
    • python3
    • pip

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use pip, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • CUSTOM_API_KEY
    • CURSOR_TOKEN
    • OPENAI_API_KEY
    • ANTHROPIC_API_KEY
    • GOOGLE_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Requires the ax CLI and a configured Arize profile.

    From compatibility in the SKILL.md frontmatter.

Context cost

Arize Experiment loads about 4.6k tokens when it runs, and up to ~6.2k if it reads all its reference files. Until then it costs about 98 tokens; SKILL.md has 1,366 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~98
When it runs · the whole SKILL.md, loaded when a task matches
~4.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:32
    - **Security:** Never read `.env` files or search the filesystem for credentials. Use `ax profiles` for Arize credential

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from github/awesome-copilot at commit 727ff2e, republished under its MIT licence (© github). 1,366 words, ~4,646 tokens.

Download SKILL.mdSave it as .claude/skills/arize-experiment/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
arize-experiment
description
Creates, runs, and analyzes Arize experiments for evaluating and comparing model performance. Covers experiment CRUD, exporting runs, comparing results, and evaluation workflows using the ax CLI. Use when the user mentions create experiment, run experiment, compare models, model performance, evaluate AI, experiment results, benchmark, A/B test models, or measure accuracy.
compatibility
Requires the ax CLI and a configured Arize profile.
metadata.author
arize
metadata.version
1.0

Arize Experiment 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

  • Experiment = a named evaluation run against a specific dataset version, containing one run per example
  • Experiment Run = the result of processing one dataset example -- includes the model output, optional evaluations, and optional metadata
  • Dataset = a versioned collection of examples; every experiment is tied to a dataset and a specific dataset version
  • Evaluation = a named metric attached to a run (e.g., correctness, relevance), with optional label, score, and explanation

The typical flow: export a dataset → process each example → collect outputs and evaluations → create an experiment with the runs.

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.
  • CRITICAL — Never fabricate outputs: When running an experiment, you MUST call the real model API specified by the user for every dataset example. Never fabricate, simulate, or hardcode model outputs, latencies, or evaluation scores. If you cannot call the API (missing SDK, missing credentials, network error), stop and tell the user what is needed before proceeding.

List Experiments: ax experiments list

Browse experiments, optionally filtered by dataset. Output goes to stdout.

bash
ax experiments list
ax experiments list --dataset DATASET_NAME --space SPACE --limit 20   # DATASET_NAME: name or ID (name preferred)
ax experiments list --cursor CURSOR_TOKEN
ax experiments list -o json
Flags
FlagTypeDefaultDescription
--datasetstringnoneFilter by dataset
--limit, -lint15Max results (1-100)
--cursorstringnonePagination cursor from previous response
-o, --outputstringtableOutput format: table, json, csv, parquet, or file path
-p, --profilestringdefaultConfiguration profile

Get Experiment: ax experiments get

Quick metadata lookup -- returns experiment name, linked dataset/version, and timestamps.

bash
ax experiments get NAME_OR_ID
ax experiments get NAME_OR_ID -o json
ax experiments get NAME_OR_ID --dataset DATASET_NAME --space SPACE   # required when using experiment name instead of ID
Flags
FlagTypeDefaultDescription
NAME_OR_IDstringrequiredExperiment name or ID (positional)
--datasetstringnoneDataset name or ID (required if using experiment name instead of ID)
--spacestringnoneSpace name or ID (required if using dataset name instead of ID)
-o, --outputstringtableOutput format
-p, --profilestringdefaultConfiguration profile
Response fields
FieldTypeDescription
idstringExperiment ID
namestringExperiment name
dataset_idstringLinked dataset ID
dataset_version_idstringSpecific dataset version used
experiment_traces_project_idstringProject where experiment traces are stored
created_atdatetimeWhen the experiment was created
updated_atdatetimeLast modification time

Export Experiment: ax experiments export

Download all runs to a file. By default uses the REST API; pass --all to use Arrow Flight for bulk transfer.

bash
# EXPERIMENT_NAME, DATASET_NAME: name or ID (name preferred)
ax experiments export EXPERIMENT_NAME --dataset DATASET_NAME --space SPACE
# -> experiment_abc123_20260305_141500/runs.json

ax experiments export EXPERIMENT_NAME --dataset DATASET_NAME --space SPACE --all
ax experiments export EXPERIMENT_NAME --dataset DATASET_NAME --space SPACE --output-dir ./results
ax experiments export EXPERIMENT_NAME --dataset DATASET_NAME --space SPACE --stdout
ax experiments export EXPERIMENT_NAME --dataset DATASET_NAME --space SPACE --stdout | jq '.[0]'
Flags
FlagTypeDefaultDescription
NAME_OR_IDstringrequiredExperiment name or ID (positional)
--datasetstringnoneDataset name or ID (required if using experiment name instead of ID)
--spacestringnoneSpace name or ID (required if using dataset name instead of ID)
--allboolfalseUse Arrow Flight for bulk export (see below)
--output-dirstring.Output directory
--stdoutboolfalsePrint JSON to stdout instead of file
-p, --profilestringdefaultConfiguration profile
REST vs Flight (--all)
  • REST (default): Lower friction -- no Arrow/Flight dependency, standard HTTPS ports, works through any corporate proxy or firewall. Limited to 500 runs per page.
  • Flight (--all): Required for experiments with more than 500 runs. Uses gRPC+TLS on a separate host/port (flight.arize.com:443) which some corporate networks may block.

Agent auto-escalation rule: If a REST export returns exactly 500 runs, the result is likely truncated. Re-run with --all to get the full dataset.

Output is a JSON array of run objects:

json
[
  {
    "id": "run_001",
    "example_id": "ex_001",
    "output": "The answer is 4.",
    "evaluations": {
      "correctness": { "label": "correct", "score": 1.0 },
      "relevance": { "score": 0.95, "explanation": "Directly answers the question" }
    },
    "metadata": { "model": "gpt-4o", "latency_ms": 1234 }
  }
]

Create Experiment: ax experiments create

Create a new experiment with runs from a data file.

bash
ax experiments create --name "gpt-4o-baseline" --dataset DATASET_NAME --space SPACE --file runs.json
ax experiments create --name "claude-test" --dataset DATASET_NAME --space SPACE --file runs.csv
Flags
FlagTypeRequiredDescription
--name, -nstringyesExperiment name
--datasetstringyesDataset to run the experiment against
--space, -sstringnoSpace name or ID (required if using dataset name instead of ID)
--file, -fpathyesData file with runs: CSV, JSON, JSONL, or Parquet
-o, --outputstringnoOutput format
-p, --profilestringnoConfiguration profile
Passing data via stdin

Use --file - to pipe data directly — no temp file needed:

bash
echo '[{"example_id": "ex_001", "output": "Paris"}]' | ax experiments create --name "my-experiment" --dataset DATASET_NAME --space SPACE --file -

# Or with a heredoc
ax experiments create --name "my-experiment" --dataset DATASET_NAME --space SPACE --file - << 'EOF'
[{"example_id": "ex_001", "output": "Paris"}]
EOF
Required columns in the runs file
ColumnTypeRequiredDescription
example_idstringyesID of the dataset example this run corresponds to
outputstringyesThe model/system output for this example

Additional columns are passed through as additionalProperties on the run.

Delete Experiment: ax experiments delete

bash
ax experiments delete NAME_OR_ID
ax experiments delete NAME_OR_ID --dataset DATASET_NAME --space SPACE   # required when using experiment name instead of ID
ax experiments delete NAME_OR_ID --force   # skip confirmation prompt
Flags
FlagTypeDefaultDescription
NAME_OR_IDstringrequiredExperiment name or ID (positional)
--datasetstringnoneDataset name or ID (required if using experiment name instead of ID)
--spacestringnoneSpace name or ID (required if using dataset name instead of ID)
--force, -fboolfalseSkip confirmation prompt
-p, --profilestringdefaultConfiguration profile

Experiment Run Schema

Each run corresponds to one dataset example:

json
{
  "example_id": "required -- links to dataset example",
  "output": "required -- the model/system output for this example",
  "evaluations": {
    "metric_name": {
      "label": "optional string label (e.g., 'correct', 'incorrect')",
      "score": "optional numeric score (e.g., 0.95)",
      "explanation": "optional freeform text"
    }
  },
  "metadata": {
    "model": "gpt-4o",
    "temperature": 0.7,
    "latency_ms": 1234
  }
}
Evaluation fields
FieldTypeRequiredDescription
labelstringnoCategorical classification (e.g., correct, incorrect, partial)
scorenumbernoNumeric quality score (e.g., 0.0 - 1.0)
explanationstringnoFreeform reasoning for the evaluation

At least one of label, score, or explanation should be present per evaluation.

Workflows

Show full SKILL.md (782 more words)Show less
Run an experiment against a dataset
  1. Find or create a dataset:

    bash
    ax datasets list --space SPACE
    ax datasets export DATASET_NAME --space SPACE --stdout | jq 'length'
  2. Export the dataset examples:

    bash
    ax datasets export DATASET_NAME --space SPACE
  3. Call the real model API for each example and collect outputs. Use ax datasets export --stdout to pipe examples directly into an inference script:

    bash
    ax datasets export DATASET_NAME --space SPACE --stdout | python3 infer.py > runs.json

    Write infer.py to read examples from stdin, call the target model, and write runs JSON to stdout. The script below is a template — first inspect the exported dataset JSON to find the correct input field name, then uncomment the provider block the user wants:

    python
    import json, sys, time
    
    examples = json.load(sys.stdin)
    runs = []
    
    for ex in examples:
        # Inspect the exported JSON to find the right field (e.g. "input", "question", "prompt")
        user_input = ex.get("input") or ex.get("question") or ex.get("prompt") or str(ex)
    
        start = time.time()
    
        # === CALL THE REAL MODEL API HERE — never fabricate or simulate ===
        # Uncomment and adapt the provider block the user requested:
        #
        # OpenAI (pip install openai  — uses OPENAI_API_KEY env var):
        #   from openai import OpenAI
        #   resp = OpenAI().chat.completions.create(
        #       model="gpt-4o",
        #       messages=[{"role": "user", "content": user_input}]
        #   )
        #   output_text = resp.choices[0].message.content
        #
        # Anthropic (pip install anthropic  — uses ANTHROPIC_API_KEY env var):
        #   import anthropic
        #   resp = anthropic.Anthropic().messages.create(
        #       model="claude-sonnet-4-6", max_tokens=1024,
        #       messages=[{"role": "user", "content": user_input}]
        #   )
        #   output_text = resp.content[0].text
        #
        # Google Gemini (pip install google-genai  — uses GOOGLE_API_KEY env var):
        #   from google import genai
        #   resp = genai.Client().models.generate_content(
        #       model="gemini-2.5-pro", contents=user_input
        #   )
        #   output_text = resp.text
        #
        # Custom / OpenAI-compatible proxy (pip install openai — uses CUSTOM_BASE_URL + CUSTOM_API_KEY env vars):
        # Use this for Azure OpenAI, NVIDIA NIM, local Ollama, or any OpenAI-compatible endpoint,
        # including a test integration proxy. Matches the `custom` provider in `ax ai-integrations create`.
        #   import os
        #   from openai import OpenAI
        #   resp = OpenAI(
        #       base_url=os.environ["CUSTOM_BASE_URL"],          # e.g. https://my-proxy.example.com/v1
        #       api_key=os.environ.get("CUSTOM_API_KEY", "none"),
        #   ).chat.completions.create(
        #       model=os.environ.get("CUSTOM_MODEL", "default"),
        #       messages=[{"role": "user", "content": user_input}]
        #   )
        #   output_text = resp.choices[0].message.content
    
        latency_ms = round((time.time() - start) * 1000)
        runs.append({
            "example_id": ex["id"],
            "output": output_text,
            "metadata": {"model": "MODEL_NAME", "latency_ms": latency_ms}
        })
        print(f"  {ex['id']}: {latency_ms}ms", file=sys.stderr)
    
    json.dump(runs, sys.stdout, indent=2)

    Before running: install the provider SDK (pip install openai / anthropic / google-genai) and ensure the API key is set as an environment variable in your shell. If you cannot access the API, stop and tell the user what is needed.

  4. Verify the runs file:

    bash
    python3 -c "import json; runs=json.load(open('runs.json')); print(f'{len(runs)} runs'); print(json.dumps(runs[0], indent=2))"

    Each run must have example_id and output. Optional fields: evaluations, metadata.

  5. Create the experiment:

    bash
    ax experiments create --name "gpt-4o-baseline" --dataset DATASET_NAME --space SPACE --file runs.json
  6. Verify: ax experiments get "gpt-4o-baseline" --dataset DATASET_NAME --space SPACE

Compare two experiments
  1. Export both experiments:
    bash
    ax experiments export "experiment-a" --dataset DATASET_NAME --space SPACE --stdout > a.json
    ax experiments export "experiment-b" --dataset DATASET_NAME --space SPACE --stdout > b.json
  2. Compare evaluation scores by example_id:
    bash
    # Average correctness score for experiment A
    jq '[.[] | .evaluations.correctness.score] | add / length' a.json
    
    # Same for experiment B
    jq '[.[] | .evaluations.correctness.score] | add / length' b.json
  3. Find examples where results differ:
    bash
    jq -s '.[0] as $a | .[1][] | . as $run |
      {
        example_id: $run.example_id,
        b_score: $run.evaluations.correctness.score,
        a_score: ($a[] | select(.example_id == $run.example_id) | .evaluations.correctness.score)
      }' a.json b.json
  4. Score distribution per evaluator (pass/fail/partial counts):
    bash
    # Count by label for experiment A
    jq '[.[] | .evaluations.correctness.label] | group_by(.) | map({label: .[0], count: length})' a.json
  5. Find regressions (examples that passed in A but fail in B):
    bash
    jq -s '
      [.[0][] | select(.evaluations.correctness.label == "correct")] as $passed_a |
      [.[1][] | select(.evaluations.correctness.label != "correct") |
        select(.example_id as $id | $passed_a | any(.example_id == $id))
      ]
    ' a.json b.json

Statistical significance note: Score comparisons are most reliable with ≥ 30 examples per evaluator. With fewer examples, treat the delta as directional only — a 5% difference on n=10 may be noise. Report sample size alongside scores: jq 'length' a.json.

Download experiment results for analysis
  1. ax experiments list --dataset DATASET_NAME --space SPACE -- find experiments
  2. ax experiments export EXPERIMENT_NAME --dataset DATASET_NAME --space SPACE -- download to file
  3. Parse: jq '.[] | {example_id, score: .evaluations.correctness.score}' experiment_*/runs.json
Pipe export to other tools
bash
# Count runs
ax experiments export EXPERIMENT_NAME --dataset DATASET_NAME --space SPACE --stdout | jq 'length'

# Extract all outputs
ax experiments export EXPERIMENT_NAME --dataset DATASET_NAME --space SPACE --stdout | jq '.[].output'

# Get runs with low scores
ax experiments export EXPERIMENT_NAME --dataset DATASET_NAME --space SPACE --stdout | jq '[.[] | select(.evaluations.correctness.score < 0.5)]'

# Convert to CSV
ax experiments export EXPERIMENT_NAME --dataset DATASET_NAME --space SPACE --stdout | jq -r '.[] | [.example_id, .output, .evaluations.correctness.score] | @csv'
  • arize-dataset: Create or export the dataset this experiment runs against → use arize-dataset first
  • arize-prompt-optimization: Use experiment results to improve prompts → next step is arize-prompt-optimization
  • arize-trace: Inspect individual span traces for failing experiment runs → use arize-trace
  • arize-link: Generate clickable UI links to traces from experiment runs → use arize-link

Troubleshooting

ProblemSolution
ax: command not foundSee references/ax-setup.md
401 UnauthorizedAPI key is wrong, expired, or doesn't have access to this space. Fix the profile using references/ax-profiles.md.
No profile foundNo profile is configured. See references/ax-profiles.md to create one.
Experiment not foundVerify experiment name with ax experiments list --space SPACE
Invalid runs fileEach run must have example_id and output fields
example_id mismatchEnsure example_id values match IDs from the dataset (export dataset to verify)
No runs foundExport returned empty -- verify experiment has runs via ax experiments get
Dataset not foundThe linked dataset may have been deleted; check with ax datasets list

Save Credentials for Future Use

See references/ax-profiles.md § Save Credentials for Future Use.

© github, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in skills/arize-experiment of github/awesome-copilot.

  • SKILL.md
  • references/ax-profiles.md
  • references/ax-setup.md

Open the folder on GitHubat commit 727ff2e

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in github/awesome-copilot, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Arize Experiment next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Arize Experiment compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Arize Experiment this skillgithub/awesome-copilot40k1 repos~4.6kAutomated safety check: NotesMIT
AnalyticsNexus-JPF/note-companion8696 repos~2.2kAutomated safety check: PassMIT
Ab Test Setupfreekmurze/dotfiles1k15 repos~1.8kAutomated safety check: PassNone
Ad Test Designeraaron-he-zhu/aaron-marketing-skills2.9k2 repos~2.8kAutomated safety check: PassApache-2.0
Ab TestingCesarjoquin/Marketing-Skills1992 repos~2.8kAutomated safety check: PassMIT
Meta Tags Optimizernowork-studio/notfair-plugin3.9k1 repos~2.7kAutomated safety check: PassMIT

Similar skills

  • Analytics

    Nexus-JPF/note-companion

    When the user wants to set up, improve, or audit analytics tracking and measurement.

    869 GitHub starsUsed in 6 repos~2.2k tokens
    Marketing & SEOAuto-check passed
  • Ab Test Setup

    freekmurze/dotfiles

    When the user wants to plan, design, or implement an A/B test or experiment.

    1k GitHub starsUsed in 15 repos~1.8k tokens
    Marketing & SEOAuto-check passed
  • Ad Test Designer

    aaron-he-zhu/aaron-marketing-skills

    A skill your agent uses when the user asks to "design an A/B test", "set up a creative/landing test", "run an incrementality test", or "is this result statistically and practically material?"…

    2.9k GitHub starsUsed in 2 repos~2.8k tokens
    Marketing & SEOAuto-check passed
  • Ab Testing

    Cesarjoquin/Marketing-Skills

    When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program.

    199 GitHub starsUsed in 2 repos~2.8k tokens
    Marketing & SEOAuto-check passed
  • Meta Tags Optimizer

    nowork-studio/notfair-plugin

    Writes and improves title tags, meta descriptions, Open Graph and Twitter card tags for click-through, with character counts and A/B test variants.

    3.9k GitHub starsUsed in 1 repo~2.7k tokens
    Marketing & SEOAuto-check passed
  • Ab Test Analyzer

    irinabuht12-oss/marketing-skills

    Statistical significance calculator for A/B test results with sample size requirements, segment breakdowns, and hypothesis generation.

    3.8k GitHub stars~1.4k tokensUpdated 13 days ago
    Marketing & SEOAuto-check passed

More from github/awesome-copilot

All 417 skills in this repo
  • Acquire Codebase Knowledge

    github/awesome-copilot

    Official

    Maps an unfamiliar codebase into seven evidence-backed documents in docs/codebase/, using a scan script and templates, for onboarding or architecture write-ups.

    40k GitHub starsUsed in 1 repo~2.3k tokens
    Auto-check passed
  • Azure Architecture Autopilot

    github/awesome-copilot

    Official

    Designs Azure infrastructure from a natural-language description, or diagrams an existing resource group, then refines the design through conversation and deploys it with Bicep.

    40k GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed
  • Draw.io Diagram Generator

    github/awesome-copilot

    Official

    Generates, edits and validates draw.io files with correct mxGraph XML, covering flowcharts, architecture, sequence, ER and UML class diagrams.

    40k GitHub starsUsed in 1 repo~4.9k tokens
    Auto-check passed
  • Credit Risk Data Cleaning

    github/awesome-copilot

    Official

    Cleans raw credit data and screens variables before loan modeling, dropping unstable, noisy or redundant features and writing an Excel report of every step.

    40k GitHub starsUsed in 1 repo~1.5k tokens
    Auto-check passed
  • Daily Focus Board

    github/awesome-copilot

    Official

    Builds a warm, browser-based daily focus board the user updates by talking to their agent, with Eisenhower priorities, a brain-dump box and kind not-today carryover.

    40k GitHub stars~3k tokensUpdated today
    Auto-check passed
  • Python Pypi Package Builder

    github/awesome-copilot

    Official

    End-to-end skill for building, testing, linting, versioning, and publishing a production-grade Python library to PyPI.

    40k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Categories

Questions about Arize Experiment

What does Arize Experiment do?

Creates, runs, and analyzes Arize experiments for evaluating and comparing model performance. Arize Experiment is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. Creates, runs, and analyzes Arize experiments for evaluating and comparing model performance.

When should I use Arize Experiment?

Arize Experiment fits situations like: the user mentions create experiment; model performance; experiment results; A/B test models.

How do I install Arize Experiment in Claude Code?

Run `npx skills add github/awesome-copilot --skill arize-experiment -a claude-code`. Or copy the skill folder (skills/arize-experiment in github/awesome-copilot) into .claude/skills/arize-experiment in your project. Claude Code loads it when a task matches its description.

How do I install Arize Experiment in Codex?

Run `npx skills add github/awesome-copilot --skill arize-experiment -a codex`. Or copy the skill folder (skills/arize-experiment in github/awesome-copilot) into .agents/skills/arize-experiment in your project. Codex loads it when a task matches its description.

Can I use Arize Experiment in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add github/awesome-copilot --skill arize-experiment -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/arize-experiment, .gemini/skills/arize-experiment, .github/skills/arize-experiment and .opencode/skills/arize-experiment in your project.

What does Arize Experiment need to run?

Going by SKILL.md and its folder, Arize Experiment needs the command-line tools its instructions call (jq, python3 and pip) and credentials named CUSTOM_API_KEY, CURSOR_TOKEN, OPENAI_API_KEY and ANTHROPIC_API_KEY. Our summary lists: Python 3; A credential in CURSOR_TOKEN; A credential in OPENAI_API_KEY. Compatibility (from SKILL.md): Requires the ax CLI and a configured Arize profile..

Does Arize Experiment access the network?

SKILL.md contains no URLs. Its commands use pip, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Arize Experiment safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Arize Experiment use?

Arize Experiment is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Arize Experiment use?

About 4.6k tokens (SKILL.md is roughly 19k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.5k tokens, read only when the agent opens those files.

What are the alternatives to Arize Experiment?

Skills that share tags, products or a category with Arize Experiment: Analytics (Nexus-JPF/note-companion, 869 stars), Ab Test Setup (freekmurze/dotfiles, 1k stars), Ad Test Designer (aaron-he-zhu/aaron-marketing-skills, 2.9k stars) and Ab Testing (Cesarjoquin/Marketing-Skills, 199 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Arize Experiment?

github (a GitHub organization, an official publisher) maintains it in github/awesome-copilot, which has 39,748 GitHub stars. The repository holds 417 skills in this directory. The repository was last updated on October 7, 2026.

Source: github/awesome-copilot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.