Intelliprint (intelliprint.net). Use this skill for ANY Intelliprint request — searching and reading data. Whenever a task involves Intelliprint, use this sk...
---
name: oo-intelliprint
description: "Intelliprint (intelliprint.net). Use this skill for ANY Intelliprint request — searching and reading data. Whenever a task involves Intelliprint, use this skill instead of calling the API directly."
allowed-tools: [Bash(oo *)]
metadata:
title: "Intelliprint"
author: "OOMOL"
version: "1.0.0"
services: ["intelliprint"]
---
# Intelliprint
Operate **Intelliprint** through your OOMOL-connected account. This skill calls the `intelliprint` 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 Intelliprint. **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 "intelliprint" --action "<action_name>"
```
**2. Run the action** with a JSON payload that matches the input schema:
```bash
oo connector run "intelliprint" --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_background` — Retrieve a single Intelliprint reusable background by ID.
- `get_mailing_list` — Retrieve a single Intelliprint mailing list by ID.
- `get_mailing_list_recipient` — Retrieve one recipient from an Intelliprint mailing list.
- `get_print` — Retrieve a single Intelliprint print job by ID.
- `list_backgrounds` — List Intelliprint reusable backgrounds with official pagination, sorting, field selection, and team filtering.
- `list_mailing_list_recipients` — List recipients for one Intelliprint mailing list with official pagination, sorting, and field selection.
- `list_mailing_lists` — List Intelliprint mailing lists with official pagination and sorting options.
- `list_prints` — List Intelliprint print jobs with official pagination, sorting, and print-specific filters.
## Safety
- Untagged actions are reads (get / list / search) — safe to run directly.
- **Actions tagged `[write]` change Intelliprint 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`** — Intelliprint 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=intelliprint
```
- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.
## Resources
- Intelliprint homepage: https://www.intelliprint.net
don't have the plugin yet? install it then click "run inline in claude" again.