Supermemory

Supermemory (supermemory.ai). Use this skill for ANY Supermemory request — reading, creating, updating, and deleting data. Whenever a task involves Supermemory, use this skill instead of calling the API directly.

Operate Supermemory through your OOMOL-connected account. This skill calls the supermemory 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 Supermemory. 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:

bash

oo connector schema "supermemory" --action "<action_name>"

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

bash

oo connector run "supermemory" --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

• add_document — Submit raw text, a transcript, or a public URL for asynchronous memory extraction or managed RAG indexing. [write]
• create_memories — Store one or more already-known facts directly as immediately searchable Supermemory memories. [write]
• delete_document — Permanently delete one source document by its Supermemory ID or caller-provided custom ID. [destructive]
• forget_memory — Soft-delete one memory by ID so it is excluded from normal recall while remaining auditable.
• get_document — Get a Supermemory document and its current processing status, including the final extracted content when available.
• get_profile — Retrieve long-term, recent, and bucketed profile context for one user or tenant container.
• search — Recall relevant memories, document chunks, or both for a question within one tenant container.
• update_memory — Correct one memory by ID, creating a new version while preserving its prior version history. [write]

Safety

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

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

Resources

• Supermemory homepage: https://supermemory.ai