agentleFS
hiteshbandhuhiteshbandhu/skills-i-use/skills/ai-engineer-talks/observe-ai-production/SKILL.md

observe-ai-production

Skill1 starsChanged 5 months agoMITView on GitHub

Observes and improves production LLM apps with Arize Phoenix—tracing, layered agent evals, prompt learning loops, and PM/engineering eval pipelines. Use when the user mentions Arize, Phoenix, OpenInference, agent router evals, prompt optimization from traces, or shipping AI with production observability.

The file

Files
SKILL.md

Observe AI production (Arize)

Action playbook from six Arize @ AI Engineer talks. Do not summarize talks — pick a workflow and execute it.

Supporting files: workflows.md · source-index.md

Optional: ./skill-outputs/observe-ai-production/


Step 0 — Pick workflow

What is the user trying to do?
├─ Layered agent evals (router, skills, convergence)     → agent-evals
├─ Hands-on Phoenix agent eval workshop                  → phoenix-workshop
├─ Prompt learning from production traces                → prompt-learning
├─ PM-facing eval frameworks and release gates           → pm-evals
└─ Org-scale eval pipelines (CI, versioning)             → eval-pipelines

See workflows.md. Related: run-llm-evals for cross-vendor eval theory.


Install

cp -r skills/observe-ai-production ~/.claude/skills/
cp -r skills/observe-ai-production ~/.cursor/skills/
cp -r skills/observe-ai-production ~/.codex/skills/

Source: playlists/arize-ai-engineer/.


Cross-cutting rules

RuleSource
Eval router decisions, not only final answers[src-001 @ 0:08:21]
Trace every tool/LLM call for agent eval substrate[src-002 @ 0:06:18]
Calibrate LLM judges on human labels before automation[src-002 @ 0:89:37]
Close loop: observability → dataset → prompt patch[src-003 @ 0:20:00]
Version datasets/scorers like production code[src-005 @ 0:10:00]

Output

Name workflow; save artifacts to ./skill-outputs/observe-ai-production/ when requested; do not auto-commit.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.