/forget
Delete a Wenlan memory by exact id from Codex. Destructive and confirmation gated. Invoked as /forget <source_id>.
$ npx -y skills add 7xuanlu/wenlan --skill forget --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/forget
Context preview
The summary Claude sees to decide when to auto-load this skill.
Delete a Wenlan memory by exact id from Codex. Destructive and confirmation gated. Invoked as /forget <source_id>.
SKILL.md
forget.SKILL.mdname: forget
description: >
Delete a Wenlan memory by exact id from Codex. Destructive and confirmation
gated. Invoked as /forget <source_id>.
argument-hint: "<source_id>"
allowed-tools: ["Bash", "mcp__wenlan__forget", "mcp__wenlan__recall"]
user-invocable: true
/forget
Delete one memory by exact `source_id`.
Safety
This cannot be undone by Wenlan. Prefer `/capture` with a corrected memory when history should be preserved.
Always confirm with the user before calling forget, unless the same user message already includes an exact id and an unambiguous delete instruction.
If the id is missing, use `mcp__wenlan__recall` to find candidates or ask the user for the exact id. The confirmation reply must include the action and id:
delete <id>
A bare id is not confirmation.
Call
After confirmation, call:
mcp__wenlan__forget(memory_id="<source_id>")
Delete only one memory per tool call. For bulk cleanup, use `/curate captures` so each item has its own decision.
Auto-commit `~/.wenlan`
After a successful delete, snapshot any Markdown projection changes. Best effort only:
git -C ~/.wenlan add -A && \
git -C ~/.wenlan -c user.name=Wenlan -c user.email=daemon@wenlan.local \
commit --quiet -m "forget: <source_id>" 2>/dev/null || \
(sleep 1 && git -C ~/.wenlan add -A && \
git -C ~/.wenlan -c user.name=Wenlan -c user.email=daemon@wenlan.local \
commit --quiet -m "forget: <source_id>" 2>/dev/null) || trueDo not fail the delete if this commit fails.
When to use
- User says to forget or delete a specific memory and gives the id.
- User confirms `delete <id>` after recall found the matching memory.
When not to use
- Corrections where history matters: capture a superseding memory.
- Page rebuilds: use `/distill rebuild <page-id>`.
Read more
name: forget description: > Delete a Wenlan memory by exact id from Codex. Destructive and confirmation gated. Invoked as /forget <source_id>. argument-hint: "<source_id>" allowed-tools: ["Bash", "mcp__wenlan__forget", "mcp__wenlan__recall"] user-invocable: true
/forget
Delete one memory by exact `source_id`.
Safety
This cannot be undone by Wenlan. Prefer `/capture` with a corrected memory when history should be preserved.
Always confirm with the user before calling forget, unless the same user message already includes an exact id and an unambiguous delete instruction.
If the id is missing, use `mcp__wenlan__recall` to find candidates or ask the user for the exact id. The confirmation reply must include the action and id:
delete <id>
A bare id is not confirmation.
Call
After confirmation, call:
mcp__wenlan__forget(memory_id="<source_id>")
Delete only one memory per tool call. For bulk cleanup, use `/curate captures` so each item has its own decision.
Auto-commit `~/.wenlan`
After a successful delete, snapshot any Markdown projection changes. Best effort only:
git -C ~/.wenlan add -A && \
git -C ~/.wenlan -c user.name=Wenlan -c user.email=daemon@wenlan.local \
commit --quiet -m "forget: <source_id>" 2>/dev/null || \
(sleep 1 && git -C ~/.wenlan add -A && \
git -C ~/.wenlan -c user.name=Wenlan -c user.email=daemon@wenlan.local \
commit --quiet -m "forget: <source_id>" 2>/dev/null) || trueDo not fail the delete if this commit fails.
When to use
- User says to forget or delete a specific memory and gives the id.
- User confirms `delete <id>` after recall found the matching memory.
When not to use
- Corrections where history matters: capture a superseding memory.
- Page rebuilds: use `/distill rebuild <page-id>`.
Wenlan is a knowledge base for the AI-native age. Your AI agents capture what they learn, Wenlan keeps it current and distills it into source-cited wiki pages you can trust
Other skills on wenlan.
- /prove
Per-surface verification loops for wenlan — daemon, cli, mcp, plugin, suite strength (mutation), behavior trace, weekly sweep. Routes to scripts; every check records evidence via attest. Deeper than the built-in verify skill — use prove for mutation audits, behavior tracing, and
Open skill - /run-wenlan
Build, launch, and stop the wenlan daemon (wenlan-server) for local dev and verification. Use when asked to run or restart the daemon, or before driving any surface (HTTP, CLI, MCP) against a live instance.
Open skill - /verify
Drive/evidence recipe for verifying wenlan changes at their real surfaces (daemon HTTP, CLI, MCP stdio). The handle file the built-in verify protocol expects; launch primitives live in the run-wenlan skill, deeper machinery (mutation audit, behavior trace, weekly sweep) in the
Open skill - /brief
Read the current Space-owned project Brief from Wenlan for Codex. With an optional topic, appends separately labeled related context from the same Space. Invoked as /brief [topic] when resuming work or asking to catch up.
Open skill - /capture
Save a durable memory to Wenlan from Codex. Use proactively when the user states a preference, makes a decision, corrects you, or shares a durable fact. Invoked as /capture <content>.
Open skill - /curate
Review pending Wenlan captures, revisions, or daemon refinements from Codex. Use for explicit audit walks after /brief or /handoff surfaces pending work. Invoked as /curate captures, /curate revisions, or /curate refinements.
Open skill

