forget

GitHub

用于从代理记忆中删除特定数据。在展示匹配结果并获取用户明确确认后,调用工具执行不可逆的删除操作,确保隐私安全。

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

Trigger Scenarios

用户说“forget this” 用户要求“delete memory” 用户说“remove that note” 用户希望清除特定数据以保护隐私

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

  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.

Version History

  • a8e7d19 Current 2026-07-24 11:39

Same Skill Collection

plugin/skills/agentmemory-architecture/SKILL.md
plugin/skills/agentmemory-config/SKILL.md
plugin/skills/agentmemory-hooks/SKILL.md
plugin/skills/agentmemory-mcp-tools/SKILL.md
plugin/skills/agentmemory-rest-api/SKILL.md
plugin/skills/commit-context/SKILL.md
plugin/skills/commit-history/SKILL.md
plugin/skills/handoff/SKILL.md
plugin/skills/recall/SKILL.md
plugin/skills/recap/SKILL.md
plugin/skills/remember/SKILL.md
plugin/skills/session-history/SKILL.md
plugin/skills/write-agentmemory-skill/SKILL.md
plugin/skills/agentmemory-agents/SKILL.md

Metadata

Files
0
Version
d219763
Hash
3f3cd1fb
Indexed
2026-07-24 11:39

Главная - Вики-сайт
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-08-07 07:54
浙ICP备14020137号-1 $Гость$