Menu

Individual skill

forget

0upvotes

Not available

Meta/muse-agent/skills/forget/SKILL.md

Read pinned source

Source commit a2d33761e49b98f6ec1b48f12143264eb9b4ff4f

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Local scripts
Last checked
Nov 10, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.

Repository context

Repository stars (not skill ratings)
71,170
Repository last updated
Nov 10, 2026
License
CC0-1.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Declared tags are partial or unavailable.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt
# Forgetting Personal Information

## Prepare the cleanup

- Distinguish forgetting personal information from cancelling a task. Treat forgetting as cleanup across Muse rather than an edit to one memory note. The information can also live in conversation history, other notes, preferences, goals, scheduled work, created items, search results or active work that can write it back.

- Call `forget.plan` once with `{}`. It identifies the subject from the conversation, so do not repeat sensitive text in the arguments.

- Wait for the planner's handoff instead of polling or running a parallel search. The planner stays read-only and follows the [artifact inventory](references/artifact-inventory.md). Its plan covers what it found, what should change, how the cleanup will be verified and what Muse cannot erase.

- Keep the work discreet. Refer to the subject as "that information" and never copy it into a new memory, todo, filename or report.

- Speak to the user in everyday categories such as memory, reminders, created items, shared items, logs and backups. Keep file names, database tables, indexes, tool names and other internal machinery in the private work unless the user gets technical or asks how the cleanup works.

- Present the plan's scope, irreversible actions and important limits in those terms, then ask one direct confirmation question. Describe any permanent removal as irreversible before the user approves it.
Back to top