status

Show whether Mem0 memory is working in this repository, covering configuration, capture state, pending flushes, and whether the Mem0 API key is valid. Use when the user asks whether memory is on, why a memory is missing, or anything looks broken.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

100%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, fully executable diagnostic skill that gives exact commands, specific reporting fields, and explicit error-case handling without padding. It is exemplary for a simple single-purpose skill.

Dimension	Reasoning	Score
Conciseness	The body is lean: two executable commands plus dense, actionable reporting guidance with no concept explanations Claude already knows; every clause, including the flush-count clarification, earns its place.	5 / 5
Actionability	It provides fully executable, copy-paste-ready commands with complete arguments and concrete error-handling instructions for the auth-failure case, including a remediation command.	5 / 5
Workflow Clarity	The run-both-then-report sequence is unambiguous, with an explicit recovery branch for authentication failures; the skill is read-only so the destructive-operation cap does not apply and the simple-skill exception holds.	5 / 5
Progressive Disclosure	Under 50 lines with no external references needed and a single clear header; per the simple-skill guidance this is well-organized enough to score at the top.	5 / 5
	Total	20 / 20 Passed

Description

82%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 focused, well-structured description that clearly states both capability and trigger conditions with low conflict risk. Its only real weakness is that it describes a single reporting action rather than multiple distinct concrete actions.

Suggestions

Tighten specificity by framing the facets as concrete actions (e.g., "Report capture state, check flush counts, and validate the Mem0 API key") rather than listing what the status covers.

Add a couple of natural trigger synonyms (e.g., "memory not working", "memories not saving") to broaden keyword coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain and one concrete action ("Show whether Mem0 memory is working") with several covered facets (configuration, capture state, flushes, API key), but it is fundamentally a single reporting action rather than a list of several distinct actions.	3 / 5
Completeness	It explicitly answers both what (show memory working state across listed facets) and when (concrete trigger phrases), matching the top anchor.	5 / 5
Trigger Term Quality	"Use when the user asks whether memory is on, why a memory is missing, or anything looks broken" supplies natural phrases users would actually say, though a few synonyms or variations are missing.	4 / 5
Distinctiveness Conflict Risk	It carves a clear Mem0-specific diagnostic niche with distinct triggers (memory on/missing/broken), keeping conflict risk with other skills minimal.	5 / 5
	Total	17 / 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/claude-code-plugin/skills/status/SKILL.md
Commit: 0df3e4b

Reviewed: 2 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.