Conductor

SKILL.md

---
name: oo-conductor
description: "Conductor (conductor.com). Use this skill for ANY Conductor request — searching and reading data. Whenever a task involves Conductor, use this skill instead of calling the API directly."
allowed-tools: [Bash(oo *)]
metadata:
  title: "Conductor"
  author: "OOMOL"
  version: "1.0.1"
  services: ["conductor"]
  icon: "https://static.oomol.com/logo/third-party/conductor.svg"
---

# Conductor

Operate **Conductor** through your OOMOL-connected account. This skill calls the `conductor` 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 Conductor. **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 "conductor" --action "<action_name>"
```

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

```bash
oo connector run "conductor" --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_page` — Retrieve data for one URL in a Conductor Monitoring website.
- `get_statistics` — Retrieve Conductor Monitoring statistics for a whole website or a segment scope.
- `list_affected_pages` — List pages affected by one Conductor Monitoring issue.
- `list_issues` — List Conductor Monitoring issues for a whole website or a segment scope.
- `list_pages` — List pages for a Conductor Monitoring website with pagination.
- `list_segments` — List Conductor Monitoring segments for one website.
- `list_websites` — List websites available in the connected Conductor Monitoring account.

## Safety

- Untagged actions are reads (get / list / search) — safe to run directly.
- **Actions tagged `[write]` change Conductor 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`** — Conductor 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=conductor
  ```

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

## Resources

- Conductor homepage: https://www.conductor.com