使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/rohitg00/agentmemory --skill forget開始前の確認
- 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
- スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
The user wants to remove data from agentmemory: $ARGUMENTS
Quick start
memory_smart_search { "query": "old api key in config", "targetLayer": "memory", "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.Why
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.
Workflow
- Search with
memory_smart_search, the user's text asquery,
targetLayer: "memory", limit: 20, and the requested project/agent scope. These are selected relevance matches, not an exhaustive inventory.
- Show what matched: memory ids, titles, and scope. Redact secret values. Ask for explicit
confirmation. Do not proceed on silence or a vague "sure, whatever".
- On confirmation, call
memory_governance_deletewithmemoryIdsas a
comma-separated string and optional reason (default plugin skill request).
- Observation or whole-session erasure is not supported by this operation.
Explain that limit before proceeding; never label selected memory deletion as a complete session wipe. Do not pass observation IDs or a sessionId.
- Lessons are separate: delete one with
memory_lesson_deleteand its
lessonId; memory_governance_delete does not touch lessons.
- Check
deleted,notFound, andfailedin the response. Report actual
deletions and unresolved IDs separately. Recheck the selected IDs before retrying a failed request; an interrupted response may hide a completed write.
Anti-patterns
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.
Checklist
- Matches were shown to the user before any delete.
- An explicit yes was received, not assumed.
memoryIdsholds real ids from the search, never a baresessionId.- Final message states the actual count deleted.
See also
remember: the write side; forget is its undo.recall: find the exact memory id before deleting.
Troubleshooting
See TROUBLESHOOTING.md if memory_smart_search or memory_governance_delete is not available.



