メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
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.
| name | supermemory-status |
| description | 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. |
| allowed-tools | Bash(node:*) |
Show whether Supermemory is connected and which credential source is active:
node ~/.codex/supermemory/status.js
On Windows, if running the command from Codex and sandbox execution is likely to fail for ~/.codex paths, request escalated shell execution immediately instead of trying the sandbox first. Use a narrow approval reason such as:
Run Supermemory status from the Codex home directory so it can read the installed credentials.
Use this when the user asks whether memory is active, what Supermemory account is connected, or whether Codex can currently use Supermemory.
Never print the full API key. The script masks credentials; preserve that masking in the response.