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.

76

Quality

96%

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

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, actionable skill body that teaches a three-tool progressive workflow with an intent-to-tool-chain decision table and error-recovery guidance. The only weakness is mild redundancy across the tool sections, the decision table, and the Tips list, which could be consolidated to save tokens.

DimensionReasoningScore

Conciseness

The body is lean and table-driven with no explanations of known concepts, but the tool headers, Decision guide table, and Tips section redundantly restate the same chaining guidance, and 'When unsure what to search' could be tightened.

4 / 5

Actionability

Concrete, fully chained instruction-only guidance: exact inputs (chunk_hash, transcript_path), expected returns, the decision table mapping user intents to tool chains, and fallbacks (rephrase keywords, read referenced files directly for unfamiliar anchor formats).

5 / 5

Workflow Clarity

The progressive search -> get -> transcript sequence is unambiguous, with an explicit recovery loop ('If memory_search returns no results, try rephrasing') and a fallback for unfamiliar anchor formats; no destructive or batch operations, so no validation cap applies.

5 / 5

Progressive Disclosure

Under 50 lines, no bundle files, and no need for external references; the simple-skill guideline applies and the body is well organized into Tools, Decision guide, Tips, and a fallback section.

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 capabilities, natural trigger phrases with example user questions, an explicit use/skip boundary, and a distinctive system-hint trigger. It is somewhat long, but every clause carries trigger or capability information rather than padding.

DimensionReasoningScore

Specificity

Names multiple 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') with parameters, comprehensively covering the skill's behavior.

5 / 5

Completeness

Explicitly answers both 'what' (search and recall memories via memsearch, with the typical flow) and 'when' ('Use when the user's question could benefit from...'), with concrete trigger phrases plus explicit skip conditions.

5 / 5

Trigger Term Quality

Includes natural user phrases ('what did I decide about X', 'why did we do Y', 'have I seen this before'), synonym coverage ('historical context, past decisions, debugging notes, previous conversations, project knowledge'), and a concrete system-hint trigger ('[memsearch] Memory available').

5 / 5

Distinctiveness Conflict Risk

Clear niche (past-session memory recall) with distinct triggers including the unique '[memsearch] Memory available' injection hint; minimal overlap with other skills.

5 / 5

Total

20

/

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.

Validation — 14 / 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.