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

90%

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

92%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.

An exemplary lean, single-purpose skill body: verbatim commands, precise field semantics, and an explicit auth-failure handling rule that prevents a misleading report. The only residual gap is the unguarded ${CURSOR_PLUGIN_ROOT} dependency and the absence of guidance for non-auth failure modes.

DimensionReasoningScore

Conciseness

The ~20-line body is lean with zero padding: two commands, a field-by-field summary instruction, and only non-obvious knowledge ('`flushes` is the number of completed flushes, not a pending count'; 'Never report an auth failure as "no memories found"'). Nothing explains concepts Claude already knows, matching anchor 5's 'every token earns its place'.

5 / 5

Actionability

Two copy-paste-ready bash commands are given verbatim, plus concrete reporting instructions and an explicit remediation ('reinstalling with `--config api_key=...`'). It falls short of anchor 5 only because the commands depend on `${CURSOR_PLUGIN_ROOT}` being set (no fallback given) and there is no sample of the JSON output or guidance for non-auth failure modes (e.g., command not found, network error) — minor gaps per anchor 4.

4 / 5

Workflow Clarity

For this simple single-purpose skill, the sequence is unambiguous: run both commands, report the combined result, with an explicit error-handling branch ('If doctor reports an authentication failure (401 / invalid key), say clearly that the Mem0 API key is invalid... Never report an auth failure as "no memories found"'). This is a clear decision checkpoint on the one real failure mode, meeting the simple-skill exception for a 5; the operations are read-only so no destructive-operation cap applies.

5 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, and requires no external reference files — none exist in the bundle (no references/, scripts/, or assets/ directories), and the body correctly inlines everything needed. Per the rubric's guidance for short skills with no need for external references, the clean single-heading structure merits a 5; there are no buried or nested references to penalize.

5 / 5

Total

19

/

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 with a clear 'what', an explicit and well-phrased 'Use when' clause, and concrete coverage areas. Its only weaknesses are minor: the trailing 'anything looks broken' trigger is broad enough to risk mis-triggering, and a few natural keyword variants are absent.

DimensionReasoningScore

Specificity

The description names a concrete capability ('Show whether Mem0 memory is working in this repository') and enumerates specific coverage areas: 'configuration, capture state, pending flushes, and whether the Mem0 API key is valid' — several specific items with only minor gaps (it does not mention running diagnostics explicitly). It sits between anchor 3 (only 1-2 concrete actions) and anchor 5 (comprehensive action list), matching anchor 4's 'several specific actions; minor gaps'.

4 / 5

Completeness

It 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'). This mirrors the anchor 5 example's structure of a concrete 'what' followed by an explicit 'Use when' with multiple concrete trigger phrases; anchor 4 would require a less explicit 'when' clause, which does not apply.

5 / 5

Trigger Term Quality

Natural user phrasings are present: 'whether memory is on', 'why a memory is missing', 'anything looks broken', plus domain terms 'Mem0', 'API key'. Good keyword coverage, but a few natural variations users might say are missing (e.g., 'is memory enabled', 'memory not saving', 'recall not working'), so it matches anchor 4 ('good keyword coverage; a few natural terms missing') rather than anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The 'Mem0 memory' scope gives it a clear niche with distinct triggers, but the catch-all phrase 'or anything looks broken' is broad and could fire for non-memory breakage, creating minor overlap risk with general debugging skills. This places it at anchor 4 ('mostly distinct; minor overlap risk') 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/cursor-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.