memory-config

Diagnose and configure MemSearch memory behavior for the OpenClaw plugin. 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

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

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 content is highly actionable with concrete commands and config, clear diagnostic-first routing, and built-in validation/state checks. Its main weaknesses are minor verbosity (repeated disclaimers, a long version-checking block) and a monolithic single-file structure with no progressive disclosure into bundle files.

Suggestions

Move the per-platform update/version-checking procedures (Codex, Claude Code, OpenClaw, OpenCode) into a references file (e.g. references/updating.md) and keep a one-line pointer in SKILL.md, improving progressive disclosure.

Remove the repeated 'this is MemSearch memory configuration, not OpenClaw's own' disclaimer beyond the single already-mandated mention, or consolidate it once near the top.

Tighten the bulk OpenClaw TOML reference by linking out to a references/config-keys.md file, leaving only the most-used keys inline in SKILL.md.

Dimension	Reasoning	Score
Conciseness	Dense and operational with almost no padding or explanation of concepts Claude already knows, but the 'MemSearch not OpenClaw's own' disclaimer is repeated several times and the multi-platform version-checking block could be trimmed, leaving minor instances of over-explanation short of a 5.	4 / 5
Actionability	Provides copy-paste-ready bash commands, exact TOML keys, concrete CLI flags, and real provider config examples covering the common cases — fully executable guidance.	5 / 5
Workflow Clarity	Clear 'Diagnose First' sequence with explicit state-inspection validation (.index-state.json status/last_error/failed_files, .maintenance-state.json) and ask-before-enabling guardrails for destructive/paid changes, but the body is partly reference-catalog style rather than a single tight validate→fix→retry checklist.	4 / 5
Progressive Disclosure	No bundle files exist and the whole skill is a single ~240-line inlined monolith with clear section headers but no split-out references; dense platform-update and TOML-reference sections that could live in separate files are inlined.	3 / 5
	Total	16 / 20 Passed

Description

95%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 a concrete capability, gives an explicit 'Use when' trigger clause with many natural user phrases, and carves out a distinct niche. The only minor gap is that the listed capabilities are configuration domains rather than a long list of distinct concrete actions.

Dimension	Reasoning	Score
Specificity	Names the domain and several specific capability areas (diagnose, configure, summarization, maintenance, index health, provider routing, prompt files, migration) rather than just 1-2 actions, but they are config domains rather than a comprehensive list of concrete distinct actions, so it sits below a 5.	4 / 5
Completeness	Explicitly answers both 'what' ('Diagnose and configure MemSearch memory behavior for the OpenClaw plugin') and 'when' ('Use when the user asks about...') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Comprehensive natural trigger phrases a user would say ('MemSearch configuration', 'plugin summarization', 'PROJECT.md/USER.md maintenance', 'memory directories', 'index health', 'provider routing', 'prompt files', 'migration/compatibility'), including concrete file-name triggers.	5 / 5
Distinctiveness Conflict Risk	Clear niche (MemSearch memory configuration for the OpenClaw plugin) with distinct triggers and minimal overlap risk with unrelated skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

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/openclaw/skills/memory-config/SKILL.md
Commit: f91f5d3

Reviewed: about 6 hours ago

Table of Contents

Discovery Implementation Validation

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.