---
name: kumori-stickers
description: This skill should be used when an agent needs to turn an image into a kumori die-cut sticker over MCP - image plus style in, sticker out, no prompts.
---

# kumori stickers

kumori turns a photo into a die-cut sticker. The grammar is fixed:
**image + style in → sticker out.** There is no prompt anywhere in the flow.
The image is the subject; the style is the only creative decision.

Connect to the kumori MCP server at `https://mcp.kumori.camera/`.

## The loop

1. **Orient.** Call `kumori_get_info` first: it returns the user's credit
   balance, generation stats, and a compact style catalog. OAuth-capable
   clients authorize on first use. Each generation spends one credit.
2. **Pick one style.** Use the catalog from `kumori_get_info`, or call
   `kumori_list_filters` for the full live list (slug, name, description).
   Choose ONE slug that suits the image. Never invent slugs.
3. **Get the image in.** Exactly one source per call, in priority order:
   - `input_image_url` — preferred whenever the image already has ANY URL
     (web, CDN, Slack, chat upload).
   - `input_image_data` — base64 (raw or data URL) for local or chat
     images without URLs, up to 4MB.
   - `input_key` — for large local files (>4MB) when shell access exists:
     call `kumori_prepare_upload`, HTTP PUT the bytes to `upload_url`,
     then pass the returned `input_key`.
4. **Generate.** Call `kumori_generate_image` with `filter_slug` plus the
   one image source. Use `wait=true` for a single blocking call (typical
   generation: 45-60s; timeout up to 120s), or `wait=false` to poll.
5. **Poll (when wait=false).** Call `kumori_check_generation` every 2-3
   seconds while status is `pending` or `processing`. The response carries
   `progress.percent`, the current step, and loading text worth relaying
   to the user. Stop on `completed` or `failed`.
6. **Deliver.** On `completed`:
   - Save the sticker when the client has a filesystem: fetch `image_url`
     and write the bytes as returned — the sticker ships with its die-cut
     edge.
   - ALWAYS include `share_url` in your reply. It is the public
     kumori.camera page for the finished sticker and the easiest way for
     the user to view, share, or save it from any device.

## Rules

- Never add prompt text, subject descriptions, or style instructions.
  The tools accept none; the image and the style slug carry everything.
- One image source per call; mixing sources is an error.
- Do not retry a `failed` generation blindly. Read the error first;
  failed generations refund their credit automatically.
- If a tool answers with authentication guidance, surface the OAuth
  reconnect flow to the user. Never collect or handle credentials
  yourself.
- Respect the balance from `kumori_get_info`. If credits are exhausted,
  point the user to https://kumori.camera/credits instead of retrying.