CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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.

Excellent single-purpose skill body: exact executable commands, precise reporting instructions tied to actual JSON fields, and an explicit auth-failure guard that prevents misreporting, including remediation. Lean, actionable, and unambiguous.

DimensionReasoningScore

Conciseness

Roughly 20 lean lines with zero padding: exact commands, a field-by-field reporting list, a semantics clarification ('flushes is the number of completed flushes, not a pending count'), and one edge-case guard. Every token earns its place and nothing explains concepts Claude already knows — anchor 5.

5 / 5

Actionability

Two copy-paste-ready commands with full flags and env var ('python3 "${KIMI_PLUGIN_ROOT}/core/memory_cli.py" --harness "kimi" status --json') plus concrete interpretation rules covering the common failure case (401 / invalid key with explicit remediation '--config api_key=...'). Fully executable — anchor 5.

5 / 5

Workflow Clarity

A single composite action ('Run both commands and report the combined result') that is unambiguous, with an explicit conditional branch for the failure case ('If doctor reports an authentication failure (401 / invalid key), say clearly... Never report an auth failure as "no memories found"'). This is a read-only status skill, so the destructive/batch validation cap does not apply, and the simple-skill exception for a single unambiguous action holds — anchor 5.

5 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references (none of references/, scripts/, or assets/ exist), and is well organized: heading, command block, then summarization and edge-case rules. Per the simple-skill exception, this earns anchor 5.

5 / 5

Total

20

/

20

Passed

Description

83%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: concrete domain and covered fields, an explicit 'Use when...' clause with natural trigger phrases, and a clear niche. The only weaknesses are minor — the unqualified 'anything looks broken' trigger and missing a few natural keyword variations.

Suggestions

Qualify the last trigger to keep it memory-scoped, e.g. 'or the memory system looks broken', so it does not fire on unrelated broken-state queries.

Add one or two natural keyword variations users would say (e.g. 'memory not working' or 'is memory enabled') to strengthen trigger coverage.

Align the description's 'pending flushes' with the body's clarification that 'flushes' counts completed flushes, avoiding a mismatch in what is reported.

DimensionReasoningScore

Specificity

Names the domain ('Mem0 memory is working in this repository') and lists several concrete covered items ('configuration, capture state, pending flushes, and whether the Mem0 API key is valid'), but it is a single show-status action enumerating coverage rather than multiple distinct actions, and omits some reported fields (doctor checks, event/retrieval counts). This fits anchor 4 ('several specific actions; minor gaps in coverage') better than anchor 5's 'multiple specific concrete actions; comprehensive coverage'.

4 / 5

Completeness

Explicitly answers both: what ('Show whether Mem0 memory is working in this repository, covering configuration, capture state, pending flushes, and whether the Mem0 API key is valid') and when ('Use when the user asks whether memory is on, why a memory is missing, or anything looks broken') with concrete trigger phrases. This matches anchor 5 exactly; anchor 4 would require the 'when' to be less explicit.

5 / 5

Trigger Term Quality

Includes natural user phrasings ('whether memory is on', 'why a memory is missing', 'anything looks broken') that a user would plausibly say. It sits at anchor 4 rather than 5 because common variations like 'memory not working', 'is memory enabled', or 'debug memory' are absent.

4 / 5

Distinctiveness Conflict Risk

The Mem0-specific niche is clear, but the final trigger 'or anything looks broken' is not memory-qualified and could match broad broken-state queries about unrelated things. Minor overlap risk with generic debugging/status skills places it at anchor 4 rather than anchor 5's 'minimal conflict risk'.

4 / 5

Total

17

/

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/kimi-plugin/skills/status/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.