CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

memory-recall

Search and recall relevant memories from past sessions via memsearch. Use when the user's question could benefit from historical context, past decisions, debugging notes, previous conversations, or project knowledge -- especially questions like 'what did I decide about X', 'why did we do Y', or 'have I seen this before'. Also use when you see `[memsearch] Recall available if needed` capability hints injected via SessionStart or UserPromptSubmit. Typical flow: search for 3-5 chunks, expand the most relevant, optionally deep-drill into original transcripts via the anchor format. Skip when the question is purely about current code state (use Read/Grep), ephemeral (today's task only), or the user has explicitly asked to ignore memory.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

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.

A tight, highly executable skill body: every step carries a concrete command, the workflow is well-sequenced with evaluation checkpoints and error-recovery branches, and there is no padding or beginner-level explanation. The only flaw is slight redundancy in the fallback/path-resolution notes.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence (no concept explanations, direct commands), but has minor trimmable redundancy: the "If `memsearch` is not found, try `uvx memsearch` instead" fallback appears twice (Steps 1 and 4), and the paragraph "The path above is relative to this skill's directory. If the host displays the placeholder literally, resolve..." re-explains path resolution already implied by the `${CLAUDE_SKILL_DIR}` variable. This fits the score-4 anchor 'minor instances of over-explanation that could be trimmed' rather than score 5's 'every token earns its place'.

4 / 5

Actionability

Fully executable, copy-paste-ready commands with all flags specified: `memsearch search "<query>" --top-k 5 --json-output --default-collection <collection>`, `memsearch expand <chunk_hash> --default-collection ...`, `memsearch transcript <jsonl_path> --turn <uuid> --context 3`, plus the `derive-collection.sh` fallback and the `uvx memsearch` alternative. Matches the score-5 anchor 'copy-paste ready code or commands' — score 4's 'minor gaps' doesn't apply since every step has a concrete command.

5 / 5

Workflow Clarity

A clear 5-step sequence (Search → Evaluate → Expand → Deep drill → Return) with an explicit selection checkpoint ("Skip chunks that are clearly irrelevant or too generic") and error-recovery feedback loops for two failure modes ("If `memsearch` is not found, try `uvx memsearch`"; "If `memsearch transcript` reports an unrecognized transcript format... read the referenced file directly"). This matches the score-5 anchor's 'explicit validation steps; feedback loops for error recovery'; the operations are read-only so no destructive/batch cap applies.

5 / 5

Progressive Disclosure

The skill is a ~50-line self-contained instruction sheet with well-organized sections (Project Collection, Steps, When unsure, Output Format) and no unnecessary inline bulk — the simple-skill case where a single file scores 5. Its one external reference (`../../scripts/derive-collection.sh`) is clearly signaled as a conditional fallback with resolution guidance; no nested reference chains exist.

5 / 5

Total

19

/

20

Passed

Description

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

An exemplary description: concrete actions, natural trigger phrases with example user utterances, explicit use/skip conditions, and clear disambiguation from built-in tools. All four dimensions sit at the top anchor with no padding or over-claims.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Search and recall relevant memories from past sessions via memsearch", "search for 3-5 chunks, expand the most relevant, optionally deep-drill into original transcripts via the anchor format" — giving comprehensive coverage of the skill's capability surface. It matches the score-5 anchor (multiple specific concrete actions) and exceeds score 4, which expects only 'several' actions with coverage gaps.

5 / 5

Completeness

It explicitly answers both 'what' (search/expand/deep-drill via memsearch) and 'when' ("Use when the user's question could benefit from..."), and goes further with explicit skip conditions ("Skip when the question is purely about current code state (use Read/Grep), ephemeral... or the user has explicitly asked to ignore memory"). Concrete trigger phrases plus explicit negative guidance place it clearly at the score-5 anchor, above score 4's 'when could be more explicit'.

5 / 5

Trigger Term Quality

Natural trigger phrases are comprehensive: "historical context, past decisions, debugging notes, previous conversations, or project knowledge" plus example utterances like "'what did I decide about X', 'why did we do Y', 'have I seen this before" and an explicit capability-hint trigger ("[memsearch] Recall available if needed"). These are exactly the phrases a user would naturally say; not merely technical jargon, so it fits the score-5 anchor rather than score 4's 'a few natural terms missing'.

5 / 5

Distinctiveness Conflict Risk

It carves out a clear niche (memsearch memory recall) with distinct triggers and explicit disambiguation from plain code reading ("purely about current code state (use Read/Grep)"). Minimal conflict risk with other skills; matches the score-5 anchor 'clear niche with distinct triggers' rather than score 4's 'minor overlap risk with closely related skills'.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

zilliztech/memsearch

Path

plugins/claude-code/skills/memory-recall/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.