Phoenix LLM Observability
Orchestra-Research/AI-Research-SKILLs
Sets up Arize Phoenix to trace, evaluate and monitor LLM applications, with instrumentation for OpenAI, LangChain and LlamaIndex and a self-hosted server.
Adds Olakai monitoring to an existing LLM application with minimal code changes, then configures custom KPIs so the dashboard tracks business outcomes instead of just token counts.
$ npx skills add andrewyng/context-hub --skill integrate -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install andrewyng/context-hub integrate --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/andrewyng/context-hub.git skills-src && mkdir -p .claude/skills && cp -r skills-src/content/olakai/skills/integrate .claude/skills/integrate && rm -rf skills-srcUse ~/.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/
Install the "integrate" agent skill from https://github.com/andrewyng/context-hub/tree/main/content/olakai/skills/integrate into .claude/skills/integrate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "integrate", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/andrewyng/context-hub/tree/main/content/olakai/skills/integrateType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add andrewyng/context-hub --skill integrate -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install andrewyng/context-hub integrate --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/andrewyng/context-hub.git skills-src && mkdir -p .agents/skills && cp -r skills-src/content/olakai/skills/integrate .agents/skills/integrate && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "integrate" agent skill from https://github.com/andrewyng/context-hub/tree/main/content/olakai/skills/integrate into .agents/skills/integrate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "integrate", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add andrewyng/context-hub --skill integrate -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install andrewyng/context-hub integrate --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/andrewyng/context-hub.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/content/olakai/skills/integrate .cursor/skills/integrate && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "integrate" agent skill from https://github.com/andrewyng/context-hub/tree/main/content/olakai/skills/integrate into .cursor/skills/integrate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "integrate", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/andrewyng/context-hub.git --path content/olakai/skills/integrate--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add andrewyng/context-hub --skill integrate -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install andrewyng/context-hub integrate --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/andrewyng/context-hub.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/content/olakai/skills/integrate .gemini/skills/integrate && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "integrate" agent skill from https://github.com/andrewyng/context-hub/tree/main/content/olakai/skills/integrate into .gemini/skills/integrate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "integrate", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install andrewyng/context-hub integrateInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add andrewyng/context-hub --skill integrate -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/andrewyng/context-hub.git skills-src && mkdir -p .github/skills && cp -r skills-src/content/olakai/skills/integrate .github/skills/integrate && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "integrate" agent skill from https://github.com/andrewyng/context-hub/tree/main/content/olakai/skills/integrate into .github/skills/integrate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "integrate", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add andrewyng/context-hub --skill integrate -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install andrewyng/context-hub integrate --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/andrewyng/context-hub.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/content/olakai/skills/integrate .opencode/skills/integrate && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "integrate" agent skill from https://github.com/andrewyng/context-hub/tree/main/content/olakai/skills/integrate into .opencode/skills/integrate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "integrate", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
integrateAdds Olakai monitoring to an existing LLM application with minimal code changes, then configures custom KPIs so the dashboard tracks business outcomes instead of just token counts.
Prerequisites are a working AI agent already using OpenAI, Anthropic or another LLM, the Olakai CLI installed and authenticated, a per-agent API key fetched through the CLI, and Node 18 or newer or Python 3.7 or newer depending on the SDK used. The skill stresses that monitoring alone only gives token counts and raw request data; the value comes from configuring at least two to four custom KPIs answering how you know the agent is performing well, and KPIs cannot be shared across agents, so a new agent needs its own KPI definitions even if they duplicate another agent's.
It explains the data pipeline from SDK custom data through a schema into a context variable and then a KPI formula: only fields registered in that schema become usable variables, formula evaluation is case-insensitive so differently-cased field names all work, and a number-typed field needs an actual numeric value rather than a numeric string. A quick-start section installs the SDK package for TypeScript or JavaScript projects to begin what the skill calls a five-minute integration.
8 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 67dcbeb. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
jqnpmpipFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use npm and pip, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
OLAKAI_API_KEYOPENAI_API_KEYANTHROPIC_API_KEYFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Olakai Monitoring Integration loads about 4.5k tokens when it runs. Until then it costs about 35 tokens; SKILL.md has 917 words of instructions outside code blocks.
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.
The automated check found no risky patterns in SKILL.md.
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.
The full file from andrewyng/context-hub at commit 67dcbeb, republished under its MIT licence (© andrewyng). 917 words, ~4,549 tokens.
.claude/skills/integrate/SKILL.md (or your agent's skills folder).This skill guides you through adding Olakai monitoring to an existing AI agent or LLM-powered application with minimal code changes.
For full SDK documentation, see: https://app.olakai.ai/llms.txt
npm install -g olakai-cli && olakai login)olakai agents get AGENT_ID --json | jq '.apiKey')Note: Each agent can have its own API key. Create one with
olakai agents create --name "Name" --with-api-key
Adding monitoring is only the first step. The real value of Olakai comes from tracking custom KPIs specific to your agent's business purpose.
Without KPIs configured:
With KPIs configured:
Plan to configure at least 2-4 KPIs that answer: "How do I know this agent is performing well?"
KPIs are unique per agent. If adding monitoring to an agent that needs the same KPIs as another already-configured agent, you must still create new KPI definitions for this agent. KPIs cannot be shared or reused across agents.
Before adding monitoring, understand how custom data flows through Olakai:
SDK customData → CustomDataConfig (Schema) → Context Variable → KPI Formula → kpiData| Rule | Consequence |
|---|---|
| Only CustomDataConfig fields become variables | Unregistered customData fields are NOT usable in KPIs |
| Formula evaluation is case-insensitive | stepCount, STEPCOUNT, StepCount all work in formulas |
| NUMBER configs need numeric values | Don't send "5" (string), send 5 (number) |
IMPORTANT: The SDK accepts any JSON in
customData, but only fields registered as CustomDataConfigs are processed. Unregistered fields are stored but cannot be used in KPIs.
1. Install the SDK:
npm install @olakai/sdk2. Add tracking after your LLM call:
Before:
import OpenAI from "openai";
const openai = new OpenAI({ apiKey: process.env.OPENAI_API_KEY });
const response = await openai.chat.completions.create({
model: "gpt-4o",
messages: [{ role: "user", content: userMessage }],
});After:
import OpenAI from "openai";
import { olakaiConfig, olakai } from "@olakai/sdk";
olakaiConfig({ apiKey: process.env.OLAKAI_API_KEY });
const openai = new OpenAI({ apiKey: process.env.OPENAI_API_KEY });
const response = await openai.chat.completions.create({
model: "gpt-4o",
messages: [{ role: "user", content: userMessage }],
});
// Track the interaction (fire-and-forget)
olakai("event", "ai_activity", {
prompt: userMessage,
response: response.choices[0].message.content,
tokens: response.usage?.total_tokens,
userEmail: user.email,
task: "Customer Experience",
});1. Install the SDK:
pip install olakai-sdk2. Add tracking after your LLM call:
Before:
from openai import OpenAI
client = OpenAI(api_key=os.getenv("OPENAI_API_KEY"))
response = client.chat.completions.create(
model="gpt-4o",
messages=[{"role": "user", "content": user_message}],
)After:
from openai import OpenAI
from olakaisdk import olakai_config, olakai, OlakaiEventParams
olakai_config(os.getenv("OLAKAI_API_KEY"))
client = OpenAI(api_key=os.getenv("OPENAI_API_KEY"))
response = client.chat.completions.create(
model="gpt-4o",
messages=[{"role": "user", "content": user_message}],
)
# Track the interaction
olakai("event", "ai_activity", OlakaiEventParams(
prompt=user_message,
response=response.choices[0].message.content,
tokens=response.usage.total_tokens,
userEmail=user.email,
task="Customer Experience",
))Pattern A: Single LLM Client
You have one OpenAI/Anthropic client used throughout your app.
Use the fire-and-forget olakai() call after each completion.
Pattern B: Multiple LLM Calls per Request Your agent makes several LLM calls to complete one task. Use manual event tracking to aggregate calls into a single event.
Pattern C: Streaming Responses You stream LLM responses to users. Track after the stream completes with the full accumulated response.
Pattern D: Third-Party LLM (not OpenAI/Anthropic)
You use Perplexity, Groq, local models, etc.
Use manual event tracking via olakai() or olakai_event().
// lib/olakai.ts - Initialize once at app startup
import { olakaiConfig } from "@olakai/sdk";
olakaiConfig({
apiKey: process.env.OLAKAI_API_KEY!,
debug: process.env.NODE_ENV === "development",
});# lib/olakai.py - Initialize once at app startup
import os
from olakaisdk import olakai_config
olakai_config(
api_key=os.getenv("OLAKAI_API_KEY"),
debug=os.getenv("DEBUG") == "true"
)TypeScript:
olakai("event", "ai_activity", {
prompt: userMessage,
response: aiResponse,
userEmail: user.email,
task: "Customer Experience",
});Python:
olakai("event", "ai_activity", OlakaiEventParams(
prompt=user_message,
response=ai_response,
userEmail=user.email,
task="Customer Experience",
))For assistive AI (chatbots/copilots), use chatId to group multiple turns of a conversation together. This is required for CHAT-scoped KPIs that analyze the full conversation.
olakai("event", "ai_activity", {
prompt: userMessage,
response: aiResponse,
chatId: conversationId, // groups turns in the same conversation
userEmail: user.email,
});When to use
chatId: If your agent handles multi-turn conversations and you want KPIs that evaluate the entire conversation (e.g., sentiment scoring, satisfaction), pass a consistentchatIdacross all turns.
IMPORTANT: Only send fields you've registered as CustomDataConfigs (Step 5.3). Unregistered fields are stored but cannot be used in KPIs.
Only send data you'll use in KPIs or for filtering. Don't duplicate fields already tracked by the platform (session ID, agent ID, user email, timestamps, token count, model, provider — all tracked automatically).
TypeScript:
olakai("event", "ai_activity", {
prompt: userMessage,
response: aiResponse,
userEmail: user.email,
customData: {
// Only include fields registered as CustomDataConfigs
Department: user.department,
ProjectId: currentProject.id,
Priority: ticket.priority,
},
});If your agent makes multiple LLM calls per task, aggregate them into a single event.
taskExecutionId— Critical for multi-agent workflows. If multiple agents collaborate on the same task, the orchestrator must generate ONEtaskExecutionIdand pass it to all agents. This is how Olakai correlates cross-agent work as a single logical task.
async function processDocument(doc: Document): Promise<string> {
const startTime = Date.now();
let totalTokens = 0;
// Step 1: Extract
const extraction = await openai.chat.completions.create({
model: "gpt-4o",
messages: [{ role: "user", content: `Extract from: ${doc.content}` }],
});
totalTokens += extraction.usage?.total_tokens ?? 0;
// Step 2: Analyze
const analysis = await openai.chat.completions.create({
model: "gpt-4o",
messages: [{ role: "user", content: `Analyze: ${extraction.choices[0].message.content}` }],
});
totalTokens += analysis.usage?.total_tokens ?? 0;
const result = analysis.choices[0].message.content ?? "";
// Track the complete workflow as ONE event
olakai("event", "ai_activity", {
prompt: `Process document: ${doc.title}`,
response: result,
tokens: totalTokens,
requestTime: Date.now() - startTime,
taskExecutionId: crypto.randomUUID(),
task: "Data Processing & Analysis",
customData: {
DocumentType: doc.type,
StepCount: 2,
Success: 1,
},
});
return result;
}This step is required to get real value from Olakai. Without KPIs, you're only tracking events — not gaining actionable insights.
npm install -g olakai-cli
olakai loginolakai agents create \
--name "Document Processor" \
--description "Processes and summarizes documents" \
--workflow WORKFLOW_ID \
--with-api-keyEvery agent MUST belong to a workflow, even if it's the only agent.
# Check if agent has a workflow
olakai agents get YOUR_AGENT_ID --json | jq '.workflowId'
# If null, create a workflow and associate:
olakai workflows create --name "Your Workflow Name" --json
olakai agents update YOUR_AGENT_ID --workflow WORKFLOW_IDIMPORTANT: Create configs for ALL fields you send in
customData. Only registered fields can be used in KPIs. CustomDataConfigs are agent-scoped.
olakai custom-data create --agent-id YOUR_AGENT_ID --name "DocumentType" --type STRING
olakai custom-data create --agent-id YOUR_AGENT_ID --name "StepCount" --type NUMBER
olakai custom-data create --agent-id YOUR_AGENT_ID --name "Success" --type NUMBER
# Verify all configs exist for this agent
olakai custom-data list --agent-id YOUR_AGENT_IDolakai kpis create \
--name "Documents Processed" \
--agent-id YOUR_AGENT_ID \
--calculator-id formula \
--formula "IF(Success = 1, 1, 0)" \
--aggregation SUM
olakai kpis create \
--name "Avg Steps per Document" \
--agent-id YOUR_AGENT_ID \
--calculator-id formula \
--formula "StepCount" \
--aggregation AVERAGEAfter creating configs, ensure your SDK code sends exactly those field names:
customData: {
DocumentType: doc.type, // Matches CustomDataConfig "DocumentType"
StepCount: 2, // Matches CustomDataConfig "StepCount"
Success: true ? 1 : 0, // Matches CustomDataConfig "Success"
}// app/api/chat/route.ts
import { NextRequest, NextResponse } from "next/server";
import { olakai } from "@olakai/sdk";
import { auth } from "@/auth";
export async function POST(req: NextRequest) {
const session = await auth();
if (!session?.user) {
return NextResponse.json({ error: "Unauthorized" }, { status: 401 });
}
const { message } = await req.json();
const response = await openai.chat.completions.create({
model: "gpt-4o",
messages: [{ role: "user", content: message }],
});
olakai("event", "ai_activity", {
prompt: message,
response: response.choices[0].message.content,
userEmail: session.user.email!,
task: "Customer Experience",
});
return NextResponse.json({ reply: response.choices[0].message.content });
}from fastapi import FastAPI, Depends
from olakaisdk import olakai_config, olakai, OlakaiEventParams
app = FastAPI()
@app.on_event("startup")
async def startup():
olakai_config(os.getenv("OLAKAI_API_KEY"))
client = OpenAI(api_key=os.getenv("OPENAI_API_KEY"))
@app.post("/chat")
async def chat(message: str, user: User = Depends(get_current_user)):
response = client.chat.completions.create(
model="gpt-4o",
messages=[{"role": "user", "content": message}]
)
olakai("event", "ai_activity", OlakaiEventParams(
prompt=message,
response=response.choices[0].message.content,
userEmail=user.email,
task="Customer Experience",
))
return {"reply": response.choices[0].message.content}Track after the stream completes with the full response:
const stream = await openai.chat.completions.create({
model: "gpt-4o",
messages: [{ role: "user", content: userMessage }],
stream: true,
});
let fullResponse = "";
for await (const chunk of stream) {
fullResponse += chunk.choices[0]?.delta?.content ?? "";
res.write(chunk.choices[0]?.delta?.content ?? "");
}
// Track after stream completes
olakai("event", "ai_activity", {
prompt: userMessage,
response: fullResponse,
userEmail: user.email,
});try {
const response = await openai.chat.completions.create({
model: "gpt-4o",
messages,
});
return response.choices[0].message.content;
} catch (error) {
// Track the failed attempt
olakai("event", "ai_activity", {
prompt: messages[messages.length - 1].content,
response: `Error: ${error instanceof Error ? error.message : "Unknown"}`,
task: "Software Development",
customData: { Success: 0 },
});
throw error;
}For Anthropic, Perplexity, or other providers, use manual tracking:
import Anthropic from "@anthropic-ai/sdk";
const anthropic = new Anthropic({ apiKey: process.env.ANTHROPIC_API_KEY });
async function callClaude(prompt: string): Promise<string> {
const startTime = Date.now();
const response = await anthropic.messages.create({
model: "claude-sonnet-4-20250514",
max_tokens: 1024,
messages: [{ role: "user", content: prompt }],
});
const content = response.content[0].type === "text" ? response.content[0].text : "";
olakai("event", "ai_activity", {
prompt,
response: content,
tokens: response.usage.input_tokens + response.usage.output_tokens,
requestTime: Date.now() - startTime,
task: "Content Development",
});
return content;
}Never assume your integration is working. Always validate by generating a test event and inspecting the actual data.
Run your application to trigger at least one LLM call.
olakai activity list --limit 1 --json
olakai activity get EVENT_ID --jsonCheck customData is present:
olakai activity get EVENT_ID --json | jq '.customData'Check KPIs are numeric (not strings or null):
olakai activity get EVENT_ID --json | jq '.kpiData'CORRECT:
{ "My KPI": 42 }WRONG (formula stored as string):
{ "My KPI": "MyVariable" }Fix: olakai kpis update KPI_ID --formula "MyVariable"
WRONG (null value):
{ "My KPI": null }Fix by ensuring:
olakai custom-data create --agent-id ID --name "MyVariable" --type NUMBER1. Trigger LLM call (generate event)
↓
2. Fetch: olakai activity get ID --json
↓
3. Event exists? NO → Check API key, SDK init, debug mode
↓
4. customData correct? NO → Fix SDK customData parameter
↓
5. kpiData numeric? NO → olakai kpis update ID --formula "X"
↓
6. kpiData not null? NO → Create CustomDataConfig, check field name case
↓
✅ Integration validated| Category | Operators |
|---|---|
| Arithmetic | +, -, *, / |
| Comparison | <, <=, =, <>, >=, > |
| Logical | AND, OR, NOT |
| Conditional | IF(condition, true_val, false_val) |
| Null handling | ISNA(value), ISDEFINED(value) |
--formula "StepCount" # passthrough
--formula "SuccessRate * 100" # percentage conversion
--formula "IF(Success = 1, 1, 0)" # conditional counting
--formula "IF(PII detected, 1, 0)" # built-in variable
--formula "IF(ISDEFINED(MyField), MyField, 0)" # null-safe| Aggregation | Use For |
|---|---|
SUM | Totals, counts |
AVERAGE | Rates, percentages |
// TypeScript — initialize once
import { olakaiConfig, olakai } from "@olakai/sdk";
olakaiConfig({ apiKey: process.env.OLAKAI_API_KEY });
// Track any interaction
olakai("event", "ai_activity", {
prompt: "input",
response: "output",
tokens: 1500,
requestTime: 5000,
userEmail: "user@example.com",
chatId: "conversation-id",
taskExecutionId: "uuid-shared-across-agents",
task: "Data Processing & Analysis",
customData: { StepCount: 3, Success: 1 },
});# Python — initialize once
from olakaisdk import olakai_config, olakai, OlakaiEventParams
olakai_config(os.getenv("OLAKAI_API_KEY"))
# Track any interaction
olakai("event", "ai_activity", OlakaiEventParams(
prompt="input",
response="output",
tokens=1500,
requestTime=5000,
userEmail="user@example.com",
chatId="conversation-id",
taskExecutionId="uuid-shared-across-agents",
task="Data Processing & Analysis",
customData={"StepCount": 3, "Success": 1},
))© andrewyng, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in content/olakai/skills/integrate of andrewyng/context-hub.
Open the folder on GitHubat commit 67dcbeb
Olakai Monitoring Integration 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Olakai Monitoring Integration this skillandrewyng/context-hub | 14k | — | ~4.5k | Automated safety check: Pass | MIT | |
| Phoenix LLM ObservabilityOrchestra-Research/AI-Research-SKILLs | 13k | 2 repos | ~2.9k | Automated safety check: Pass | MIT | |
| Langfusedavila7/claude-code-templates | 32k | 6 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Phoenix Integration SnippetsArize-ai/phoenix | 12k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Langfuse Cost Tuningjeremylongshore/tons-of-skills-marketplace | 2.8k | 1 repos | ~2.4k | Automated safety check: Pass | MIT | |
| Langfuse Hello Worldjeremylongshore/tons-of-skills-marketplace | 2.8k | 1 repos | ~1.9k | Automated safety check: Pass | MIT |
Orchestra-Research/AI-Research-SKILLs
Sets up Arize Phoenix to trace, evaluate and monitor LLM applications, with instrumentation for OpenAI, LangChain and LlamaIndex and a self-hosted server.
davila7/claude-code-templates
Expert in Langfuse - the open-source LLM observability platform.
Arize-ai/phoenix
Generates onboarding code snippets for Phoenix tracing integrations and wires them into the project onboarding UI.
jeremylongshore/tons-of-skills-marketplace
Monitor and optimize LLM costs using Langfuse analytics and dashboards.
jeremylongshore/tons-of-skills-marketplace
Create a minimal working Langfuse trace example. An agent skill from jeremylongshore/tons-of-skills-marketplace.
majiayu000/claude-skill-registry
Expert in Langfuse - the open-source LLM observability platform.
andrewyng/context-hub
Fetches current documentation for third-party APIs and SDKs with the chub CLI before the agent writes code against them, instead of relying on remembered API shapes.
andrewyng/context-hub
Guides building Tavily integrations for web search, URL extraction, site crawling and AI-assisted research in Python or JavaScript agent and RAG projects.
andrewyng/context-hub
Helps choose between Bloc and Cubit in Flutter and sets defaults for packages, lifecycle, widget binding and tests.
andrewyng/context-hub
Sequences parts-mcp tool calls for finding, pricing and checking availability of electronic components, including BOM processing and datasheet navigation.
andrewyng/context-hub
Collects reusable Playwright patterns for logging in during end-to-end tests: password forms, OAuth redirects, saved browser state and TOTP two-factor codes.
andrewyng/context-hub
Builds a new AI agent with Olakai monitoring from the start: CLI login, SDK integration, per-agent KPI configuration and an end-to-end check that data flows.
Works with
Adds Olakai monitoring to an existing LLM application with minimal code changes, then configures custom KPIs so the dashboard tracks business outcomes instead of just token counts. 7 or newer depending on the SDK used. The skill stresses that monitoring alone only gives token counts and raw request data; the value comes from configuring at least two to four custom KPIs answering how you know the agent is performing well, and KPIs cannot be shared across agents, so a new agent needs its own KPI definitions even if they duplicate another agent's.
Olakai Monitoring Integration fits situations like: adding Olakai monitoring to an existing LLM-powered application; configuring custom KPIs so Olakai tracks business outcomes, not just tokens; debugging why a custom data field isn't showing up in a KPI.
Run `npx skills add andrewyng/context-hub --skill integrate -a claude-code`. Or copy the skill folder (content/olakai/skills/integrate in andrewyng/context-hub) into .claude/skills/integrate in your project. Claude Code loads it when a task matches its description.
Run `npx skills add andrewyng/context-hub --skill integrate -a codex`. Or copy the skill folder (content/olakai/skills/integrate in andrewyng/context-hub) into .agents/skills/integrate in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add andrewyng/context-hub --skill integrate -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/integrate, .gemini/skills/integrate, .github/skills/integrate and .opencode/skills/integrate in your project.
Going by SKILL.md and its folder, Olakai Monitoring Integration needs the command-line tools its instructions call (jq, npm and pip) and credentials named OLAKAI_API_KEY, OPENAI_API_KEY and ANTHROPIC_API_KEY. Our summary lists: The Olakai CLI, installed and authenticated; An Olakai API key for the agent; Node.js 18 or newer, or Python 3.7 or newer.
SKILL.md contains no URLs. Its commands use npm and pip, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Olakai Monitoring Integration is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 4.5k tokens (SKILL.md is roughly 18k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Olakai Monitoring Integration: Phoenix LLM Observability (Orchestra-Research/AI-Research-SKILLs, 13k stars), Langfuse (davila7/claude-code-templates, 32k stars), Phoenix Integration Snippets (Arize-ai/phoenix, 12k stars) and Langfuse Cost Tuning (jeremylongshore/tons-of-skills-marketplace, 2.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
andrewyng (a GitHub user) maintains it in andrewyng/context-hub, which has 13,977 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on May 31, 2026.
Source: andrewyng/context-hub on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.