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.
In this repository51 other files it gives its agents.
- architect-enterprise-aiSkill
- author-agent-skillsSkill
- build-agent-harnessesSkill
- build-aiewf-2024-ragSkill
- build-generative-mediaSkill
- build-multimodal-productsSkill
- build-rag-search-stacksSkill
- build-robotics-aiSkill
- build-with-deepmindSkill
- build-with-microsoft-aiSkill
- build-with-openaiSkill
- deploy-public-sector-aiSkill
- design-agent-skillsSkill
- evaluate-with-braintrustSkill
- lead-ai-engineering-teamsSkill
- lead-ai-transformationSkill
- learn-summit-2023-remoteSkill
- learn-summit-2023-talksSkill
- navigate-aie-europe-2026Skill
- navigate-aiewf-2024-keynotesSkill
- operate-agent-memorySkill
- operate-legal-ai-agentsSkill
- operate-openclaw-agentsSkill
- optimize-llm-inferenceSkill
- plan-sovereign-aiSkill
- price-ai-productsSkill
- run-aiewf-2024-evalsSkill
- run-llm-evalsSkill
- run-summit-2023-workshopsSkill
- secure-ai-agentsSkill
- ship-ai-as-pmSkill
- ship-aiewf-2024-agentsSkill
- train-llms-locallySkill
- architecture-reviewSkill
- chat-failure-auditSkill
- create-a-skillSkill
- cross-model-reviewSkill
- cto-weekly-reviewSkill
- friction-auditSkill
- ig-carouselSkill
- pdf-reportSkill
- raise-prSkill
- reel-editSkill
- research-reportSkill
- ship-checkSkill
- spec-grounded-designSkill
- state-lifetime-decisionSkill
- ste100Skill
- scroll-engineeringSkill
- ui-uxSkill
- verify-like-a-userSkill
The file
Files
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-pipelinesSee 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
| Rule | Source |
| 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.
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
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.

