olakai-ai
10 verified skills
olakai
Show your Olakai developer Coding IQ status — monitoring health, personal spend, and budget. AUTO-INVOKE when user asks about: their Olakai monitoring health, personal AI spend, budget status, Coding IQ digest, whether their workspace is monitored, how much they've spent on AI this month, whether they're approaching their budget limit, or wants a quick overview of their Olakai coding status. TRIGGER KEYWORDS: olakai status, my spend, my budget, coding iq status, am I monitored, monitoring health, personal spend, budget limit, how much have I spent, olakai digest, coding status, my olakai, workspace monitored, check my olakai. DO NOT load for: setting up monitoring (use olakai-monitor-local-coding-agent), troubleshooting events or KPIs (use olakai-troubleshoot), generating analytics reports (use olakai-reports), or creating new agents (use olakai-new-project).
development
olakai-get-started
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).
tools
olakai-integrate
Add Olakai to existing AI code with minimal changes — wrap your LLM client, add custom metrics, and validate the integration. AUTO-INVOKE when user wants to: add monitoring to existing code, integrate observability into a working agent, add tracking to LLM calls, wrap OpenAI/Anthropic clients, add analytics to working AI code, or retrofit monitoring to production AI. TRIGGER KEYWORDS: olakai, add monitoring, integrate monitoring, wrap client, observability, SDK integration, @olakai/sdk, olakai-sdk, existing agent, existing code, add tracking, analytics, telemetry, retrofit monitoring, existing LLM, existing OpenAI, existing Anthropic. DO NOT load for: creating new agents from scratch (use olakai-new-project), troubleshooting issues (use olakai-troubleshoot), or generating reports (use olakai-reports).
tools
olakai-new-project
Build a new AI agent project from scratch — design metrics, configure the platform, write SDK code, and validate end-to-end. AUTO-INVOKE when user wants to: build a new AI agent, create an AI workflow, set up a new chatbot or copilot, implement an autonomous agent, design an AI-powered feature, start a new project with AI observability, or add KPI tracking and governance to a new AI system. TRIGGER KEYWORDS: olakai, create agent, new agent, build agent, AI agent, AI workflow, chatbot, copilot, autonomous agent, agent architecture, agentic AI, assistive AI, observability setup, KPI tracking, governance, new AI project, AI monitoring setup, agent from scratch. DO NOT load for: adding monitoring to existing code (use olakai-integrate), troubleshooting existing agents (use olakai-troubleshoot), or generating reports (use olakai-reports).
development
olakai-planning
Create detailed implementation plans for Olakai monitoring that can be executed independently. AUTO-INVOKE when: Creating a plan for Olakai monitoring, writing implementation steps for AI observability, planning agent creation or SDK integration, entering plan mode for Olakai work, designing monitoring architecture. TRIGGER KEYWORDS: plan, implementation plan, steps, roadmap, architecture, design, olakai plan, monitoring plan, agent plan, planning, plan mode. DO NOT load for: Executing implementation (use olakai-new-project or olakai-integrate), troubleshooting (use olakai-troubleshoot), generating reports (use olakai-reports).
development
olakai-reports
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).
tools
olakai-monitor-doctor
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
olakai-monitor-local-coding-agent
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
olakai-monitor-claude-code
Renamed to olakai-monitor-local-coding-agent. This skill now covers all three local coding agents (Claude Code, Codex CLI, Cursor) under one entry point. Existing plugin installs that reference olakai-monitor-claude-code continue to resolve here so they don't break — but the canonical, up-to-date guidance lives in olakai-monitor-local-coding-agent. Load that skill instead.
tools
olakai-troubleshoot
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