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

Quick start

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.

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, limit: 20.
Show what matched: session ids, memory ids, titles. Ask for explicit confirmation. Do not proceed on silence or a vague "sure, whatever".
On confirmation, call memory_governance_delete with memoryIds (array or comma-separated string) and optional reason (default plugin skill request).
To drop a whole session, collect every memory id in that session from the search results and pass them all. The MCP does not accept a bare sessionId.
Lessons are separate: delete one with memory_lesson_delete and its lessonId; memory_governance_delete does not touch lessons.
Report the deletion count back. A count of 0 means the ids did not exist; say so instead of claiming a delete.