forget

用于从 agentmemory 中遗忘指定数据的破坏性技能：先用 memory_smart_search 检索匹配的持久记忆，向用户展示 ID、标题与范围并取得明确确认，再用 memory_governance_delete 按 ID 删除，并分别报告 deleted、notFound、failed；不支持按观察或整段会话擦除，lesson 需用另有工具删除。

rohitg00

热度 0.00

最近更新 2026-10-19 02:52:24

分类：知识依赖：MCP 服务应用场景：笔记整理 / 工作流

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add rohitg00/agentmemory/forget

Metadata

name: forget
description: Delete selected durable memories 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

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 as query, 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_delete with memoryIds as 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_delete and its lessonId; memory_governance_delete does not touch lessons.
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.

Troubleshooting

See TROUBLESHOOTING.md if memory_smart_search or memory_governance_delete is not available.