CtrlK
BlogDocsLog inGet started
Tessl Logo

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).

75

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

87%Weight 40%Scale 1-3

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

A well-structured, actionable CLI reference that keeps the body lean and pushes deep detail into appropriately organized reference files. The only gap is the absence of an explicit verification checkpoint around the destructive batch delete operation.

Suggestions

Add a pre-flight verification step for destructive batch operations, e.g. run 'mem0 list --user-id alice' to confirm scope before 'mem0 delete --all --user-id alice --force'.

Show an explicit confirm/recover loop for the delete workflow (verify count -> delete -> re-list to confirm empty) to satisfy the validation-checkpoint expectation for destructive ops.

Consider a one-line note that --force bypasses confirmation so the verification step is framed as the safety gate.

DimensionReasoningScore

Conciseness

The body is lean and command/example-dense with no explanation of concepts Claude already knows; prose is tight and every section earns its place, matching the lean-and-efficient anchor.

3 / 3

Actionability

Provides fully executable, copy-paste-ready commands (install, init, add/search/list/get/update/delete) plus a concrete JSON envelope example, matching the fully-executable anchor.

3 / 3

Workflow Clarity

The agent init/claim flow is sequenced with idempotent recovery (mem0 identify), but the batch destructive 'mem0 delete --all --user-id alice --force' has no explicit verification checkpoint; per the rubric this caps destructive/batch workflows at 2 rather than 3.

2 / 3

Progressive Disclosure

SKILL.md is a concise overview with a clearly signaled References table pointing to three real, one-level-deep files (command-reference.md, configuration.md, workflows.md, all verified present), matching the clear-overview-with-one-level-references anchor.

3 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

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, third-person description that concretely states the skill's purpose, provides rich and natural trigger terms, and explicitly disambiguates from sibling skills. It cleanly answers both what the skill does and when to use it.

DimensionReasoningScore

Specificity

Explicitly names the domain ('command-line interface for mem0 memory operations') and enumerates concrete operations ('mem0 add, mem0 search, mem0 list, mem0 get, mem0 init, mem0 config, mem0 import'), matching the anchor for multiple specific concrete actions.

3 / 3

Completeness

Explicitly answers both what ('command-line interface for mem0 memory operations') and when (a detailed 'TRIGGER when:' clause plus a 'DO NOT TRIGGER when:' exclusion), matching the anchor for clear what AND when with explicit triggers.

3 / 3

Trigger Term Quality

Broad natural-term coverage users would actually say ('mem0 cli', '@mem0/cli', 'pip install mem0-cli', command names, CLI flags like --user-id/--json/--agent, and 'bash/zsh/terminal/shell usage'), matching the good-coverage anchor.

3 / 3

Distinctiveness Conflict Risk

Has an explicit 'DO NOT TRIGGER when:' clause redirecting SDK/Vercel cases to the mem0 and mem0-vercel-ai-sdk skills, giving it a clear CLI niche unlikely to conflict.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 suspicious

Warning

Total

15

/

16

Passed

Repository
mem0ai/mem0
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.