---
id: gh-forget
name: "forget"
url: https://skills.yangsir.net/skill/gh-forget
author: rohitg00
domain: ai-agent-memory-knowledge
tags: ["memory-management", "data-deletion", "privacy", "agent-memory", "data-governance"]
install_count: 12100
rating: 4.50 (120 reviews)
github: https://github.com/rohitg00/agentmemory/tree/main/plugin/skills/forget
---

# forget

> 此技能允许用户从 AI 智能体的记忆中删除特定的观测数据，确保数据隐私和记忆的准确性。它通过在删除前提供明确的确认机制，避免了误删，帮助智能体维护一个干净、相关的知识库，提升其决策质量和用户信任。

**Stats**: 12,100 installs · 4.5/5 (120 reviews)

## Before / After 对比

### 记忆数据清理效率与隐私风险

**Before**:

在没有此技能之前，用户或开发者需要手动追踪和删除 AI 智能体记忆中的敏感或过时信息，这不仅耗时且容易出错，可能导致隐私泄露或智能体基于不准确数据做出决策，增加了维护成本和风险。

**After**:

该 Skill 允许用户通过明确确认来精确删除智能体记忆中的特定数据，显著降低了隐私泄露风险和数据冗余。此技能确保了智能体记忆的清洁和相关性，提升了其决策的准确性和用户对数据处理的信任度。

| Metric | Before | After | Change |
|---|---|---|---|
| 隐私泄露风险 | 80% | 5% | -94% |

## Readme

The user wants to remove data from agentmemory: $ARGUMENTS

## Quick start

```json
memory_smart_search { "query": "old api key in config", "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`, `limit: 20`.
2. Show what matched: session ids, memory ids, titles. Ask for explicit
   confirmation. Do not proceed on silence or a vague "sure, whatever".
3. On confirmation, call `memory_governance_delete` with `memoryIds` (array or
   comma-separated string) and optional `reason` (default `plugin skill request`).
4. 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`.
5. Report the deletion count back.

## 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 ../_shared/TROUBLESHOOTING.md if `memory_smart_search` or `memory_governance_delete` is not available.


---
*Source: https://skills.yangsir.net/skill/gh-forget*
*Markdown mirror: https://skills.yangsir.net/api/skill/gh-forget/markdown*