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

Critical

Do not install without reviewing

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 strong, highly actionable configuration skill: executable commands, exact config keys, and well-organized per-platform references kept one level deep. The main weakness is redundancy — repeated disclaimers and platform-reference pointers — and version-sensitive details that could drift, which keep it from full token efficiency.

Suggestions

State the MemSearch-vs-host-memory disclaimer once (e.g., in the opening paragraph) and reference it from the closing summary instead of repeating it three times.

Consolidate the six 'see your platform reference file' pointers into a single named convention (e.g., 'platform-ref') defined once, so later sections can say 'per platform-ref' without restating the instruction.

Move version-sensitive specifics (v0.4.11 allowlist behavior, exact model default names like gpt-5-mini / claude-sonnet-4-6 / gemini-3-flash-preview) into a short 'Compatibility' reference file so the body does not silently go stale as versions change.

DimensionReasoningScore

Conciseness

The body is dense with MemSearch-specific facts Claude could not know, but it includes repetition that could be tightened: the 'this is MemSearch, not the host agent's memory system' disclaimer appears three times, 'see your platform reference file' is repeated six times, and config resolution behavior is explained twice. This matches 'mostly efficient but some unnecessary explanation or could be tightened' rather than the minor-trim level of 4.

3 / 5

Actionability

Guidance is fully executable: copy-paste-ready diagnostics (memsearch config list --resolved, memsearch stats, state-file inspection), complete TOML provider examples, exact allowlisted project keys, model defaults, and precise state-file fields to check (status, last_error, failed_files, last_failed_at).

5 / 5

Workflow Clarity

There is a clear sequence (identify platform → route intent → diagnose → configure → apply) with real checkpoints: verify resolved values after every change, check .index-state.json and .maintenance-state.json for silent failures, and a pre-enablement checklist before advanced maintenance. It falls short of 5 because the intent-routing flows are sketched as one-liners without an explicit ordered procedure or a re-verify loop after config changes.

4 / 5

Progressive Disclosure

Platform-specific detail is properly split into six real, one-level-deep reference files (references/workbuddy.md, claude-code.md, codex.md, openclaw.md, opencode.md, dsh.md — all present), clearly signaled with 'Read ONLY the one file matching your current environment', while the body stays at overview level. Structure and navigation match the top anchor.

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 well-crafted description with an explicit 'Use when' clause, concrete trigger phrases, and a clearly named niche. Its main limitation is that the 'what' portion states only two actions (diagnose, configure), with the scope conveyed through the trigger list rather than enumerated capabilities.

DimensionReasoningScore

Specificity

"Diagnose and configure MemSearch memory behavior" names the domain and exactly two concrete actions, matching the 'domain + 1-2 concrete actions, not comprehensive' anchor; it does not enumerate the several specific operations (routing providers, maintaining PROJECT.md/USER.md, checking index health) that would justify a 4.

3 / 5

Completeness

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

5 / 5

Trigger Term Quality

The trigger list — "MemSearch configuration, plugin summarization, PROJECT.md/USER.md maintenance, memory directories, index health, provider routing, prompt files, or migration/compatibility questions" — covers most natural phrases a user would say, but a few common variations (e.g., "memory isn't saving", "search returns nothing") are absent, placing it at 'good coverage, a few natural terms missing' rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

MemSearch is a named product with a clear niche and distinct triggers (PROJECT.md/USER.md, provider routing, prompt files), but generic "memory" terms create minor overlap risk with the host agent's own memory/config skills — a confusion the body itself acknowledges — so it sits at 'mostly distinct, minor overlap risk' rather than minimal.

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/opencode/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.