memory-stats
Skill16 starsChanged 18 days agoMITView on GitHub
View statistics and recent entries from the persistent memory database. Shows session count, knowledge areas, facts, and recent activity.
In this repository8 other files it gives its agents.
- knowledge-graphSkill
- pullSkill
- pushSkill
- qmdSkill
- rememberSkill
- resume-memorySkill
- token-statsSkill
- turbo-indexSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Use the skill's actual installed location, including plugin caches or symlinks.
- Very specific: line 19
When the user invokes /memory-stats, run these commands to show memory information:
≈ “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.
Files
Installed paths
Resolve PLUGIN_DIR to the absolute directory two levels above this SKILL.md file.
Use the skill's actual installed location, including plugin caches or symlinks; do not infer it from the project's working directory or a home-directory checkout.
Set PLUGIN_DIR explicitly in each shell invocation below, keeping the working directory in the user's target repository.
/memory-stats - View Memory Statistics
Show statistics and recent entries from the persistent memory database.
Instructions
When the user invokes /memory-stats, run these commands to show memory information:
1. Show Statistics
: "${PLUGIN_DIR:?Set PLUGIN_DIR from this skill file location}"
"$PLUGIN_DIR/memory/memory-db.sh" stats2. Show Recent Sessions
"$PLUGIN_DIR/memory/memory-db.sh" recent 53. Format Output
Present the information clearly:
## Memory Database
| Type | Count |
|------|-------|
| Sessions | X |
| Knowledge areas | Y |
| Facts | Z |
## Recent Sessions
1. [date] - Summary of session 1
2. [date] - Summary of session 2
...Optional Flags
The user might ask for specific views:
/memory-stats facts- Show all facts/memory-stats knowledge- Show all knowledge areas/memory-stats search <query>- Search memory
For these, use:
# Search
"$PLUGIN_DIR/memory/memory-db.sh" search "query"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
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.

