supermemory

name: supermemory description: Supermemory skill for plugin-backed persistent memory, recall, user-profile context, and project-scoped workflows license: MIT compatibility: opencode metadata: audience: developers workflow: memory

Supermemory Skill

Use This Skill For

• cross-session memory and recall
• preserving durable project or user context
• retrieving previously stored high-signal facts before continuing work
• plugin-backed memory workflows inside OpenCode

Do Not Use This Skill For

• storing secrets, API keys, or credentials
• replacing source-of-truth files such as code, configs, or README
• saving noisy, temporary details that will not matter later

Default Workflow

1. Decide whether the information is durable enough to store.
2. Prefer project-scoped memory when the context is repository-specific.
3. Recall before long-running or resumed tasks that depend on prior decisions.
4. Validate recalled context against the current codebase before relying on it.

What To Store

• stable project conventions
• high-value architectural decisions
• recurring user preferences that affect implementation
• long-lived task context that would be expensive to reconstruct

What Not To Store

• tokens, secrets, or private credentials
• raw logs unless they encode a lasting lesson
• temporary debugging notes that will go stale quickly
• facts that are already better represented in checked-in files

Supermemory Plugin Notes

• Plugin package: opencode-supermemory@latest
• Plugin config file: ~/.config/opencode/supermemory.jsonc
• Tool name exposed in OpenCode: supermemory
• API key source for this repo: SUPERMEMORY_API_KEY from the environment
• Plugin config supports tuning retrieval, profile injection, keyword triggers, and compaction behavior

Rules

• Supermemory is a plugin-backed accelerator, not the source of truth.
• Re-check recalled facts against the live repo before making edits.
• Keep stored memory concise and durable.

Done Criteria

• only durable, useful context is stored or retrieved
• recalled information is cross-checked before use
• no secret or transient data is pushed into memory