Gerencia fluxos de trabalho de avaliação LLM-as-judge no Arize, incluindo a criação de avaliadores, execução de tarefas em spans ou experimentos e monitoramento contínuo.
- Estrelas no GitHub
- 41.038
- Arquivos
- 3
- Último commit
- 11 de nov. de 2026
- Licença
- MIT
- Ferramentas permitidas
- —
O que a skill arize-evaluator faz?
arize-evaluator é uma Agent Skill. Gerencia fluxos de trabalho de avaliação LLM-as-judge no Arize, incluindo a criação de avaliadores, execução de tarefas em spans ou experimentos e monitoramento contínuo.
Resumo gerado a partir do SKILL.md da skill.
Sobre a skill arize-evaluator
Gerenciar fluxos de trabalho de avaliação LLM-as-judge no Arize é o que esta SKILL permite para desenvolvedores que constroem aplicações de IA. Ela permite que os usuários projetem, criem e executem evaluators que utilizam modelos como gpt-4o ou claude-sonnet-4-5 para pontuar dados quanto a qualidades como alucinação, fidelidade e relevância. Ao definir um evaluator com um template de prompt específico e opções de classificação, você pode automatizar a avaliação das saídas do modelo.
Um agente pode usar esta SKILL para executar tasks contra traces de projetos ao vivo ou datasets de experimentos específicos. Ela suporta diferentes níveis de granularidade de dados, incluindo os níveis de span, trace e session, permitindo desde a correção de um Q&A individual até a análise de qualidade de conversas de múltiplos turnos. A SKILL depende da CLI ax e requer um perfil do Arize configurado e integrações de IA para as credenciais do provedor de LLM. Ela produz resultados de avaliação estruturados, incluindo labels, pontuações numéricas e explicações opcionais, que podem ser usados para o monitoramento contínuo de modelos em produção.
O que um agente pode fazer com ela
- 1Iterar em prompts de judgeDesenvolver e versionar novos prompts de evaluator para melhorar a qualidade do LLM judge.
Escrito a partir do SKILL.md da skill. Cada caso de uso é verificado com uma citação dele.
Como instalar a skill arize-evaluator
Cada comando copia a pasta da skill para o diretório de skills do cliente. Reinicie o cliente ou inicie uma nova sessão para carregá-la.Instalar a skill arize-evaluator no Claude Code
~/.claude/skills/arize-evaluator/SKILL.md
$ npx degit github/awesome-copilot/skills/arize-evaluator ~/.claude/skills/arize-evaluatorInstalar a skill arize-evaluator no Claude Code (project)
.claude/skills/arize-evaluator/SKILL.md
$ npx degit github/awesome-copilot/skills/arize-evaluator .claude/skills/arize-evaluatorInstalar a skill arize-evaluator no Codex
~/.agents/skills/arize-evaluator/SKILL.md
$ npx degit github/awesome-copilot/skills/arize-evaluator ~/.agents/skills/arize-evaluatorInstalar a skill arize-evaluator no Gemini CLI
~/.gemini/skills/arize-evaluator/SKILL.md
$ npx degit github/awesome-copilot/skills/arize-evaluator ~/.gemini/skills/arize-evaluatorInstalar a skill arize-evaluator no Claude.ai
npx degit github/awesome-copilot/skills/arize-evaluator arize-evaluator && zip -r arize-evaluator.zip arize-evaluator # claude.ai → Customize → Skills → + → Create skill → Upload a skill → arize-evaluator.zip
Verificações automatizadas
Executado em 15 de nov. de 2026Relatório completo →Passou nas nossas verificações automáticas. Não é uma auditoria de segurança: leia os scripts antes de deixar um agente executá-los. Como as verificações funcionam · O que corrigir para ganhar mais pontos
- Repositório de origem vinculado e acessívelgithub/awesome-copilot/skills/arize-evaluator is public and reachablegithub.com/github/awesome-copilot/tree/HEAD/skills/arize-eva ↗Passou
- Licença de código aberto (OSI)MITspdx.org/licenses/MIT.html ↗Passou
- Commit ou release no último anoLast commit 2026-11-11github.com/github/awesome-copilot/commits ↗Passou
- Sem baixar e executar nem roubo de credenciais nos scriptsNo scripts in the skill folderPassou
- Sem instruções ocultas no SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/github/awesome-copilot/blob/HEAD/skills/arize-eva ↗Passou
- Ferramentas pré-aprovadas são restritasNo pre-approved tools; the agent asks before using onegithub.com/github/awesome-copilot/blob/HEAD/skills/arize-eva ↗Passou
- O SKILL.md segue o formato Agent SkillsSKILL.md is 674 lines; the spec suggests under 500github.com/github/awesome-copilot/blob/HEAD/skills/arize-eva ↗Problema encontrado
SKILL.md
Ver no GitHubArize Evaluator Skill
SPACE— All--spaceflags and theARIZE_SPACEenv var accept a space name (e.g.,my-workspace) or a base64 space ID (e.g.,U3BhY2U6...). Find yours withax spaces list.
This skill covers designing, creating, and running LLM-as-judge evaluators on Arize. An evaluator defines the judge; a task is how you run it against real data.
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 foundor version error → see references/ax-setup.md401 Unauthorized/ missing API key → runax profiles showto 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 listto pick by name, or ask the user - LLM provider call fails (missing OPENAI_API_KEY / ANTHROPIC_API_KEY) → run
ax ai-integrations list --space SPACEto check for platform-managed credentials. If none exist, ask the user to provide the key or create an integration via the arize-ai-provider-integration skill - Security: Never read
.envfiles or search the filesystem for credentials. Useax profilesfor Arize credentials andax ai-integrationsfor LLM provider keys. If credentials are not available through these channels, ask the user. - CRITICAL — Never fabricate evaluation results: If an evaluation task fails, is cancelled, or produces no scores, report the failure clearly and explain what went wrong. Do NOT perform a "manual evaluation," invent quality scores, estimate percentages, or present any agent-generated analysis as if it came from the Arize evaluation system. Instead suggest: (1) fix the identified issue and retry, (2) try running from the Arize UI, (3) verify integration credentials with
ax ai-integrations list, (4) contact support at https://arize.com/support
Concepts
What is an Evaluator?
An evaluator is an LLM-as-judge definition. It contains:
| Field | Description |
|---|---|
| Template | The judge prompt. Uses {variable} placeholders (e.g. {input}, {output}, {context}) that get filled in at run time via a task's column mappings. |
| Classification choices | The set of allowed output labels (e.g. factual / hallucinated). Binary is the default and most common. Each choice can optionally carry a numeric score. |
| AI Integration | Stored LLM provider credentials (OpenAI, Anthropic, Bedrock, etc.) the evaluator uses to call the judge model. |
| Model | The specific judge model (e.g. gpt-4o, claude-sonnet-4-5). |
| Invocation params | Optional JSON of model settings like {"temperature": 0}. Low temperature is recommended for reproducibility. |
| Optimization direction | Whether higher scores are better (maximize) or worse (minimize). Sets how the UI renders trends. |
| Data granularity | Whether the evaluator runs at the span, trace, or session level. Most evaluators run at the span level. |
Evaluators are versioned — every prompt or model change creates a new immutable version. The most recent version is active.
What is a Task?
A task is how you run one or more evaluators against real data. Tasks are attached to a project (live traces/spans) or a dataset (experiment runs). A task contains:
| Field | Description |
|---|---|
| Evaluators | List of evaluators to run. You can run multiple in one task. |
| Column mappings | Maps each evaluator's template variables to actual field paths on spans or experiment runs (e.g. "input" → "attributes.input.value"). This is what makes evaluators portable across projects and experiments. |
| Query filter | SQL-style expression to select which spans/runs to evaluate (e.g. "span_kind = 'LLM'"). Optional but important for precision. |
| Continuous | For project tasks: whether to automatically score new spans as they arrive. |
| Sampling rate | For continuous project tasks: fraction of new spans to evaluate (0–1). |
Data Granularity
The --data-granularity flag controls what unit of data the evaluator scores. It defaults to span and only applies to project tasks (not dataset/experiment tasks — those evaluate experiment runs directly).
| Level | What it evaluates | Use for | Result column prefix |
|---|---|---|---|
span (default) |
Individual spans | Q&A correctness, hallucination, relevance | eval.{name}.label / .score / .explanation |
trace |
All spans in a trace, grouped by context.trace_id |
Agent trajectory, task correctness — anything that needs the full call chain | trace_eval.{name}.label / .score / .explanation |
session |
All traces in a session, grouped by attributes.session.id and ordered by start time |
Multi-turn coherence, overall tone, conversation quality | session_eval.{name}.label / .score / .explanation |
How trace and session aggregation works
For trace granularity, spans sharing the same context.trace_id are grouped together. Column values used by the evaluator template are comma-joined into a single string (each value truncated to 100K characters) before being passed to the judge model.
For session granularity, the same trace-level grouping happens first, then traces are ordered by start_time and grouped by attributes.session.id. Session-level values are capped at 100K characters total.
The {conversation} template variable
At session granularity, {conversation} is a special template variable that renders as a JSON array of {input, output} turns across all traces in the session, built from attributes.input.value / attributes.llm.input_messages (input side) and attributes.output.value / attributes.llm.output_messages (output side).
At span or trace granularity, {conversation} is treated as a regular template variable and resolved via column mappings like any other.
Multi-evaluator tasks
A task can contain evaluators at different granularities. At runtime the system uses the highest granularity (session > trace > span) for data fetching and automatically splits into one child run per evaluator. Per-evaluator query_filter in the task's evaluators JSON further narrows which spans are included (e.g., only tool-call spans within a session).
Basic CRUD
AI Integrations
AI integrations store the LLM provider credentials the evaluator uses. For full CRUD — listing, creating for all providers (OpenAI, Anthropic, Azure, Bedrock, Vertex, Gemini, NVIDIA NIM, custom), updating, and deleting — use the arize-ai-provider-integration skill.
Quick reference for the common case (OpenAI):
# Check for an existing integration first
ax ai-integrations list --space SPACE
# Create if none exists
ax ai-integrations create \
--name "My OpenAI Integration" \
--provider openAI \
--api-key $OPENAI_API_KEY
Copy the returned integration ID — it is required for ax evaluators create --ai-integration-id.
Evaluators
# List / Get
ax evaluators list --space SPACE
ax evaluators get ID # accepts name or ID
ax evaluators get NAME --space SPACE # required when using name instead of ID
ax evaluators list-versions NAME_OR_ID
ax evaluators get-version VERSION_ID
# Create (creates the evaluator and its first version)
ax evaluators create \
--name "Answer Correctness" \
--space SPACE \
--description "Judges if the model answer is correct" \
--template-name "correctness" \
--commit-message "Initial version" \
--ai-integration-id INT_ID \
--model-name "gpt-4o" \
--include-explanations \
--use-function-calling \
--classification-choices '{"correct": 1, "incorrect": 0}' \
--template 'You are an evaluator. Given the user question and the model response, decide if the response correctly answers the question.
User question: {input}
Model response: {output}
Respond with exactly one of these labels: correct, incorrect'
# Create a new version (for prompt or model changes — versions are immutable)
ax evaluators create-version NAME_OR_ID \
--commit-message "Added context grounding" \
--template-name "correctness" \
--ai-integration-id INT_ID \
--model-name "gpt-4o" \
--include-explanations \
--classification-choices '{"correct": 1, "incorrect": 0}' \
--template 'Updated prompt...
{input} / {output} / {context}'
# Update metadata only (name, description — not prompt)
ax evaluators update NAME_OR_ID \
--name "New Name" \
--description "Updated description"
# Delete (permanent — removes all versions)
ax evaluators delete NAME_OR_ID
Key flags for create:
| Flag | Required | Description |
|---|---|---|
--name |
yes | Evaluator name (unique within space) |
--space |
yes | Space name or ID to create in |
--template-name |
yes | Eval column name — alphanumeric, spaces, hyphens, underscores |
--commit-message |
yes | Description of this version |
--ai-integration-id |
yes | AI integration ID (from above) |
--model-name |
yes | Judge model (e.g. gpt-4o) |
--template |
yes | Prompt with {variable} placeholders (single-quoted in bash) |
--classification-choices |
yes | JSON object mapping choice labels to numeric scores e.g. '{"correct": 1, "incorrect": 0}' |
--description |
no | Human-readable description |
--include-explanations |
no | Include reasoning alongside the label |
--use-function-calling |
no | Prefer structured function-call output |
--invocation-params |
no | JSON of model params e.g. '{"temperature": 0}' |
--data-granularity |
no | span (default), trace, or session. Only relevant for project tasks, not dataset/experiment tasks. See Data Granularity section. |
--direction |
no | Optimization direction: maximize or minimize. Sets how the UI renders trends. |
--provider-params |
no | JSON object of provider-specific parameters |
Tasks
PROJECT_NAME,DATASET_NAME, andevaluator_idall accept a name or base64 ID.
# List / Get
ax tasks list --space SPACE
ax tasks list --project PROJECT_NAME
ax tasks list --dataset DATASET_NAME --space SPACE
ax tasks get TASK_ID
# Create (project — continuous)
ax tasks create \
--name "Correctness Monitor" \
--task-type template_evaluation \
--project PROJECT_NAME \
--evaluators '[{"evaluator_id": "EVAL_ID", "column_mappings": {"input": "attributes.input.value", "output": "attributes.output.value"}}]' \
--is-continuous \
--sampling-rate 0.1
# Create (project — one-time / backfill)
ax tasks create \
--name "Correctness Backfill" \
--task-type template_evaluation \
--project PROJECT_NAME \
--evaluators '[{"evaluator_id": "EVAL_ID", "column_mappings": {"input": "attributes.input.value", "output": "attributes.output.value"}}]' \
--no-continuous
# Create (experiment / dataset)
ax tasks create \
--name "Experiment Scoring" \
--task-type template_evaluation \
--dataset DATASET_NAME --space SPACE \
--experiment-ids "EXP_ID_1,EXP_ID_2" \ # base64 IDs from `ax experiments list --space SPACE -o json`
--evaluators '[{"evaluator_id": "EVAL_ID", "column_mappings": {"output": "output"}}]' \
--no-continuous
# Trigger a run (project task — use data window)
ax tasks trigger-run TASK_ID \
--data-start-time "2026-03-20T00:00:00" \
--data-end-time "2026-03-21T23:59:59" \
--wait
# Trigger a run (experiment task — use experiment IDs)
ax tasks trigger-run TASK_ID \
--experiment-ids "EXP_ID_1" \ # base64 ID from `ax experiments list --space SPACE -o json`
--wait
# Monitor
ax tasks list-runs TASK_ID
ax tasks get-run RUN_ID
ax tasks wait-for-run RUN_ID --timeout 300
ax tasks cancel-run RUN_ID --force
Time format for trigger-run: 2026-03-21T09:00:00 — no trailing Z.
Additional trigger-run flags:
| Flag | Description |
|---|---|
--max-spans |
Cap processed spans (default 10,000) |
--override-evaluations |
Re-score spans that already have labels |
--wait / -w |
Block until the run finishes |
--timeout |
Seconds to wait with --wait (default 600) |
--poll-interval |
Poll interval in seconds when waiting (default 5) |
Run status guide:
| Status | Meaning |
|---|---|
completed, 0 spans |
The eval index lags 1–2 hours — spans ingested recently may not be indexed yet. Shift the window to data at least 2 hours old, or widen the time range to cover more historical data. |
cancelled ~1s |
Integration credentials invalid |
cancelled ~3min |
Found spans but LLM call failed — check model name or key |
completed, N > 0 |
Success — check scores in UI |
Workflow A: Create an evaluator for a project
Use this when the user says something like "create an evaluator for my Playground Traces project".
Step 1: Confirm the project name
ax spans export accepts a project name directly — no ID lookup needed. If you don't know the project name, list available projects:
ax projects list --space SPACE -o json
Find the entry whose "name" matches (case-insensitive) and use that name as PROJECT in subsequent commands. If you later hit a validation error with a name, fall back to using the project's "id" (a base64 string) instead.
Step 2: Understand what to evaluate
If the user specified the evaluator type (hallucination, correctness, relevance, etc.) → skip to Step 3.
If not, sample recent spans to base the evaluator on actual data:
ax spans export PROJECT --space SPACE -l 10 --days 30 --stdout
Inspect attributes.input, attributes.output, span kinds, and any existing annotations. Identify failure modes (e.g. hallucinated facts, off-topic answers, missing context) and propose 1–3 concrete evaluator ideas. Let the user pick.
Each suggestion must include: the evaluator name (bold), a one-sentence description of what it judges, and the binary label pair in parentheses. Format each like:
- Name — Description of what is being judged. (
label_a/label_b)
Example:
- Response Correctness — Does the agent's response correctly address the user's financial query? (
correct/incorrect) - Hallucination — Does the response fabricate facts not grounded in retrieved context? (
factual/hallucinated)
Step 3: Confirm or create an AI integration
ax ai-integrations list --space SPACE -o json
If a suitable integration exists, note its ID. If not, create one using the arize-ai-provider-integration skill. Ask the user which provider/model they want for the judge.
Step 4: Create the evaluator
Use the template design best practices below. Keep the evaluator name and variables generic — the task (Step 6) handles project-specific wiring via column_mappings.
ax evaluators create \
--name "Hallucination" \
--space SPACE \
--template-name "hallucination" \
--commit-message "Initial version" \
--ai-integration-id INT_ID \
--model-name "gpt-4o" \
--include-explanations \
--use-function-calling \
--classification-choices '{"factual": 1, "hallucinated": 0}' \
--template 'You are an evaluator. Given the user question and the model response, decide if the response is factual or contains unsupported claims.
User question: {input}
Model response: {output}
Respond with exactly one of these labels: hallucinated, factual'
Step 5: Ask — backfill, continuous, or both?
Recommended approach: Always start with a small backfill (~100 historical spans) to validate the evaluator before turning on continuous monitoring. This lets you catch column mapping errors, wrong span kinds, and template issues on known data before scoring all future production spans. Only enable continuous after a backfill confirms correct scoring.
Before creating the task, ask:
"Would you like to: (a) Run a backfill on historical spans (one-time)? (b) Set up continuous evaluation on new spans going forward? (c) Both — backfill first to validate, then keep scoring new spans automatically? (recommended)"
Step 6: Determine column mappings from real span data
Do not guess paths. Pull a sample and inspect what fields are actually present:
ax spans export PROJECT --space SPACE -l 5 --days 7 --stdout
For each template variable ({input}, {output}, {context}), find the matching JSON path. Common starting points — always verify on your actual data before using:
| Template var | LLM span | CHAIN span |
|---|---|---|
input |
attributes.input.value |
attributes.input.value |
output |
attributes.llm.output_messages.0.message.content |
attributes.output.value |
context |
attributes.retrieval.documents.contents |
— |
tool_output |
attributes.input.value (fallback) |
attributes.output.value |
Validate span kind alignment: If the evaluator prompt assumes LLM final text but the task targets CHAIN spans (or vice versa), runs can cancel or score the wrong text. Make sure the query_filter on the task matches the span kind you mapped.
query_filter only works on indexed attributes: The query_filter in the evaluators JSON is evaluated against the eval index, not the raw span store. Attributes under attributes.metadata.* or custom keys may not be indexed and will silently match nothing. Use well-known indexed attributes like span_kind or attributes.llm.model_name for filtering. If a filter returns 0 spans despite data existing, try removing the filter as a diagnostic step.
Full example --evaluators JSON:
[
{
"evaluator_id": "EVAL_ID",
"query_filter": "span_kind = 'LLM'",
"column_mappings": {
"input": "attributes.input.value",
"output": "attributes.llm.output_messages.0.message.content",
"context": "attributes.retrieval.documents.contents"
}
}
]
Include a mapping for every variable the template references. Omitting one causes runs to produce no valid scores.
Step 7: Create the task
Backfill only (a):
ax tasks create \
--name "Hallucination Backfill" \
--task-type template_evaluation \
--project PROJECT \
--evaluators '[{"evaluator_id": "EVAL_ID", "column_mappings": {"input": "attributes.input.value", "output": "attributes.output.value"}}]' \
--no-continuous
Continuous only (b):
ax tasks create \
--name "Hallucination Monitor" \
--task-type template_evaluation \
--project PROJECT \
--evaluators '[{"evaluator_id": "EVAL_ID", "column_mappings": {"input": "attributes.input.value", "output": "attributes.output.value"}}]' \
--is-continuous \
--sampling-rate 0.1
Both (c): Use --is-continuous on create, then also trigger a backfill run in Step 8.
Step 8: Trigger a backfill run (if requested)
Eval index lag: The eval index is built asynchronously from the primary trace store and can lag 1–2 hours. For your first test run, use a time window ending at least 2 hours in the past. If you set
--data-end-timeto "now" on spans ingested in the last hour, the run will complete successfully but score 0 spans.
First find what time range has data:
ax spans export PROJECT --space SPACE -l 100 --days 1 --stdout # try last 24h first
ax spans export PROJECT --space SPACE -l 100 --days 7 --stdout # widen if empty
Use the start_time / end_time fields from real spans to set the window. For the first validation run, cap --max-spans at ~100 to get quick feedback:
ax tasks trigger-run TASK_ID \
--data-start-time "2026-03-20T00:00:00" \
--data-end-time "2026-03-21T23:59:59" \
--max-spans 100 \
--wait
Review scores and explanations before widening to the full backfill or enabling continuous.
Workflow B: Create an evaluator for an experiment
Use this when the user says something like "create an evaluator for my experiment" or "evaluate my dataset runs".
If the user says "dataset" but doesn't have an experiment: A task must target an experiment (not a bare dataset). Ask:
"Evaluation tasks run against experiment runs, not datasets directly. Would you like help creating an experiment on that dataset first?"
If yes, use the arize-experiment skill to create one, then return here.
Step 1: Find the dataset and experiment names
ax datasets list --space SPACE
ax experiments list --dataset DATASET_NAME --space SPACE -o json
Note the dataset name and the experiment name(s) to score. These accept names or IDs in subsequent commands — names are preferred.
Step 2: Understand what to evaluate
If the user specified the evaluator type → skip to Step 3.
If not, inspect a recent experiment run to base the evaluator on actual data:
ax experiments export EXPERIMENT_NAME --dataset DATASET_NAME --space SPACE --stdout | python3 -c "import sys,json; runs=json.load(sys.stdin); print(json.dumps(runs[0], indent=2))"
Look at the output, input, evaluations, and metadata fields. Identify gaps (metrics the user cares about but doesn't have yet) and propose 1–3 evaluator ideas. Each suggestion must include: the evaluator name (bold), a one-sentence description, and the binary label pair in parentheses — same format as Workflow A, Step 2.
Step 3: Confirm or create an AI integration
Same as Workflow A, Step 3.
Step 4: Create the evaluator
Same as Workflow A, Step 4. Keep variables generic.
Step 5: Determine column mappings from real run data
Run data shape differs from span data. Inspect:
ax experiments export EXPERIMENT_NAME --dataset DATASET_NAME --space SPACE --stdout | python3 -c "import sys,json; runs=json.load(sys.stdin); print(json.dumps(runs[0], indent=2))"
Common mapping for experiment runs:
output→"output"(top-level field on each run)input→ check if it's on the run or embedded in the linked dataset examples
If input is not on the run JSON, export dataset examples to find the path:
ax datasets export DATASET_NAME --space SPACE --stdout | python3 -c "import sys,json; ex=json.load(sys.stdin); print(json.dumps(ex[0], indent=2))"
Step 6: Create the task
ax tasks create \
--name "Experiment Correctness" \
--task-type template_evaluation \
--dataset DATASET_NAME --space SPACE \
--experiment-ids "EXP_ID" \ # base64 ID from `ax experiments list --space SPACE -o json`
--evaluators '[{"evaluator_id": "EVAL_ID", "column_mappings": {"output": "output"}}]' \
--no-continuous
Step 7: Trigger and monitor
ax tasks trigger-run TASK_ID \
--experiment-ids "EXP_ID" \ # base64 ID from `ax experiments list --space SPACE -o json`
--wait
ax tasks list-runs TASK_ID
ax tasks get-run RUN_ID
Best Practices for Template Design
1. Use generic, portable variable names
Use {input}, {output}, and {context} — not names tied to a specific project or span attribute (e.g. do not use {attributes_input_value}). The evaluator itself stays abstract; the task's column_mappings is where you wire it to the actual fields in a specific project or experiment. This lets the same evaluator run across multiple projects and experiments without modification.
Arquivos desta skill
3Perguntas sobre a skill arize-evaluator
Como instalo a skill arize-evaluator no Claude Code?
Execute npx degit github/awesome-copilot/skills/arize-evaluator ~/.claude/skills/arize-evaluator. O Claude Code carrega skills de ~/.claude/skills (todos os projetos) ou .claude/skills (um projeto) e usa uma skill quando a descrição dela corresponde à tarefa.
Quais clientes podem usar a skill arize-evaluator?
Qualquer cliente que leia o formato Agent Skills: Claude Code, Codex, Gemini CLI e claude.ai (envie como ZIP). Scripts da skill são executados apenas onde o cliente permite execução de código.
Qual é a diferença entre um evaluator e uma task no Arize?
Um evaluator é uma definição de LLM-as-judge que contém um template de prompt e configurações de modelo, enquanto uma task é a execução de um ou mais evaluators contra dados reais em um projeto ou dataset.
Quais granularidades de dados são suportadas para avaliações?
As avaliações podem ser executadas nos níveis de span, trace ou session, dependendo se você está pontuando unidades individuais, cadeias de chamadas completas ou conversas de múltiplos turnos.
Como faço para lidar com a autenticação de provedores de LLM?
Você deve usar o comando ax ai-integrations para gerenciar as credenciais de provedores como OpenAI ou Anthropic, em vez de ler arquivos de ambiente diretamente.