mem0-cli

Mem0 CLI -- the command-line interface for mem0 memory operations. TRIGGER when: user mentions "mem0 cli", "mem0 command line", "@mem0/cli", "mem0-cli", "pip install mem0-cli", "npm install -g @mem0/cli", or is running mem0 commands in a terminal/shell (mem0 add, mem0 search, mem0 list, mem0 get, mem0 init, mem0 config, mem0 import). Also triggers when query includes CLI flags like --user-id, --output, --json, --agent, or describes bash/zsh/terminal/shell usage. DO NOT TRIGGER when: user asks about programmatic SDK integration in Python/TS code (use mem0 skill), or Vercel AI SDK provider (use mem0-vercel-ai-sdk skill).

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Quality

Content

80%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 well-organized, highly actionable CLI skill body that keeps the overview lean and pushes detail to three well-signaled reference files. The main weakness is the destructive delete-all workflow, which documents the command and cascade semantics but omits an explicit validation checkpoint before the batch deletion.

Suggestions

Add a verify-before-destroy checkpoint to the delete-all flow, e.g. 'Run `mem0 list --user-id alice` to confirm scope before `mem0 delete --all --user-id alice --force`' to introduce a feedback loop for the destructive batch operation.

Tighten the 'Node and Python Parity' section or merge it with the Install note that already states both packages install an identical `mem0` binary, removing the redundant re-statement.

Consider an explicit recovery note for the async processing delay (e.g. retry `mem0 search` after the 2-3s wait) to round out the add→search feedback loop.

Dimension	Reasoning	Score
Conciseness	Lean and largely assumes Claude's competence, but the 'Node and Python Parity' section re-states the identical-commands claim already made in Install, a minor redundancy that could be trimmed.	4 / 5
Actionability	Every operation has copy-paste executable commands (add, search, list, get, update, delete) plus a concrete JSON envelope example covering both success and error cases — fully actionable.	5 / 5
Workflow Clarity	The destructive batch operation 'mem0 delete --all --user-id alice --force' is documented but lacks a verify-before-delete feedback loop, triggering the rubric cap at 3 for destructive/batch operations without validation.	3 / 5
Progressive Disclosure	Clear overview with a References table pointing to three real one-level-deep files (command-reference.md, configuration.md, workflows.md), each verified to exist and clearly signaled by topic.	5 / 5
	Total	17 / 20 Passed

Description

100%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, well-structured description that concretely states capabilities, supplies abundant natural trigger terms, and explicitly marks both positive and negative trigger conditions to avoid conflicts with sibling Mem0 skills. No meaningful gaps relative to the rubric anchors.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete commands — 'mem0 add, mem0 search, mem0 list, mem0 get, mem0 init, mem0 config, mem0 import' — giving comprehensive coverage of concrete actions rather than vague abstractions.	5 / 5
Completeness	Explicitly answers both 'what' ('command-line interface for mem0 memory operations') and 'when' ('TRIGGER when: ...') with concrete trigger phrases, and adds a negative 'DO NOT TRIGGER when' boundary clause beyond the 5 anchor.	5 / 5
Trigger Term Quality	Comprehensive natural terms including synonyms and package identifiers ('mem0 cli', 'mem0 command line', '@mem0/cli', 'mem0-cli', install commands) plus CLI flags users would actually type (--user-id, --output, --json, --agent).	5 / 5
Distinctiveness Conflict Risk	Clear CLI niche with distinct triggers, and explicit conflict avoidance steering SDK/Vercel-AI-SDK requests to the sibling mem0 and mem0-vercel-ai-sdk skills, minimizing wrong-skill triggering.	5 / 5
	Total	20 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 2 suspicious	Warning

	Total	15 / 16 Passed

Repository: mem0ai/mem0
Path: skills/mem0-cli/SKILL.md
Commit: 39bc023

Reviewed: 3 days ago

Table of Contents

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.