forget

Agent Skills › rohitg00/agentmemory › forget

forget

GitHub

用于删除代理持久化记忆。通过搜索匹配项、展示结果并获取用户显式确认后，调用接口删除指定记忆ID，保障隐私安全。

plugin/skills/forget/SKILL.md rohitg00/agentmemory

Trigger Scenarios

用户要求遗忘特定信息用户要求删除记忆用户要求移除笔记

Install

npx skills add rohitg00/agentmemory --skill forget -g -y

More Options

Non-standard path

npx skills add https://github.com/rohitg00/agentmemory/tree/main/plugin/skills/forget -g -y

Use without installing

npx skills use rohitg00/agentmemory@forget

指定 Agent (Claude Code)

npx skills add rohitg00/agentmemory --skill forget -a claude-code -g -y

安装 repo 全部 skill

npx skills add rohitg00/agentmemory --all -g -y

预览 repo 内 skill

npx skills add rohitg00/agentmemory --list

SKILL.md

Frontmatter

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

Version History

e01540e Current 2026-10-19 02:22
更新记忆搜索参数以支持项目/代理范围；修改删除接口参数格式为逗号分隔字符串；修正旧版中关于会话擦除和ID类型的错误描述。
2d38daf 2026-08-19 18:52
新增关于删除整个会话时需收集所有memory id的说明；更新Checklist以强调必须使用真实id而非bare sessionId。
a8e7d19 2026-07-24 11:39