rohitg00/agentmemory

forget

Delete selected durable memories from agentmemory after showing them and getting explicit confirmation.

查看源码

使用方法

  1. 复制安装命令,在自己的智能体环境安装前先检查源码包。
  2. 从原始文档核对所需工具、凭据和支持的宿主。
  3. 说明输入材料与期望交付物,并对照来源检查输出。
npx skills add https://github.com/rohitg00/agentmemory --skill forget

开始前需了解

  • 安装不包含模型订阅、API 额度或访问文件的权限。
  • 仓库星数和安装量反映活跃情况,不等于独立质量或安全测试。
仓库原始内容

按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。

The user wants to remove data from agentmemory: $ARGUMENTS

Quick start

json
memory_smart_search { "query": "old api key in config", "targetLayer": "memory", "limit": 20 }

Show the matches, get a yes, then:

json
memory_governance_delete { "memoryIds": "abc12345,def67890", "reason": "user privacy request" }

Expected output:

text
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

  1. Search with memory_smart_search, the user's text as query,

targetLayer: "memory", limit: 20, and the requested project/agent scope. These are selected relevance matches, not an exhaustive inventory.

  1. 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".

  1. On confirmation, call memory_governance_delete with memoryIds as a

comma-separated string and optional reason (default plugin skill request).

  1. 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.

  1. Lessons are separate: delete one with memory_lesson_delete and its

lessonId; memory_governance_delete does not touch lessons.

  1. Check deleted, notFound, and failed in 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.
  • memoryIds holds real ids from the search, never a bare sessionId.
  • 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.

按任务相关推荐

来自同一仓库

更多 Skills

全部 Skills