ImageKit

ImageKit

Operate ImageKit through your OOMOL-connected account. This skill calls the imagekit 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 ImageKit. 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 "imagekit" --action ""

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

oo connector run "imagekit" --action "" --data '' --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

• delete_file — Delete one ImageKit file and all of its versions permanently. [destructive]
• get_file_details — Get details for the current version of an ImageKit file.
• get_purge_status — Get the status of an ImageKit cache purge request. [destructive]
• get_remote_file_metadata — Get image or video metadata from a remote URL through ImageKit.
• get_uploaded_file_metadata — Get image or video metadata for an uploaded ImageKit file.
• list_assets — List or search assets in the ImageKit media library.
• purge_cache — Submit a cache purge request for an ImageKit file URL. [destructive]

Safety

• Untagged actions are reads (get / list / search) — safe to run directly.
• Actions tagged [write] change ImageKit 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 / Linux
  

  irm 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 — ImageKit 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=imagekit
  

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

Resources

• ImageKit homepage: https://imagekit.io