supermemoryai

Log in to Supermemory. Use when the user needs to authenticate, set up their API key, or when memory features report a missing key.

Log out of Supermemory in Codex. Use when the user wants to disconnect Supermemory, remove saved credentials, switch accounts, clear auth state, or stop memory from using the current saved API key.

Show Supermemory connection status for Codex. Use when the user asks whether Supermemory is connected, which account or API key is active, memory hook health, or plugin status.

View the user's Supermemory profile (persistent facts and recent context).

Remove outdated or incorrect information from memory. Use when user says something is no longer true, wants to delete a memory, or information has changed.

Save important project knowledge to memory. Use when user wants to preserve architectural decisions, significant bug fixes, design patterns, or important implementation details for future reference.

Search your coding memory. Use when user asks about past work, previous sessions, how something was implemented, what they worked on before, or wants to recall information from earlier sessions.

Use the Supermemory CLI to programmatically manage memories, documents, profiles, tags, connectors, keys, and teams from the terminal. Covers all commands, flags, and usage patterns.

Supermemory is a state-of-the-art memory and context infrastructure for AI agents. Use this skill when building applications that need persistent memory, user personalization, long-term context retention, or semantic search across knowledge bases. It provides Memory API for learned user context, User Profiles for static/dynamic facts, and RAG for semantic search. Perfect for chatbots, assistants, and knowledge-intensive applications.

Create beautiful, performant SVG animations and illustrations. Use this skill when the user asks to create SVG graphics, icons, illustrations, animated logos, path animations, morphing shapes, loading spinners, or any animated SVG content. Covers SMIL animations, CSS-driven SVG animation, path drawing effects, shape morphing, motion paths, gradients, masks, and filters.

Deep codebase exploration to initialize project memory. Use when starting work on a new project or when user asks to "index" or "learn" the codebase.

Save important information to persistent memory. Use when user explicitly asks to remember something, or when you've solved a significant problem worth preserving.

Search persistent memory for relevant information from past coding sessions. Use when user asks about previous work, past bugs, architectural decisions, or anything that may have been worked on before.

Save important project knowledge to memory. Use when user wants to preserve architectural decisions, significant bug fixes, design patterns, or important implementation details for team reference.

Search your coding memory. Use when user asks about past work, previous sessions, how something was implemented, what they worked on before, or wants to recall information from earlier sessions.

Supermemory is a state-of-the-art memory and context infrastructure for AI agents. Use this skill when building applications that need persistent memory, user personalization, long-term context retention, or semantic search across knowledge bases. It provides Memory API for learned user context, User Profiles for static/dynamic facts, and RAG for semantic search. Perfect for chatbots, assistants, and knowledge-intensive applications.

Automatically benchmark your custom memory implementation against established systems like Supermemory. Set up a public benchmark, or create your own. Compare solutions against quality, latency, features and cost, easily, with a simple UI and CLI.

Use when the user points you at a Preprint workspace (a directory containing `preprint/tabs.md` and `<host>-tN.md` page files). Operate a real Chromium browser through markdown files. Read `preprint/tabs.md` to discover open tabs, read a tab's page file to see its current state, and append exactly one action under `<!-- preprint:actions -->` for the daemon to execute. Use `preprint open / close / status` for tab lifecycle. Do not call `agent-browser` directly while these files exist.