TiDB Cloud

SKILL.md

---
name: oo-tidb
description: "TiDB Cloud (pingcap.com). Use this skill for ANY TiDB Cloud request — reading, creating, and updating data. Whenever a task involves TiDB Cloud, use this skill instead of calling the API directly."
allowed-tools: [Bash(oo *)]
metadata:
  title: "TiDB Cloud"
  author: "OOMOL"
  version: "1.0.0"
  service: "tidb"
  categories: "Data & Analytics, Developer Tools"
  homepage: "https://www.pingcap.com/tidb/cloud/"
  icon: "https://static.oomol.com/logo/third-party/tidb.svg"
---

# TiDB Cloud

Operate **TiDB Cloud** through your OOMOL-connected account. This skill calls the `tidb` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.

Category: Data & Analytics, Developer Tools. Exposes 17 action(s).

## Running an action

Assume the user has already installed the oo CLI, signed in, and connected TiDB Cloud. **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 "tidb" --action "<action_name>"
```

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

```bash
oo connector run "tidb" --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_api_key`](actions/get_api_key.md) — Fetch one TiDB Cloud API key by access key.
- [`get_branch`](actions/get_branch.md) — Fetch one TiDB Cloud Starter or Essential branch by branch ID.
- [`get_cluster`](actions/get_cluster.md) — Fetch one TiDB Cloud Starter, Essential, or Dedicated cluster by ID.
- [`get_export`](actions/get_export.md) — Fetch one TiDB Cloud Starter or Essential export task.
- [`get_import`](actions/get_import.md) — Fetch one TiDB Cloud Starter, Essential, or Dedicated import task.
- [`get_node_spec`](actions/get_node_spec.md) — Fetch one TiDB Cloud Dedicated node spec by region, component type, and key.
- [`get_region`](actions/get_region.md) — Fetch one TiDB Cloud Dedicated region by region ID.
- [`list_api_keys`](actions/list_api_keys.md) — List TiDB Cloud API keys visible to the connected organization API key.
- [`list_audit_logs`](actions/list_audit_logs.md) — List TiDB Cloud console audit logs for security and change tracking.
- [`list_branches`](actions/list_branches.md) — List TiDB Cloud Starter or Essential branches for a cluster.
- [`list_clusters`](actions/list_clusters.md) — List TiDB Cloud Starter, Essential, or Dedicated clusters.
- [`list_exports`](actions/list_exports.md) — List TiDB Cloud Starter or Essential export tasks.
- [`list_imports`](actions/list_imports.md) — List TiDB Cloud Starter, Essential, or Dedicated import tasks.
- [`list_node_specs`](actions/list_node_specs.md) — List TiDB Cloud Dedicated node specs available in a region.
- [`list_regions`](actions/list_regions.md) — List TiDB Cloud regions available to the connected organization API key.
- [`show_cloud_providers`](actions/show_cloud_providers.md) — List cloud providers available for TiDB Cloud Dedicated clusters.
- [`show_node_quota`](actions/show_node_quota.md) — List TiDB Cloud Dedicated node quotas for the organization.

## Safety

- Read actions (get / list / search) are safe to run directly.
- **Create, update, send, or post actions change TiDB Cloud 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`** — TiDB Cloud is not connected, or the connection expired or lacks a scope. Connect once (auth type: custom credential) at:

  ```text
  https://console.oomol.com/app-connections?provider=tidb
  ```

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

## Resources

- TiDB Cloud homepage: https://www.pingcap.com/tidb/cloud/