CtrlK
BlogDocsLog inGet started
Tessl Logo

mem-search

This skill should be used when the user asks to "search memory", "what do you remember about X", "check claude-mem", "mem search", "find past observations", "what did we do last session", or wants prior-session context about a project, decision, file, or task. Searches the user's Claude-Mem (cmem.ai) memory.

74

Quality

91%

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

93%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, actionable, well-structured skill body: executable commands, a clear cheap-to-expensive search discipline, and a diagnostic recovery path. The only mild gap is that workflow validation checkpoints are implicit rather than explicit.

Suggestions

Make the confirm-hits checkpoint explicit in the Progressive search method (e.g. 'Only proceed to the narrow pass once step 1 surfaces a relevant title') to push workflow clarity toward 5.

No changes needed for conciseness, actionability, or progressive disclosure.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — "Search the user's persistent Claude-Mem memory on cmem.ai" plus a brief, domain-specific note on what memory stores; no generic concept explanation or padding, matching the level-5 anchor.

5 / 5

Actionability

Provides copy-paste-ready commands covering the common cases — `node "${CLAUDE_PLUGIN_ROOT}/scripts/cmem-hook.mjs" search "your query" --limit 20` and the `status` diagnostic — fully executable, matching the level-5 anchor.

5 / 5

Workflow Clarity

The 3-step Index → Narrow → Answer sequence is clear and the Diagnostics section gives an error-recovery path, but validation checkpoints are implicit (skim/confirm hits) rather than explicit validate-then-proceed steps, so it sits at level 4 rather than 5; the operation is read-only so the destructive-cap does not apply.

4 / 5

Progressive Disclosure

A self-contained skill under 50 lines with no in-bundle reference files, organized into well-signaled sections (How to search, Progressive search method, Diagnostics, Notes); the referenced cmem-hook.mjs is a plugin runtime script outside this bundle, so per the simple-skill note this earns a 5.

5 / 5

Total

19

/

20

Passed

Description

90%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, third-person description with explicit 'when' trigger guidance and rich natural trigger phrases; its only weak spot is specificity, since it names just one concrete action (search) rather than enumerating several.

Suggestions

Consider naming one or two more concrete actions (e.g. 'search and surface prior-session observations') to lift specificity from a single named action toward several.

No change needed for trigger terms, completeness, or distinctiveness — all are at the top anchor.

DimensionReasoningScore

Specificity

The description names the domain ("Searches the user's Claude-Mem (cmem.ai) memory") and one concrete action (search), but offers no further actions; not a level-4 'several specific actions' nor a level-2 minimal 'Processes PDF files' style.

3 / 5

Completeness

Explicitly answers both what ("Searches the user's Claude-Mem (cmem.ai) memory") and when ("This skill should be used when the user asks to...") with concrete trigger phrases, hitting the level-5 anchor; uses third-person voice so no voice penalty applies.

5 / 5

Trigger Term Quality

Quotes many natural phrases users would actually say — "search memory", "what do you remember about X", "check claude-mem", "mem search", "find past observations", "what did we do last session" — covering synonyms comprehensively, matching the level-5 anchor.

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche (Claude-Mem / cmem.ai memory search) with distinctive triggers ("mem search", "check claude-mem") unlikely to fire for unrelated skills, matching the level-5 anchor.

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
thedotmack/claude-mem
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.