Snipe-IT (snipeitapp.com). Use this skill for ANY Snipe-IT request — searching and reading data. Whenever a task involves Snipe-IT, use this skill instead of...
Data & analysis
Snipcart
Try itSnipcart (snipcart.com). Use this skill for ANY Snipcart request — reading, creating, and updating data. Whenever a task involves Snipcart, use this skill instead of calling the API directly.
What it does
Snipcart (snipcart.com). Use this skill for ANY Snipcart request — reading, creating, and updating data. Whenever a task involves Snipcart, use this skill instead of calling the API directly.
The skill document
Snipcart
Operate Snipcart through your OOMOL-connected account. This skill calls the snipcart connector with the 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 Snipcart. Do not run oo auth login or open the connection URL proactively — just run the action. Fall back to 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:
oo connector schema "snipcart" --action ""
2. Run the action with a JSON payload that matches the input schema:
oo connector run "snipcart" --action "" --data '' --json
--datatakes a JSON object string or@path/to/file.json; omit it to send{}.- The response is
{ "data": ..., "meta": { "executionId": "..." } }; the execution id lives undermeta.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 Snipcart customer by ID.get_order— Retrieve one Snipcart order by token. [write]list_customers— List Snipcart customers with pagination and optional filters.list_orders— List completed Snipcart orders with pagination and optional filters.
Safety
- Untagged actions are reads (get / list / search) — safe to run directly.
- Actions tagged
[write]change Snipcart 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: ):curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linuxirm https://cli.oomol.com/install.ps1 | iex # Windows PowerShell -
Not signed in / authentication error — sign in to your OOMOL account once:
oo auth login -
scope_missing/credential_expired/app_not_ready/app_not_found— Snipcart is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:https://console.oomol.com/app-connections?provider=snipcart -
HTTP 402 /
OOMOL_INSUFFICIENT_CREDIT— billing stop. Recharge athttps://console.oomol.com/billing/token-rechargebefore retrying.
Resources
- Snipcart homepage: https://snipcart.com/
Related skills
Cartes.io (cartes.io). Use this skill for ANY Cartes.io request — reading, creating, updating, and deleting data. Whenever a task involves Cartes.io, use this skill instead of calling the API directly.
SamCart (samcart.com). Use this skill for ANY SamCart request — reading, creating, and updating data. Whenever a task involves SamCart, use this skill instead of calling the API directly.
Shopify Storefront (shopify.com). Use this skill for ANY Shopify Storefront request — reading, creating, and updating data. Whenever a task involves Shopify...
Shopify Partner (shopify.com). Use this skill for ANY Shopify Partner request — searching and reading data. Whenever a task involves Shopify Partner, use thi...
Help Scout (helpscout.com). Use this skill for ANY Help Scout request — reading, creating, and updating data. Whenever a task involves Help Scout, use this skill instead of calling the API directly.