用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/exiao/skills --skill phoenix-cli命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | phoenix-cli |
| description | Use when debugging LLM apps with Phoenix CLI: traces, errors, experiments. |
| license | Apache-2.0 |
| metadata | {"author":"arize-ai","version":"1.0"} |
Unified skill for Phoenix AI observability: CLI debugging, evaluators, and tracing instrumentation.
| Task | Read This |
|---|---|
| CLI usage, fetch traces, debug failures, analyze experiments | This file (below) |
| Build evaluators (code, LLM, RAG) | references/evals.md + references/evals-rules/ |
| Instrument tracing (OpenInference, spans, production) | references/tracing.md + references/tracing-rules/ |
Phoenix CLI reads PHOENIX_HOST, PHOENIX_API_KEY, and PHOENIX_PROJECT
from the environment (project can also be passed via --project).
Set them in whatever env-management surface your agent runtime uses, e.g.:
# Hermes
echo 'PHOENIX_HOST=https://app.phoenix.arize.com/s/<workspace>' >> ~/.hermes/.env
echo 'PHOENIX_API_KEY=...' >> ~/.hermes/.env
echo 'PHOENIX_PROJECT=bloom_chat' >> ~/.hermes/.env
# Plain shell
export PHOENIX_HOST=https://app.phoenix.arize.com/s/<workspace>
export PHOENIX_API_KEY=...
export PHOENIX_PROJECT=bloom_chat
# OpenClaw gateway
openclaw config set env.vars.PHOENIX_HOST 'https://app.phoenix.arize.com/s/<workspace>'
openclaw config set env.vars.PHOENIX_API_KEY '...'
openclaw config set env.vars.PHOENIX_PROJECT 'bloom_chat'
Verify: px traces --limit 1 (or px traces --limit 1 --project bloom_chat).
Projects: bloom_chat (prod), bloom_chat_dev (dev).
npm install -g @arizeai/phoenix-cli
# Or: npx @arizeai/phoenix-cli
CLI flags override environment variables when specified.
# Recent traces
px traces --limit 10
# Find failed traces
px traces --limit 50 --format raw --no-progress | jq '.[] | select(.status == "ERROR")'
# Specific trace details
px trace <trace-id>
# Errors in spans
px trace <trace-id> --format raw | jq '.spans[] | select(.status_code != "OK")'
# Slowest traces
px traces --limit 20 --format raw --no-progress | jq 'sort_by(-.duration) | .[0:5]'
# Span durations within a trace
px trace <trace-id> --format raw | jq '.spans | sort_by(-.duration_ms) | .[0:5] | .[] | {name, duration_ms, span_kind}'
px traces --limit 50 --format raw --no-progress | \
jq -r '.[].spans[] | select(.span_kind == "LLM") | {model: .attributes["llm.model_name"], prompt_tokens: .attributes["llm.token_count.prompt"], completion_tokens: .attributes["llm.token_count.completion"]}'
px datasets # List datasets
px experiments --dataset my-dataset # List experiments
px experiment <id> --format raw --no-progress | jq '.[] | select(.error != null) | {input: .input, error}' # Failures
px experiment <id> --format raw --no-progress | jq '[.[].latency_ms] | add / length' # Avg latency
| Command | Purpose | Key Options |
|---|---|---|
px traces | Fetch recent traces | -n <limit>, --last-n-minutes, --since, --format, --include-annotations |
px trace <id> | Fetch specific trace | --file, --format, --include-annotations |
px datasets | List datasets | |
px dataset <name> | Fetch dataset examples | --split, --version, --file |
px experiments | List experiments | --dataset <name> (required) |
px experiment <id> | Fetch experiment runs | --format, --file |
px prompts | List prompts | |
px prompt <name> | Fetch prompt |
pretty (default): Human-readable tree viewjson: Formatted JSON with indentationraw: Compact JSON for piping to jqUse --format raw --no-progress when piping.
Key span kinds: LLM, CHAIN, TOOL, RETRIEVER, EMBEDDING, AGENT.
Key LLM span attributes:
llm.model_name, llm.providerllm.token_count.prompt, llm.token_count.completionllm.input_messages.*, llm.output_messages.*input.value, output.valueexception.message| File | Contents |
|---|---|
references/evals.md | Evaluator guide: code evals, LLM evals, RAG evals, experiments, validation, production guardrails |
references/evals-rules/ | 34 rule files for evaluator implementation (fundamentals, error analysis, axial coding, experiments, validation, production) |
references/tracing.md | Tracing guide: setup, instrumentation, span types, projects, sessions, production deployment |
references/tracing-rules/ | 30 rule files for tracing implementation (setup, auto/manual instrumentation, span types, annotations, production) |