remove.bg (remove.bg). Use this skill for ANY remove.bg request — reading, creating, updating, and deleting data. Whenever a task involves remove.bg, use thi...
---
name: oo-remove-bg
description: "remove.bg (remove.bg). Use this skill for ANY remove.bg request — reading, creating, updating, and deleting data. Whenever a task involves remove.bg, use this skill instead of calling the API directly."
allowed-tools: [Bash(oo *)]
metadata:
title: "remove.bg"
author: "OOMOL"
version: "1.0.0"
service: "remove_bg"
categories: "AI, Design & Media"
homepage: "https://www.remove.bg"
icon: "https://static.oomol.com/logo/third-party/Remove.bg.svg"
---
# remove.bg
Operate **remove.bg** through your OOMOL-connected account. This skill calls the `remove_bg` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.
Category: AI, Design & Media. Exposes 3 action(s).
## Running an action
Assume the user has already installed the oo CLI, signed in, and connected remove.bg. **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 "remove_bg" --action "<action_name>"
```
**2. Run the action** with a JSON payload that matches the input schema:
```bash
oo connector run "remove_bg" --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_account`](actions/get_account.md) — Fetch the current remove.bg credit balance and free API call allowance for the authenticated account.
- [`remove_background`](actions/remove_background.md) — Remove the background from an image and upload the generated result file to connector transit storage.
- [`submit_improvement`](actions/submit_improvement.md) — Submit a source image to the remove.bg improvement program for future model quality improvements.
## Safety
- Read actions (get / list / search) are safe to run directly.
- **Create, update, send, or post actions change remove.bg 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`** — remove.bg 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=remove_bg
```
- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.
## Resources
- remove.bg homepage: https://www.remove.bg
don't have the plugin yet? install it then click "run inline in claude" again.