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

84%

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

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 highly actionable, well-structured configuration guide: executable diagnostic commands, precise config-scope rules, safety gates before destructive operations, and exemplary progressive disclosure across the six platform reference files. Its main weakness is redundancy — the host-memory disclaimer, platform-reference pointers, and trusted-key rules are each repeated multiple times and could be consolidated.

Suggestions

State the "this is MemSearch, not the host agent's memory/config system" disclaimer once (e.g., in the opening) and remove the restatement in the "Applying changes" section.

Consolidate the trusted-vs-project config key rules into a single section and reference it from "Applying changes" instead of restating the key lists three times.

Replace the repeated "see your platform reference file" reminders with one prominent statement that all platform-specific details (plugin keys, native model defaults, restart guidance) live in the platform file.

DimensionReasoningScore

Conciseness

The bulk is dense, non-inferable domain knowledge (v0.4.11 project-config restrictions, allowlisted keys, model resolution order), but there is noticeable repetition: the "this is MemSearch, not the host agent's memory/config system" disclaimer appears both in the opening and again near the end, "see your platform reference file" recurs about six times, and the trusted-vs-project key rules are restated in "Configuration Logic", "Applying changes", and the closing paragraph. This fits anchor 3 ("could be tightened") better than anchor 4, since the redundancy goes beyond minor trimming, but is well above anchor 2's padded verbosity.

3 / 5

Actionability

Provides copy-paste-ready commands for every common case: `memsearch config list --resolved/--global/--project`, version and PyPI latest-version checks, memory-file inspection (`ls`, `find`, `tail`), `memsearch stats`, concrete TOML provider blocks, and explicit scope rules for `memsearch config set` (global vs `--project`). This matches anchor 5's fully executable, common-case-covering guidance.

5 / 5

Workflow Clarity

The flow is coherent and well-checkpointed: detect platform via environment markers, read exactly one platform reference, route intent, diagnose first with concrete commands, ask before risky operations ("Ask the user before enabling external or paid providers, ... re-indexing, deleting state"), and after changes "show the command, the resolved value, and whether a new session is needed". Error-recovery guidance exists (`.index-state.json` status/degraded/error semantics, `.maintenance-state.json` last_error), but the sequence is presented as topical sections rather than an explicit ordered workflow and post-fix re-verification is implied, fitting anchor 4 rather than anchor 5.

4 / 5

Progressive Disclosure

Platform-specific details are correctly split into six per-platform reference files, all of which exist in `references/` and are exactly one level deep. The body clearly signals navigation ("Read ONLY the one file matching your current environment") with environment markers for disambiguation, matching anchor 5's well-signaled, appropriately split structure.

5 / 5

Total

17

/

20

Passed

Description

83%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 strong: it states concrete capabilities, provides an explicit and detailed "Use when" trigger clause, and is tightly scoped to the named MemSearch tool. Trigger coverage is good though it misses a few natural synonyms, and the action verbs are limited to diagnose/configure despite broad topical coverage.

DimensionReasoningScore

Specificity

"Diagnose and configure MemSearch memory behavior" names two concrete actions applied to an enumerated list of specific areas ("plugin summarization, PROJECT.md/USER.md maintenance, memory directories, index health, provider routing, prompt files, or migration/compatibility questions"). Coverage of sub-tasks is broad, but the action verbs themselves are limited to diagnose/configure, matching anchor 4 rather than anchor 5's multiple distinct concrete actions.

4 / 5

Completeness

Explicitly answers both "what" ("Diagnose and configure MemSearch memory behavior") and "when" with concrete trigger phrases ("Use when the user asks about MemSearch configuration, plugin summarization, ..."). This mirrors the anchor-5 example structure; it is above anchor 4 because the when-clause is fully explicit rather than merely present.

5 / 5

Trigger Term Quality

Includes natural phrases users would say such as "MemSearch configuration", "index health", "provider routing", "prompt files", and concrete filenames (PROJECT.md/USER.md). A few natural terms are missing (e.g., "memory search", "recall", "summarizer settings"), so it fits anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

Everything is anchored to the distinct named tool "MemSearch" with niche triggers (plugin summarization, PROJECT.md/USER.md maintenance), giving a clear niche. Terms like "memory directories" carry minor overlap risk with generic memory-management skills, so anchor 4 fits better than anchor 5, while the tool-specific naming keeps it above anchor 3.

4 / 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

zilliztech/memsearch

Path

plugins/claude-code/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.