CtrlK
BlogDocsLog inGet started
Tessl Logo

mem0-status

Diagnoses mem0 connectivity, API key validity, and memory read/write functionality. Use when memory operations fail, searches return empty, add_memory errors occur, or to verify the plugin is working correctly.

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 highly actionable, well-sequenced diagnostic skill with executable commands, explicit per-check validation, and recovery guidance. Its main weaknesses are a few verbose rationale passages and a large inlined extended-mode section that would benefit from extraction into a separate file.

Suggestions

Tighten the prose rationale in Check 2 and Check 6 to the essential one-liner; the pitfall and gate logic are already conveyed by the commands and PASS/WARN lines.

Move the 'Extended mode: Memory Quality Analysis' section (~60 lines) into a separate reference file (e.g. references/quality-analysis.md) and keep only the entry point and flag description in SKILL.md.

Replace remaining angle-bracket placeholders like <active_user_id> with a brief inline note pointing to the Check 2/3 resolved values, so each snippet is self-contained.

DimensionReasoningScore

Conciseness

Dense and operational with concrete commands throughout, but a few rationale passages (e.g. Check 2's explanation of why not to re-shell git, Check 6's gate notes) could be trimmed without losing clarity.

4 / 5

Actionability

Copy-paste-ready bash snippets and exact tool-call parameters with precise filter structures cover the common diagnostic cases fully.

5 / 5

Workflow Clarity

Sequenced as 'run ALL checks, then summarize' with explicit PASS/FAIL/WARN validation per check and a feedback loop in Check 4 (write → get_event_status → delete probe); a Troubleshooting section is mandated on failure.

5 / 5

Progressive Disclosure

Well-organized into clearly headed sections with no nested references, but at ~193 lines the substantial inlined --deep quality analysis could be split into a separate reference file rather than kept inline.

4 / 5

Total

18

/

20

Passed

Description

87%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, specific description that clearly states the skill's diagnostic purpose and provides concrete trigger phrases tied to real mem0 failure modes. It is tightly scoped with minimal conflict risk; the only minor gap is that the listed actions don't preview every check the body performs.

DimensionReasoningScore

Specificity

Lists several concrete diagnostic actions — 'mem0 connectivity, API key validity, and memory read/write functionality' — with only minor gaps (it omits identity/session/auto-dream checks that the body covers).

4 / 5

Completeness

Explicitly answers both 'what' (diagnoses connectivity, API key validity, read/write) and 'when' with a concrete 'Use when...' clause enumerating specific failure scenarios.

5 / 5

Trigger Term Quality

Natural trigger phrases like 'memory operations fail', 'searches return empty', and 'add_memory errors occur' give good coverage, though a few synonyms (e.g. 'memory not saving') are missing.

4 / 5

Distinctiveness Conflict Risk

Scoped tightly to the mem0 plugin with mem0-specific triggers, giving it a clear niche and minimal overlap risk with other skills.

5 / 5

Total

18

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.