CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

forget

Deletes memories by search query or memory ID with confirmation before removal. Use when removing outdated information, incorrect memories, sensitive data, or cleaning up after experiments.

70

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

93%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An excellent, lean instruction-only body: every step is executable with exact tool calls, prompts, and output formats, and the destructive nature of the operation is guarded by an explicit confirmation checkpoint plus failure reporting. The only gap is the absence of a retry/recovery loop when a deletion fails. Suggestions are omitted because all dimensions scored at or near the top of the scale.

DimensionReasoningScore

Conciseness

The ~50-line body is entirely operational — exact prompts, tool invocations, and output formats — with no padding and no explanation of concepts Claude already knows; every token earns its place.

5 / 5

Actionability

Fully concrete instruction-only guidance: exact `mem0_memory` tool calls with `action="search"`/`"delete"`, verbatim confirmation prompts, and copy-paste-ready display templates covering both the query and memory-ID paths.

5 / 5

Workflow Clarity

A clearly sequenced 5-step workflow with an explicit validation checkpoint for the destructive operation ('Never delete without confirmation') and failure reporting in Step 5; however, there is no retry/recovery loop after a failed deletion, leaving a minor validation gap versus anchor 5.

4 / 5

Progressive Disclosure

Under 50 lines, single task, no external references needed, and well-organized sectioned steps — the rubric's simple-skill exception applies, so well-organized sections alone score 5.

5 / 5

Total

19

/

20

Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that explicitly covers what the skill does and when to use it, with concrete and naturally phrased trigger conditions in proper third-person voice. Its main weakness is that the capability description is somewhat narrow — a single delete operation with two lookup modes — and it omits common synonyms like 'forget' or 'erase'.

Suggestions

Add natural trigger synonyms such as 'forget' or 'erase memories' to broaden keyword coverage for users who phrase the request differently.

Briefly mention what the user sees during the process (e.g., matching memories are listed for selection before deletion) to make the capability description more comprehensive.

DimensionReasoningScore

Specificity

Names the domain (memories) with concrete actions ('Deletes memories by search query or memory ID', 'with confirmation before removal'), but this is one operation with two selection modes rather than the several distinct actions of anchor 4, and coverage is not comprehensive.

3 / 5

Completeness

Clearly answers both 'what' ('Deletes memories by search query or memory ID with confirmation before removal') and 'when' ('Use when removing outdated information, incorrect memories, sensitive data, or cleaning up after experiments') with concrete trigger phrases in third-person voice.

5 / 5

Trigger Term Quality

Good natural trigger phrases ('removing outdated information', 'incorrect memories', 'sensitive data', 'cleaning up after experiments') that users would actually say, but common synonyms like 'forget' or 'erase' are missing, so it does not reach anchor 5's comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

Clear niche (memory deletion in Mem0) with distinct, specific triggers; only minor overlap risk with closely related sibling memory skills (e.g., save/search memory), so anchor 4 fits better than 5.

4 / 5

Total

16

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

mem0ai/mem0

Path

integrations/pi-agent-plugin/skills/forget/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.