Update to Agent Memory

{
  "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.",
  "included_files": [
    {
      "relative_path": "EXAMPLES.md",
      "size_in_bytes": 1454
    }
  ],
  "name": "forget",
  "skill_md_contents": "---\nname: forget\ndescription: 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.\nargument-hint: \"[what to forget - session ID, file path, or search term]\"\nuser-invocable: true\n---\n\nThe user wants to remove data from agentmemory: $ARGUMENTS\n\n## Quick start\n\n```json\nmemory_smart_search { \"query\": \"old api key in config\", \"limit\": 20 }\n```\n\nShow the matches, get a yes, then:\n\n```json\nmemory_governance_delete { \"memoryIds\": [\"abc12345\", \"def67890\"], \"reason\": \"user privacy request\" }\n```\n\nExpected output:\n\n```text\nFound 2 matching memories. Confirmed. Deleted 2 memories.\n```\n\n## Why\n\nThis is destructive and irreversible. Show exactly what will be deleted and get\nan explicit yes before calling delete. Delete by memory ID, never a bare session.\n\n## Workflow\n\n1. Search with `memory_smart_search`, the user's text as `query`, `limit: 20`.\n2. Show what matched: session ids, memory ids, titles. Ask for explicit\n   confirmation. Do not proceed on silence or a vague \"sure, whatever\".\n3. On confirmation, call `memory_governance_delete` with `memoryIds` (array or\n   comma-separated string) and optional `reason` (default `plugin skill request`).\n4. To drop a whole session, collect every memory id in that session from the\n   search results and pass them all. The MCP does not accept a bare `sessionId`.\n5. Lessons are separate: delete one with `memory_lesson_delete` and its\n   `lessonId`; `memory_governance_delete` does not touch lessons.\n6. Report the deletion count back. A count of 0 means the ids did not exist;\n   say so instead of claiming a delete.\n\n## Anti-patterns\n\nWRONG: search returns matches, you immediately call `memory_governance_delete`\nwithout showing them or waiting for a yes.\n\nRIGHT: list the matches, ask \"Delete these 2? (yes/no)\", and only delete after\nan explicit yes.\n\n## Checklist\n\n- Matches were shown to the user before any delete.\n- An explicit yes was received, not assumed.\n- `memoryIds` holds real ids from the search, never a bare `sessionId`.\n- Final message states the actual count deleted.\n\n## See also\n\n- `remember`: the write side; forget is its undo.\n- `recall`: find the exact memory id before deleting.\n\n## Troubleshooting\n\nSee ../_shared/TROUBLESHOOTING.md if `memory_smart_search` or `memory_governance_delete` is not available.\n"
}