メニュー
Delete specific observations from agentmemory after showing them and getting explicit confirmation. Use when the user says "forget this", "delete memory", "remove that note", or wants to scrub specific data for privacy.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/rohitg00/agentmemory --skill forgetコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
agentmemory configuration, environment variables, ports, and feature flags. Use when enabling a feature, changing ports, setting an API key, configuring auth, or explaining why a feature is off by default.
How agentmemory wires into host coding agents via the connect command. Use when installing agentmemory into a specific agent, when asked which agents are supported, or when a connect adapter writes the wrong config path.
Save a correction or hard-won rule as a confidence-weighted lesson that resurfaces before similar work. Use when the user corrects your approach, says "learn this", "always" or "never do X", or you notice yourself repeating a past mistake.
SOC 職業分類に基づく
SKILL.md を表示中
| name | forget |
| description | Delete specific observations from agentmemory after showing them and getting explicit confirmation. Use when the user says "forget this", "delete memory", "remove that note", or wants to scrub specific data for privacy. |
| argument-hint | [what to forget - session ID, file path, or search term] |
| user-invocable | true |
The user wants to remove data from agentmemory: $ARGUMENTS
memory_smart_search { "query": "old api key in config", "limit": 20 }
Show the matches, get a yes, then:
memory_governance_delete { "memoryIds": ["abc12345", "def67890"], "reason": "user privacy request" }
Expected output:
Found 2 matching memories. Confirmed. Deleted 2 memories.
This is destructive and irreversible. Show exactly what will be deleted and get an explicit yes before calling delete. Delete by memory ID, never a bare session.
memory_smart_search, the user's text as query, limit: 20.memory_governance_delete with memoryIds (array or
comma-separated string) and optional reason (default plugin skill request).sessionId.memory_lesson_delete and its
lessonId; memory_governance_delete does not touch lessons.WRONG: search returns matches, you immediately call memory_governance_delete
without showing them or waiting for a yes.
RIGHT: list the matches, ask "Delete these 2? (yes/no)", and only delete after an explicit yes.
memoryIds holds real ids from the search, never a bare sessionId.remember: the write side; forget is its undo.recall: find the exact memory id before deleting.See ../_shared/TROUBLESHOOTING.md if memory_smart_search or memory_governance_delete is not available.