CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

82%

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

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.

A well-structured, highly actionable configuration skill: executable commands and exact config keys throughout, a clear platform-routing and diagnose-first workflow with error-recovery guidance, and exemplary one-level reference file usage. The main drag is token efficiency — repeated deferral phrases, a duplicated disclaimer, and version-pinned model/version specifics embedded in the main text.

DimensionReasoningScore

Conciseness

The body is dense and MemSearch-specific with no basic-concept padding, but "see your platform reference file" is repeated roughly six times, the MemSearch-vs-host disclaimer is stated twice, and version-pinned specifics ("Since v0.4.11", "gpt-5-mini", "claude-sonnet-4-6", "gemini-3-flash-preview") sit in the main text rather than a compatibility/deprecated section — matching the "mostly efficient but could be tightened" anchor.

3 / 5

Actionability

Guidance is copy-paste ready: exact commands ("memsearch config list --resolved", the PyPI curl one-liner, the MDIR shell block), complete TOML provider examples, an explicit allowlisted project-key list, and exact state-file paths with named error fields ("status", "last_error", "failed_files") cover the common cases.

5 / 5

Workflow Clarity

The sequence (identify platform → read its reference file → route intent → diagnose → apply → show resolved value and restart need) is clear, with explicit error-recovery checkpoints ("status: degraded", ".maintenance-state.json ... last_error") and a confirmation gate before destructive or paid changes; it falls short of 5 because steps are not enumerated and some ordering is only implicit in section order.

4 / 5

Progressive Disclosure

The body is a clear overview that lists all five existing one-level-deep platform reference files with a selection rule and environment markers ("Read ONLY the one file matching your current environment"), and consistently defers platform-specific detail to them; no nested references exist in the bundle.

5 / 5

Total

17

/

20

Passed

Description

78%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 third-person description with an explicit "Use when..." trigger list covering the domain's natural vocabulary. Its main limitation is a thin action list (diagnose/configure only) and slight overlap risk with host-agent memory features that the description does not itself disambiguate.

DimensionReasoningScore

Specificity

"Diagnose and configure MemSearch memory behavior" names the domain with two concrete actions, matching the anchor for 1-2 actions that are not comprehensive; it is below 4 because the action list does not extend beyond diagnose/configure.

3 / 5

Completeness

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

5 / 5

Trigger Term Quality

"MemSearch configuration, plugin summarization, PROJECT.md/USER.md maintenance, memory directories, index health, provider routing, prompt files, or migration/compatibility questions" covers natural phrasings well, but misses common variations users might say such as "search memory", "recall", "embedding", or ".memsearch".

4 / 5

Distinctiveness Conflict Risk

Repeated naming of "MemSearch" gives a clear niche with distinct triggers, but terms like "memory directories" and "memory behavior" carry minor overlap risk with generic memory/config skills — a conflict the body itself has to disambiguate.

4 / 5

Total

16

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

zilliztech/memsearch

Path

plugins/codex/skills/memory-config/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.