oo-komari

name	oo-komari
description	Komari (github.com). Use this skill for ANY Komari request — reading, creating, updating, and deleting data. Whenever a task involves Komari, use this skill instead of calling the API directly.
allowed-tools	["Bash(oo *)"]
metadata	{"title":"Komari","author":"OOMOL","version":"1.0.0","services":["komari"],"icon":"https://static.oomol.com/logo/third-party/komari.png"}

Komari

Operate Komari through your OOMOL-connected account. This skill calls the komari connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.

Running an action

Assume the user has already installed the oo CLI, signed in, and connected Komari. Do not run oo auth login or open the connection URL proactively — just run the action. Fall back to 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:

oo connector schema "komari" --action "<action_name>"

2. Run the action with a JSON payload that matches the input schema:

oo connector run "komari" --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 is listed below with a one-line description; actions that change state carry a [write] or [destructive] tag. Before constructing --data, fetch the action's live schema with oo connector schema to get its authoritative input fields.

Available actions

• add_client — Create a Komari client. The response contains its enrollment token. [write]
• add_load_notification — Create a load notification rule. [write]
• add_ping_task — Create a ping task. [write]
• batch_delete_clipboard — Delete multiple clipboard entries. [destructive]
• cancel_metric_migration — Cancel the active metric-store migration. [write]
• clear_all_records — Permanently delete all load and ping records. [destructive]
• clear_records — Permanently delete all load records. [destructive]
• create_clipboard — Create a clipboard entry. [write]
• delete_all_sessions — Revoke all login sessions. [destructive]
• delete_clipboard — Delete a clipboard entry. [destructive]
• delete_load_notification — Delete load notification rules. [destructive]
• delete_ping_tasks — Delete ping tasks and their records. [destructive]
• delete_session — Revoke one login session using the stable identifier returned by list_sessions. [destructive]
• disable_offline_notifications — Disable offline notifications for clients. [write]
• disable_traffic_report_notifications — Disable traffic reports for clients. [write]
• edit_client — Update client fields. This changes Komari configuration. [write]
• edit_load_notification — Replace load notification rule fields. [write]
• edit_offline_notifications — Replace offline notification rule fields. [write]
• edit_ping_tasks — Replace ping task fields. [write]
• edit_settings — Update arbitrary Komari settings; invalid database settings can disrupt service. [write]
• edit_traffic_report_notifications — Replace traffic-report rule fields. [write]
• enable_offline_notifications — Enable offline notifications for clients. [write]
• enable_traffic_report_notifications — Enable traffic reports for clients. [write]
• execute_command — DANGEROUS: execute a shell command on selected clients. Komari API keys bypass interactive 2FA for this sensitive RPC. [write]

Safety

• Untagged actions are reads (get / list / search) — safe to run directly.
• Actions tagged [write] change Komari state — confirm the exact payload and effect with the user before running.
• Actions tagged [destructive] remove or overwrite data — 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):

  curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux
  

  irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell
  

• Not signed in / authentication error — sign in to your OOMOL account once:

  oo auth login
  

• scope_missing / credential_expired / app_not_ready / app_not_found — Komari is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:

  https://console.oomol.com/app-connections?provider=komari
  

• HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources

• Komari homepage: https://github.com/komari-monitor/komari