agentleFS
Sign inStart free
ladyicebergladyiceberg/openclaw-memory-quality/skills/memory-check/SKILL.md

memory-check

Skill1 starsChanged 7 months agoMITView on GitHub

Quickly scan OpenClaw memory system health and summarize findings in plain language. Use this skill whenever the user asks about memory health, memory status, memory stats, wants to know if their OpenClaw memory is working well, or uses phrases like "check memory", "memory health", "how is my memory", "记忆健康", "检查记忆", "记忆状态", "记忆统计". Always use this skill — don't try to answer memory health questions without it.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run memory_health_check_oc and translate the output into a plain-language summary.

    line 8
  2. Very specific:

    Call memory_health_check_oc (pass workspace_dir if the user specified one)

    line 12
  3. Distinctive:

    Read the raw report and identify the most important finding

    line 13
  4. Distinctive:

    If there are problems, suggest the next action

    line 16
  5. Distinctive:

    No API key required. Fast (< 1s).

    line 27

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Memory Check

Run memory_health_check_oc and translate the output into a plain-language summary.

Steps

  1. Call memory_health_check_oc (pass workspace_dir if the user specified one)
  2. Read the raw report and identify the most important finding
  3. Give a one-sentence verdict first: healthy / minor issues / needs attention
  4. Show the full report
  5. If there are problems, suggest the next action

When to suggest follow-up

  • Zombie entries > 10% or false-positive signals > 15% → suggest /memory-cleanup
  • Retrieval quality looks degraded → suggest /memory-diagnose
  • MEMORY.md has 200+ entries → suggest running a longterm audit
  • Everything looks fine → say so, no action needed

Notes

No API key required. Fast (< 1s). Read-only — never modifies any files.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free