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.

70

Quality

86%

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

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

The body is a well-structured progressive-recall guide: three tools sequenced by depth, a decision table, tips, and a fallback section. It is concise and actionable for an instruction-only skill, with only minor validation-loop and repetition gaps.

DimensionReasoningScore

Conciseness

The body is lean with tight per-tool returns/input/use-for bullets and no concept over-explanation, though the decision table and tips mildly restate tool chains already implied. It is not 5 because of that minor repetition, and not 3 because it is genuinely efficient throughout.

4 / 5

Actionability

Concrete instruction-only guidance with exact input fields (chunk_hash, transcript_path) and the anchor format `<!-- session:UUID transcript:PATH -->` plus a fallback for unfamiliar anchor formats. It is not 5 because there are no copy-paste commands (the rubric exempts instruction-only skills from requiring code), and not 3 because the guidance is concrete rather than pseudocode.

4 / 5

Workflow Clarity

A clear progressive sequence (search -> get -> transcript) with a decision-guide table mapping intent to tool chain and a light error-recovery hint ('If memory_search returns no results, try rephrasing'). It is not 5 because there is no explicit validate->fix->retry loop, and not 3 because the sequence and decision mapping are clear.

4 / 5

Progressive Disclosure

No bundle files exist; the skill is under 50 lines and well-organized into clear sections (Tools, Decision guide, Tips, When unsure), qualifying for the simple-skill exception. It is not 4 because the structure is clean and self-contained with no organization gaps.

5 / 5

Total

17

/

20

Passed

Description

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

The description is well-crafted: it gives concrete actions, rich natural trigger phrases, explicit when/skip-when guidance, and clear distinctiveness from code-state tools. It is concise yet comprehensive and uses appropriate third-person voice.

DimensionReasoningScore

Specificity

Names several concrete actions (search, expand the most relevant, deep-drill into original transcripts) with minor coverage gaps rather than a fully comprehensive enumeration. It is not 5 because not all capabilities are listed, and not 3 because more than 1-2 actions are specified.

4 / 5

Completeness

Explicitly answers both what ('Search and recall relevant memories from past sessions via memsearch') and when ('Use when...', 'Also use when...', 'Skip when...') with concrete trigger phrases. It is not 4 because the when clause is explicit and specific rather than merely adequate.

5 / 5

Trigger Term Quality

Provides comprehensive natural trigger phrases users would actually say, e.g. 'what did I decide about X', 'why did we do Y', 'have I seen this before', plus synonyms (historical context, past decisions, debugging notes, previous conversations). It is not 4 because coverage is genuinely comprehensive rather than missing a few natural terms.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear memory-recall niche with distinct triggers and explicitly disambiguates from current-code-state work via the 'Skip when... (use Read/Grep)' clause, minimizing conflict risk. It is not 4 because the explicit skip-when disambiguation places it firmly in a distinct niche.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

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.