Leexi (leexi.ai). Use this skill for ANY Leexi request — searching and reading data. Whenever a task involves Leexi, use this skill instead of calling the AP...
---
name: oo-leexi
description: "Leexi (leexi.ai). Use this skill for ANY Leexi request — searching and reading data. Whenever a task involves Leexi, use this skill instead of calling the API directly."
allowed-tools: [Bash(oo *)]
metadata:
title: "Leexi"
author: "OOMOL"
version: "1.0.0"
service: "leexi"
categories: "Productivity, Communication"
homepage: "https://www.leexi.ai/"
icon: "https://static.oomol.com/logo/third-party/leexi.svg"
---
# Leexi
Operate **Leexi** through your OOMOL-connected account. This skill calls the `leexi` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.
Category: Productivity, Communication. Exposes 6 action(s).
## Running an action
Assume the user has already installed the oo CLI, signed in, and connected Leexi. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.
**1. Inspect the contract** to get the authoritative input/output schema before building a payload:
```bash
oo connector schema "leexi" --action "<action_name>"
```
**2. Run the action** with a JSON payload that matches the input schema:
```bash
oo connector run "leexi" --action "<action_name>" --data '<json>' --json
```
- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.
- The response is `{ "data": ..., "meta": { "executionId": "..." } }`; the execution id lives under `meta.executionId`.
Each action below links to a reference file with its purpose and exact commands. Read the linked file, then fetch the live schema with `oo connector schema` before constructing `--data`.
## Available actions
- [`get_call`](actions/get_call.md) — Retrieve one Leexi call or meeting by UUID.
- [`get_call_note`](actions/get_call_note.md) — Retrieve one Leexi call note by UUID.
- [`list_call_notes`](actions/list_call_notes.md) — List call notes for a Leexi call, optionally filtered by prompt UUID.
- [`list_calls`](actions/list_calls.md) — List calls and meetings in the current Leexi workspace with optional filters.
- [`list_teams`](actions/list_teams.md) — List teams in the current Leexi workspace.
- [`list_users`](actions/list_users.md) — List users in the current Leexi workspace.
## Safety
- Read actions (get / list / search) are safe to run directly.
- **Create, update, send, or post actions change Leexi state — confirm the exact payload and effect with the user before running.**
- **Delete or remove actions are destructive — always confirm the target and get explicit approval first.**
## First-time setup
These are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.
- **`oo: command not found`** — install the oo CLI (other platforms: <https://cli.oomol.com/install-guide.md>):
```bash
curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux
```
```powershell
irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShell
```
- **Not signed in / authentication error** — sign in to your OOMOL account once:
```bash
oo auth login
```
- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — Leexi is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:
```text
https://console.oomol.com/app-connections?provider=leexi
```
- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.
## Resources
- Leexi homepage: https://www.leexi.ai/
don't have the plugin yet? install it then click "run inline in claude" again.