CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

search

Search memories from earlier Kimi sessions in this repository. Use it when earlier work may already explain the code, error, decision, or command you need, so you can avoid repeating file reads, searches, or experiments.

Quality

89%

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

The canonical home for this skill is search in mem0ai/mem0

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, well-organized body for a simple single-action skill: it documents the tool call, argument mapping, defaults, scope semantics, and edge guidance (never invent a run_id) with zero padding. The only real gap is the absence of a concrete example tool call showing the parameter structure.

Suggestions

Add one example `search_memories` invocation showing the parameter names and types (e.g., how the user's question maps to the query parameter and how top_k/category/scope/run_id are passed), closing the actionability gap.

State explicitly which parameter carries the user's question (e.g., 'pass the question as `query`') so the flag-to-argument mapping is fully unambiguous.

DimensionReasoningScore

Conciseness

The ~20-line body is lean and assumes Claude's competence: every sentence carries non-obvious detail (defaults for top_k/category/scope, the meaning of repo/dir/mine scopes, "It filters the memories returned; it does not identify the session making the search request", "Use a known session ID, never invent one"). Nothing explains concepts Claude already knows, matching 'every token earns its place'.

5 / 5

Actionability

Guidance is concrete and mostly executable: the exact tool name (`search_memories`), how to map CLI flags (`--top-k`, `--category`, `--scope`, `--run-id`) to tool arguments, defaults when omitted, and the final instruction "Return the tool's result directly". It falls short of a 5 only because no example call shows the actual parameter names/signature (e.g., how the question maps to a `query` parameter), leaving a minor gap.

4 / 5

Workflow Clarity

This is a simple single-task skill and the single action is unambiguous: call `search_memories` with the user's question, pass flags as arguments, return the result directly — the rubric's simple-skill exception applies. There are no destructive or batch operations, so no validation checkpoint is required for a 5.

5 / 5

Progressive Disclosure

At under 50 lines with no need for external references (no references/, scripts/, or assets/ bundles exist), the single section header and short well-organized paragraphs fully satisfy the rubric's simple-skill criterion. There are no nested or buried references to penalize.

5 / 5

Total

19

/

20

Passed

Description

82%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 concise, well-targeted description that clearly states what the skill does and when to use it, with natural trigger phrasing tied to concrete needs (code, error, decision, command). Its only limitation is that it names a single action, which is appropriate for a single-purpose tool but leaves capability coverage thin.

DimensionReasoningScore

Specificity

"Search memories from earlier Kimi sessions in this repository" names the domain and exactly one concrete action (searching memories); for a single-function tool this matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'. It does not list several actions needed for a 4.

3 / 5

Completeness

It explicitly answers both halves: what ("Search memories from earlier Kimi sessions in this repository") and when ("Use it when earlier work may already explain the code, error, decision, or command you need") with concrete trigger objects. Both are present, explicit, and concrete, matching the top anchor; a 4 would require the when-clause to be less specific.

5 / 5

Trigger Term Quality

The when-clause surfaces natural phrases users would say — "earlier work may already explain the code, error, decision, or command you need" — alongside "memories" and "earlier... sessions". A few natural synonyms ("recall", "history", "past sessions") are missing, so it is a good-but-not-comprehensive keyword set rather than a 5.

4 / 5

Distinctiveness Conflict Risk

The niche is clear (session memories from a specific agent, "Kimi sessions", in "this repository") and the triggers (earlier work explaining code, errors, decisions, commands) are unlikely to fire for unrelated skills. This matches 'Clear niche with distinct triggers; minimal conflict risk'; a 4 would imply meaningful overlap with a closely related skill, which is not evident.

5 / 5

Total

17

/

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

mem0ai/mem0

Path

integrations/kimi-plugin/skills/search/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.