Anrok (anrok.com). Use this skill for ANY Anrok request — searching and reading data. Whenever a task involves Anrok, use this skill instead of calling the A...
---
name: oo-anrok
description: "Anrok (anrok.com). Use this skill for ANY Anrok request — searching and reading data. Whenever a task involves Anrok, use this skill instead of calling the API directly."
allowed-tools: [Bash(oo *)]
metadata:
title: "Anrok"
author: "OOMOL"
version: "1.0.0"
services: ["anrok"]
---
# Anrok
Operate **Anrok** through your OOMOL-connected account. This skill calls the `anrok` connector with the [oo CLI](https://github.com/oomol-lab/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 Anrok. **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 "anrok" --action "<action_name>"
```
**2. Run the action** with a JSON payload that matches the input schema:
```bash
oo connector run "anrok" --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
- `get_customer` — Retrieve one Anrok customer by customer ID.
- `get_product` — Retrieve one Anrok product by external ID.
- `list_customers` — List Anrok customers with cursor pagination.
- `list_filings` — List Anrok filings with optional cursor pagination and filters.
- `list_product_mappings` — List Product ID mappings for one Anrok integration.
- `list_product_tax_categories` — List product tax categories available on the Anrok seller account.
- `list_transactions` — List Anrok transactions with optional cursor pagination and filters.
## Safety
- Untagged actions are reads (get / list / search) — safe to run directly.
- **Actions tagged `[write]` change Anrok 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>):
```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`** — Anrok 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=anrok
```
- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.
## Resources
- Anrok homepage: https://www.anrok.com
don't have the plugin yet? install it then click "run inline in claude" again.