CtrlK
BlogDocsLog inGet started
Tessl Logo

memory-config

Diagnose and configure MemSearch memory behavior. Use when the user asks about MemSearch configuration, plugin summarization, PROJECT.md/USER.md maintenance, memory directories, index health, provider routing, prompt files, or migration/compatibility questions.

71

Quality

86%

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

The canonical home for this skill is memory-config in zilliztech/memsearch

SKILL.md
Quality
Evals
Security

Quality

Content

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

Well-structured, actionable configuration skill with strong progressive disclosure and concrete commands. Minor conciseness trims and a few implicit validation steps are the only weaknesses.

DimensionReasoningScore

Conciseness

The body is dense with executable commands and config keys and mostly assumes competence, but repeated "see your platform reference file" phrasings and the Background/Compatibility prose could be trimmed slightly.

4 / 5

Actionability

Copy-paste-ready commands (`memsearch config list --resolved`, version checks, `memsearch config set`) and complete TOML provider examples cover the common cases with executable guidance.

5 / 5

Workflow Clarity

A clear diagnose-then-route-by-intent sequence with validation checkpoints (ask before re-indexing/deleting state; show resolved value and restart need after changes); minor gaps keep it below 5.

4 / 5

Progressive Disclosure

The body is a clear overview with well-signaled one-level-deep per-platform reference files (all verified present), instructing the reader to load only the matching platform file.

5 / 5

Total

18

/

20

Passed

Description

87%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 strong description: third-person voice, explicit what/when, concrete trigger terms tied to a named product niche. Slightly light on distinct action verbs, which keeps specificity and trigger quality at 4 rather than 5.

DimensionReasoningScore

Specificity

"Diagnose and configure MemSearch memory behavior" names the domain plus two concrete actions, and the trigger clause enumerates several specific capability areas (plugin summarization, PROJECT.md/USER.md maintenance, index health, provider routing, prompt files); minor gaps remain in distinct action verbs.

4 / 5

Completeness

It explicitly states both what ("Diagnose and configure MemSearch memory behavior") and when ("Use when the user asks about..." with concrete trigger phrases), matching the top anchor.

5 / 5

Trigger Term Quality

The "Use when the user asks about..." clause lists natural terms a user would say ("MemSearch configuration", "index health", "provider routing", "prompt files", "migration/compatibility questions"), with good coverage though a few synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

The MemSearch product name carves a clear niche with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

18

/

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.