skills/olakai-get-started/SKILL.md
Install the CLI, authenticate, and send your first monitored event. AUTO-INVOKE when: CLI is not installed, user is not authenticated, user asks about getting started with Olakai, user wants to try Olakai, user mentions they don't have an account yet, or when other skills fail due to missing prerequisites. TRIGGER KEYWORDS: get started, setup, install olakai, olakai account, sign up, signup, new to olakai, try olakai, olakai onboarding, first agent, getting started, no account, create account, register. DO NOT load for: users who are already authenticated and have agents set up (use olakai-new-project, olakai-integrate, or olakai-troubleshoot instead).
npx skillsauth add olakai-ai/olakai-skills olakai-get-startedInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill helps you get set up with Olakai from scratch - from creating an account to generating your first monitored event.
IMPORTANT: For account creation, prefer the in-terminal API flow (Step 1) which calls
POST /api/auth/signupdirectly. If the user prefers a browser-based flow, use the full developer signup URL with PLG parameters:https://app.olakai.ai/signup?flow=developer&source=claude-codeNEVER shorten this tohttps://app.olakai.ai/signup— the query parameters are required for the developer onboarding flow.
Before proceeding, let's check your current setup status.
Run these diagnostic commands to determine where to start:
# Check 1: Is CLI installed?
which olakai || echo "CLI_NOT_INSTALLED"
# Check 2: Is user authenticated?
olakai whoami 2>/dev/null || echo "NOT_AUTHENTICATED"
# Check 3: Are there any agents?
olakai agents list --json 2>/dev/null | head -5 || echo "NO_AGENTS_OR_NOT_AUTH"
Based on results, jump to the appropriate section:
| Result | Jump To |
|--------|---------|
| CLI_NOT_INSTALLED | Step 1: Create Account |
| NOT_AUTHENTICATED | Step 2: Install CLI if CLI missing, else Step 3: Authenticate |
| Empty agents list | Step 4: Register Your Agent. Use "register" language (not "create your first agent") when presenting next steps. |
| Agents exist | You're all set! Use /olakai-new-project or /olakai-integrate instead |
If you don't have an Olakai account yet, create one directly from the terminal.
Ask the user for:
Use the Bash tool to call the signup endpoint. Replace the placeholder values with what the user provided:
curl -s -X POST https://app.olakai.ai/api/auth/signup \
-H "Content-Type: application/json" \
-d '{
"email": "USER_EMAIL",
"companyName": "USER_COMPANY",
"firstName": "USER_FIRST_NAME",
"lastName": "USER_LAST_NAME",
"source": "claude-code",
"medium": "skill"
}'
Expected response:
{ "success": true, "message": "Check your email to verify your account.", "requiresVerification": true }
Tell the user:
If the API call fails (network issues, corporate firewall, etc.), direct the user to the browser-based signup:
https://app.olakai.ai/signup?flow=developer&source=claude-code
IMPORTANT: Always include the
?flow=developer&source=claude-codequery parameters — they activate the developer onboarding flow.
After verifying your email, you'll have access to the dashboard where you can see your agents and events.
The Olakai CLI is the primary tool for configuring agents, KPIs, and custom data.
npm install -g olakai-cli
olakai --version
# Should output: olakai-cli/0.2.x
Permission errors on macOS/Linux:
# Option 1: Use sudo (not recommended)
sudo npm install -g olakai-cli
# Option 2: Fix npm permissions (recommended)
mkdir -p ~/.npm-global
npm config set prefix '~/.npm-global'
echo 'export PATH=~/.npm-global/bin:$PATH' >> ~/.bashrc
source ~/.bashrc
npm install -g olakai-cli
Windows:
# Run PowerShell as Administrator
npm install -g olakai-cli
Connect the CLI to your Olakai account.
olakai login
This opens your browser for secure authentication. After logging in:
olakai whoami
Expected output:
Logged in as: [email protected]
Account: Your Organization
"Not authenticated" errors:
# Clear cached credentials and re-login
olakai logout
olakai login
Browser doesn't open:
# The CLI will display a URL - copy and paste it manually
olakai login
# Look for: "Open this URL in your browser: https://app.olakai.ai/..."
Corporate proxy/firewall issues:
app.olakai.ai is accessibleThis step registers your AI agent (or any AI-powered feature) in Olakai so it can be monitored. This doesn't build any code — it creates a tracking record where Olakai collects analytics, KPIs, and governance data.
# Create agent with an API key for SDK integration
olakai agents create \
--name "My First Agent" \
--description "Testing Olakai integration" \
--with-api-key \
--json
Save the output! It contains your apiKey which you'll need for SDK integration:
{
"id": "cmkbteqn501kyjy4yu6p6xrrx",
"name": "My First Agent",
"apiKey": "sk_agent_xxxxx..."
}
# Add to your shell profile (.bashrc, .zshrc, etc.)
export OLAKAI_API_KEY="sk_agent_xxxxx..."
Or add to your project's .env file:
OLAKAI_API_KEY=sk_agent_xxxxx...
If you need to get the API key again:
olakai agents get AGENT_ID --json | jq '.apiKey'
Choose based on your project's language.
npm install @olakai/sdk
Quick Integration:
import { OlakaiSDK } from "@olakai/sdk";
import OpenAI from "openai";
// Initialize Olakai
const olakai = new OlakaiSDK({
apiKey: process.env.OLAKAI_API_KEY!
});
await olakai.init();
// Wrap your OpenAI client
const openai = olakai.wrap(
new OpenAI({ apiKey: process.env.OPENAI_API_KEY }),
{ provider: "openai" }
);
// Use as normal - events are automatically tracked
const response = await openai.chat.completions.create({
model: "gpt-4",
messages: [{ role: "user", content: "Hello!" }]
});
pip install olakai-sdk
Quick Integration:
import os
from openai import OpenAI
from olakaisdk import olakai_config, instrument_openai
# Initialize Olakai
olakai_config(os.getenv("OLAKAI_API_KEY"))
instrument_openai()
# Use OpenAI as normal - events are automatically tracked
client = OpenAI()
response = client.chat.completions.create(
model="gpt-4",
messages=[{"role": "user", "content": "Hello!"}]
)
Let's verify everything is working.
Execute the code from Step 5. This should:
# List recent events (replace with your agent ID)
olakai activity list --limit 1 --json
# Get full event details
olakai activity get EVENT_ID --json | jq '{prompt, response, tokens, model}'
Expected output:
{
"prompt": "Hello!",
"response": "Hello! How can I assist you today?",
"tokens": 25,
"model": "gpt-4"
}
Open https://app.olakai.ai and navigate to your agent's activity view. You should see the event appear within seconds.
You're now set up! Here's what to explore next:
Track business-specific metrics:
// TypeScript
const response = await openai.chat.completions.create(
{ model: "gpt-4", messages },
{
customData: {
feature: "customer-support",
ticketId: "TICKET-123",
priority: 1
}
}
);
# Python
from olakaisdk import olakai_context
with olakai_context(customData={"feature": "customer-support", "ticketId": "TICKET-123"}):
response = client.chat.completions.create(...)
Define metrics that aggregate your custom data:
# First, create the custom data config for your agent
olakai custom-data create --agent-id YOUR_AGENT_ID --name "Priority" --type NUMBER
# Then create a KPI
olakai kpis create \
--name "High Priority Events" \
--agent-id YOUR_AGENT_ID \
--calculator-id formula \
--formula "IF(Priority == 1, 1, 0)" \
--aggregation SUM
Note: KPIs are created per-agent. If you later create additional agents, you'll need to create KPIs for each one separately — they can't be shared across agents. CustomDataConfigs, on the other hand, are account-level and shared.
/olakai-new-project - Detailed guide for building agents with full observability/olakai-integrate - Add monitoring to existing AI code/olakai-troubleshoot - Debug issues with events or KPIs| Problem | Solution |
|---------|----------|
| command not found: olakai | Reinstall CLI: npm install -g olakai-cli |
| Not authenticated | Run olakai login |
| Network error | Check internet connection, try again |
| Problem | Solution |
|---------|----------|
| Invalid API key | Verify OLAKAI_API_KEY env var is set correctly |
| Events not appearing | Check API key matches agent, verify network access |
| Import errors | Ensure SDK is installed: npm install @olakai/sdk or pip install olakai-sdk |
| Problem | Solution |
|---------|----------|
| Browser doesn't open | Copy URL from terminal manually |
| Login succeeds but CLI says not authenticated | Try olakai logout then olakai login again |
| Corporate SSO issues | Contact your IT admin about OAuth access |
# Check status
which olakai # CLI installed?
olakai whoami # Authenticated?
olakai agents list # Agents exist?
# Setup commands
npm install -g olakai-cli # Install CLI
olakai login # Authenticate
olakai agents create --name "Name" --with-api-key --json # Register agent
# SDK installation
npm install @olakai/sdk # TypeScript
pip install olakai-sdk # Python
# Verify events
olakai activity list --limit 1 --json
olakai activity get EVENT_ID --json
npm install -g olakai-cli)olakai login)OLAKAI_API_KEY environment variable set@olakai/sdk or olakai-sdk)Once all boxes are checked, you're ready to build production AI agents with full observability!
tools
Set up and self-heal Olakai monitoring for the coding tool you are using — Claude Code, OpenAI Codex CLI, Cursor, Google Gemini CLI, or Antigravity CLI. Installs hooks, creates the agent record, and explains how to enrich events with KPIs. This is the skill for "monitor my coding tool itself" (not for instrumenting your own agent's source code with the SDK — that is olakai-integrate). AUTO-INVOKE when user wants to: monitor Claude Code / Codex / Cursor / Gemini CLI / Antigravity CLI sessions, monitor THIS coding tool, add observability to a local coding agent, track my own coding-assistant usage, set up olakai monitoring in this workspace, see what is being monitored on this machine, check if monitoring is working, or enable / repair hooks-based monitoring for any local coding agent. TRIGGER KEYWORDS: olakai monitor, monitor my coding tool, monitor this tool, monitor claude code, monitor codex, monitor cursor, monitor gemini cli, monitor antigravity, codex cli, cursor hooks, gemini cli, gemini-cli hooks, antigravity cli, antigravity, agy, local coding agent, local agent monitoring, olakai hooks, olakai monitor init, olakai monitor list, olakai monitor doctor, olakai monitor repair, monitor workspace, track sessions, is my monitoring working, monitoring not working, no events from claude code, claude code monitoring, codex monitoring, cursor monitoring, agents mine, where am i monitoring. DO NOT load for: instrumenting your own agent's SDK code (use olakai-integrate), creating agents from scratch with custom code (use olakai-new-project), generic SDK / KPI / event troubleshooting unrelated to a coding tool (use olakai-troubleshoot).
tools
Diagnose and repair Olakai monitoring for a local coding tool you already set up — Claude Code, OpenAI Codex CLI, or Cursor. Drives `olakai monitor list`, `olakai monitor doctor [--fix]`, and `olakai monitor repair` to self-heal hooks-based monitoring (no events, missing KPIs, broken/deleted agent, drifted config). For first-time setup use olakai-monitor-local-coding-agent instead. AUTO-INVOKE when user says: my coding-tool monitoring isn't working, no events from Claude Code / Codex / Cursor, is monitoring on / working, check my olakai monitoring, what's monitored on this machine, monitor doctor, monitor repair, monitor list, fix my monitoring, my monitored agent disappeared / 404, hooks stopped firing, re-link my monitoring key. TRIGGER KEYWORDS: olakai monitor doctor, olakai monitor repair, olakai monitor list, monitor not working, no events claude code, no events codex, no events cursor, fix monitoring, repair monitoring, agent 404, agent missing, hooks stopped firing, drift, registry, agents mine, where am i monitoring, is my monitoring working, self-heal monitoring. DO NOT load for: first-time setup of a coding tool (use olakai-monitor-local-coding-agent), instrumenting your own agent's SDK code (use olakai-integrate), generic SDK / KPI / event troubleshooting unrelated to a coding tool (use olakai-troubleshoot).
tools
Diagnose and fix issues with events, KPIs, custom data, or SDK integration. AUTO-INVOKE when user mentions: events not appearing, KPIs showing wrong values, KPIs showing strings instead of numbers, custom data missing, null KPIs, authentication errors, CLI not working, events not associated with agent, monitoring broken, SDK errors, or any Olakai-related problem. TRIGGER KEYWORDS: olakai, troubleshoot, debug, not working, events missing, KPI wrong, KPI null, KPI string, customData missing, authentication failed, CLI error, no events, events not appearing, diagnose, fix olakai, broken, SDK error, monitoring issue, API key invalid, events not tracked. DO NOT load for: initial setup (use olakai-new-project or olakai-integrate), or generating reports (use olakai-reports).
tools
Generate usage summaries, KPI trends, ROI reports, and compliance analytics from the terminal. AUTO-INVOKE when user wants: usage summaries, KPI trends, risk analysis, ROI reports, efficiency metrics, agent comparisons, token usage reports, cost analysis, compliance reports, or any analytics without using the web dashboard. TRIGGER KEYWORDS: olakai, analytics, reports, usage summary, KPI trends, risk analysis, ROI, efficiency, agent comparison, token usage, cost analysis, metrics report, dashboard data, CLI analytics, terminal report, compliance, usage report, event summary, performance metrics, AI usage stats. DO NOT load for: setting up monitoring (use olakai-integrate), troubleshooting (use olakai-troubleshoot), or creating new agents (use olakai-new-project).