Tessl • The management layer for AI agent skills

SkillPublic

forget

Delete the Mem0 memories stored for this repository and this user. Use when the user asks to forget, clear, wipe, or delete memories.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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.

A tight, actionable, well-sequenced destructive-operation skill that correctly front-loads user confirmation and provides a copy-paste command with option variants. Its only gap is the absence of an explicit error-recovery feedback loop, which keeps workflow clarity just below the top anchor.

Suggestions

Add a brief 'if the command reports nothing was deleted or errors, check that --remote/--harness match the configured backend and retry' feedback loop to push workflow clarity to 5.

Clarify what the harness value should be for non-Cursor environments, since the example hardcodes --harness "cursor".

State explicitly that confirmation must be re-obtained in the current conversation before each --yes invocation, not just once.

Dimension	Reasoning	Score
Conciseness	The body is lean (~17 lines), assumes Claude's competence, and every sentence earns its place — context about shared project memory is load-bearing for the confirmation step, not padding. No concepts Claude already knows are re-explained. Matches anchor 5; not 4 because there are no real instances of over-explanation to trim.	5 / 5
Actionability	Provides a fully copy-paste-ready command (`python3 "${CURSOR_PLUGIN_ROOT}/core/memory_cli.py" --harness "cursor" forget --remote --yes`) and concrete option flags covering remote, local, and project-memory cases. Matches anchor 5 (fully executable, specific examples cover common cases); not 4 because no gaps remain in the common cases.	5 / 5
Workflow Clarity	Clear sequence: inform user what will be deleted → obtain confirmation → run command → report output, with an explicit confirmation checkpoint before passing --yes (satisfying the destructive-op validation requirement). Not 5 because there is no error-recovery feedback loop (validate → fix → retry) or checklist, only a report step; not 3 because the key validation checkpoint is explicitly present.	4 / 5
Progressive Disclosure	Under 50 lines, single-purpose, no external references needed, with well-organized sections (context, command block, options, reporting). Per the rubric's simple-skkill guidance this matches anchor 5; no bundle files exist to require deeper navigation.	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, concise description that clearly states both capability and explicit trigger conditions with good synonym coverage. Its only weakness is limited action breadth (single deletion action) and slight overlap risk with general memory skills.

Suggestions

Broaden the stated action coverage if applicable (e.g., mention local-only clearing of evidence log / pending queue) to lift specificity above a single action.

Add a distinguishing qualifier to the trigger clause (e.g., 'Mem0 memories' rather than bare 'memories') to reduce overlap with other memory-management skills.

Consider adding 'erase' or 'remove' as synonyms to round out trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Mem0 memories stored for this repository and this user') and one concrete action ('Delete'), but offers no breadth of actions beyond deletion. Matches anchor 3 (domain + 1-2 concrete actions, not comprehensive); not 4 because there is only a single action, not 'several specific actions'.	3 / 5
Completeness	Explicitly answers both what ('Delete the Mem0 memories stored for this repository and this user') and when ('Use when the user asks to forget, clear, wipe, or delete memories') with concrete trigger phrases. Matches anchor 5; voice is third person with no penalty.	5 / 5
Trigger Term Quality	'Use when the user asks to forget, clear, wipe, or delete memories' supplies four natural synonyms users would say. Not 5 because additional natural variants (erase, remove, reset) are absent and file-extension coverage is inapplicable here; not 3 because coverage is already good rather than merely 'some'.	4 / 5
Distinctiveness Conflict Risk	The 'Mem0 memories for this repository and this user' niche is fairly distinct, but the verbs 'forget/clear/wipe/delete memories' could overlap with other memory-management skills. Not 5 due to minor overlap risk with closely related memory skills; not 3 because the Mem0 + repo/user scoping makes it more specific than 'somewhat specific'.	4 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

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/cursor-plugin/skills/forget/SKILL.md
Revision: 2c81af3

Reviewed: 27 days ago

Discovery Implementation Validation

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.

forget

Table of Contents

Is this your skill?