Skip to content
Back to skills

Forget

ASecurity

Delete a memory from Origin by ID. Destructive and cannot be undone — prefer `/capture` with `supersedes` for corrections. Invoked as `/forget <source_id>`.

  • 3,543 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added May 27, 2026
data-aibashgit

Works with

  • mcp

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add davepoon/buildwithclaude --skill forget --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Forget?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Forget
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/davepoon-forget/badge)](https://www.skillsdirectory.com/skills/davepoon-forget)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: forget
description: >
  Delete a memory from Origin by ID. Destructive and cannot be undone —
  prefer `/capture` with `supersedes` for corrections. Invoked as
  `/forget <source_id>`.
argument-hint: "<source_id>"
allowed-tools: ["Bash", "mcp__plugin_origin_origin__forget", "mcp__plugin_origin_origin__recall"]
---

# /forget

Permanently delete a memory by its `source_id`.

## How to invoke

You need the `source_id`. If the user did not provide it, call
`/recall` first to find the matching memory and confirm with the
user before deleting.

```
forget(memory_id="<source_id>")
```

## When to use

- User says "forget this", "delete that", "that's wrong, remove it".
- User explicitly identifies a memory by ID.

## When NOT to use

- For corrections, prefer storing a new memory with `supersedes` pointing
  at the old one. That preserves history. Use `/capture` with the
  `supersedes` arg instead.
- Bulk deletions — call `/review` first, confirm with the user,
  then delete one at a time.

## Safety

Deletion is destructive. Always confirm with the user before calling forget,
unless the user has already given an explicit, unambiguous instruction in
the same turn (e.g. they pasted the ID and said "delete this").

## Auto-commit ~/.origin/

If the deletion removed a page md (daemon archives the page and
KnowledgeWriter unlinks the file), snapshot the change. Defensive —
silent skip if `git` missing, `~/.origin/` not a repo, or no diff.

```
Bash: git -C ~/.origin add -A && \
      git -C ~/.origin -c user.name=Origin -c user.email=daemon@origin.local \
          commit --quiet -m "forget: <source_id>" 2>/dev/null || \
      (sleep 1 && git -C ~/.origin add -A && \
       git -C ~/.origin -c user.name=Origin -c user.email=daemon@origin.local \
           commit --quiet -m "forget: <source_id>" 2>/dev/null) || true
```

The retry handles index.lock races — the daemon may be writing to
`~/.origin/` at the same moment (auto-commit from captures). One-second
wait is enough for the daemon to release the lock.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…