CtrlK
BlogDocsLog inGet started
Tessl Logo

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] Memory available` 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.

77

Quality

96%

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, highly actionable retrieval skill with concrete executable commands, a clearly sequenced workflow, and an evaluation checkpoint. The only minor gap is the absence of an explicit validation feedback loop, though the read-only nature of the task makes this a small concern.

DimensionReasoningScore

Conciseness

Lean and efficient throughout — assumes Claude's competence, never explains what memory or memsearch is, and every section delivers concrete commands or guidance with no padding.

5 / 5

Actionability

Fully executable, copy-paste-ready commands with specific flags ('memsearch search "<query>" --top-k 5 --json-output --collection ...', 'memsearch expand <chunk_hash>', 'python3 .../parse-transcript.py <session_id> --turn <turn_id> --context 3') plus a fallback ('uvx memsearch').

5 / 5

Workflow Clarity

Five steps are clearly sequenced (Search → Evaluate → Expand → Deep drill → Return) with an Evaluate checkpoint and conditional branching, but there is no explicit validate-and-retry feedback loop, which keeps it just below the top anchor.

4 / 5

Progressive Disclosure

A self-contained skill under 50 lines with well-organized sections (Project Collection, Your Task, Steps, When unsure, Output Format) and no need for external bundle references, meeting the simple-skill exception for a top score.

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 excellent description that concretely states capabilities, provides natural trigger phrases users would actually say, and explicitly covers both what and when with disambiguating skip guidance. Third-person voice is used throughout with no over-claims.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — 'Search and recall relevant memories', 'search for 3-5 chunks, expand the most relevant, optionally deep-drill into original transcripts via the anchor format' — giving comprehensive coverage of the workflow.

5 / 5

Completeness

Clearly answers both what ('Search and recall relevant memories from past sessions via memsearch' plus a typical flow) and when ('Use when the user's question could benefit from historical context...') with concrete trigger phrases and explicit skip guidance.

5 / 5

Trigger Term Quality

Comprehensive natural trigger terms and synonyms users would actually say: 'historical context, past decisions, debugging notes, previous conversations, project knowledge' plus example phrases like 'what did I decide about X' and 'have I seen this before'.

5 / 5

Distinctiveness Conflict Risk

Clear niche (memory recall via memsearch) with distinct triggers and an explicit 'Skip when the question is purely about current code state (use Read/Grep)' clause that minimizes conflict risk with adjacent skills.

5 / 5

Total

20

/

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
zilliztech/memsearch
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.