cortex-explore-memory skill
✓ VerifiedAnalyze memory system health, identify knowledge gaps, assess coverage, and validate memory accuracy against the filesystem.
- GitHub stars
- 76
- Files
- 1
- Last commit
- Nov 12, 2026
- License
- MIT
- Allowed tools
- —
What does the cortex-explore-memory skill do?
cortex-explore-memory analyzes memory system health, identify knowledge gaps, assess coverage, and validate memory accuracy against the filesystem.
Summary generated from the skill's SKILL.md.
About the cortex-explore-memory skill
Analyzing the health and completeness of your stored knowledge is what cortex-explore-memory enables. Developers use this skill to audit their memory systems, identify where information is missing, and ensure that stored facts remain accurate relative to the actual filesystem. It is particularly useful when starting new project phases or after long periods of inactivity to determine if the agent has sufficient context for upcoming tasks.
The skill provides a suite of diagnostic tools including memory_stats for system-level metrics like entity counts and decay statistics, and assess_coverage to generate a numerical score for specific domains. It can pinpoint isolated entities or orphan clusters through detect_gaps and verify that memory references to files or functions are still valid using validate_memory. By running these tools, an agent produces a clear picture of knowledge strength, temporal gaps, and potential stale data.
What an agent can do with it
- 1Audit memory system healthRequest a high-level summary of total memories, entity counts, and confidence levels.
- 2Identify missing project informationFind specific areas within a domain where knowledge is sparse or disconnected.
- 3Score topic knowledge depthDetermine how well a specific project or topic is documented with a coverage score.
- 4Clean up stale referencesCheck if existing memories point to files or functions that have been deleted or moved.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the cortex-explore-memory skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the cortex-explore-memory skill in Plugin
/plugin marketplace add cdeust/Cortex /plugin install hypermnesia-mcp@cortex-plugins
Install the cortex-explore-memory skill in Claude Code
~/.claude/skills/cortex-explore-memory/SKILL.md
$ npx degit cdeust/Cortex/skills/cortex-explore-memory ~/.claude/skills/cortex-explore-memoryInstall the cortex-explore-memory skill in Claude Code (project)
.claude/skills/cortex-explore-memory/SKILL.md
$ npx degit cdeust/Cortex/skills/cortex-explore-memory .claude/skills/cortex-explore-memoryInstall the cortex-explore-memory skill in Codex
~/.agents/skills/cortex-explore-memory/SKILL.md
$ npx degit cdeust/Cortex/skills/cortex-explore-memory ~/.agents/skills/cortex-explore-memoryInstall the cortex-explore-memory skill in Gemini CLI
~/.gemini/skills/cortex-explore-memory/SKILL.md
$ npx degit cdeust/Cortex/skills/cortex-explore-memory ~/.gemini/skills/cortex-explore-memoryInstall the cortex-explore-memory skill in Claude.ai
npx degit cdeust/Cortex/skills/cortex-explore-memory cortex-explore-memory && zip -r cortex-explore-memory.zip cortex-explore-memory # claude.ai → Customize → Skills → + → Create skill → Upload a skill → cortex-explore-memory.zip
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the scripts before you let an agent run them. How checks work
- Source repository linked and reachablecdeust/cortex/skills/cortex-explore-memory is public and reachablegithub.com/cdeust/cortex/tree/HEAD/skills/cortex-explore-mem ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit 2026-11-12github.com/cdeust/cortex/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/cdeust/cortex/blob/HEAD/skills/cortex-explore-mem ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/cdeust/cortex/blob/HEAD/skills/cortex-explore-mem ↗Pass
- SKILL.md follows the Agent Skills formatValid name and description; says when to use it; 95 linesgithub.com/cdeust/cortex/blob/HEAD/skills/cortex-explore-mem ↗Pass
SKILL.md
View on GitHubExplore Memory — Diagnostics, Gaps, and Coverage
Keywords
memory stats, diagnostics, coverage, gaps, what am I missing, memory health, knowledge gaps, weak areas, isolated entities, sparse domains, how much do I know, memory overview, system status, knowledge assessment
Overview
Understand the state of your memory system — what's stored, what's missing, what's decaying, and where knowledge is strong or weak. This skill combines multiple diagnostic tools to give you a complete picture.
Use this skill when: Starting a new project phase, after a long break, or when you want to understand what Cortex knows and doesn't know about a topic.
Workflow
Step 1: Quick Health Check
Get system-level diagnostics:
cortex:memory_stats({})
Returns: total memories, heat distribution, store type breakdown (episodic vs semantic), entity count, relationship count, average confidence, and decay statistics.
Step 2: Assess Knowledge Coverage
Score how well a topic or project is covered:
cortex:assess_coverage({
"domain": "<project or topic>",
"query": "<specific area to assess>"
})
Returns a 0-100 coverage score with specific recommendations on what to document or remember next.
Step 3: Detect Knowledge Gaps
Find isolated entities, sparse domains, and temporal drift:
cortex:detect_gaps({
"domain": "<optional domain filter>"
})
Returns:
- Isolated entities — entities mentioned but not connected to memories
- Sparse domains — project areas with few memories
- Temporal gaps — periods with no memory activity (potential knowledge loss)
- Orphan clusters — groups of memories disconnected from the main knowledge graph
Step 4: Validate Against Filesystem
Check if memories reference files/paths that still exist:
cortex:validate_memory({
"directory": "<project root>"
})
Flags stale memories that reference deleted files, moved modules, or renamed functions — keeping the knowledge base accurate.
Step 5: Review Memory Quality
Get a narrative summary of what's stored:
cortex:narrative({
"domain": "<project>",
"style": "diagnostic"
})
Or get a period-based project story:
cortex:get_project_story({
"domain": "<project>",
"period": "last_30_days"
})
Tips
- Run after backfill: After
cortex:backfill_memories, run diagnostics to see what was captured and what's still missing - Coverage before deep work: Before a major feature or refactor, assess coverage to know if you have enough context stored
- Validate periodically: Run
validate_memoryafter major refactors to catch stale references
Files in this skill
1cortex-explore-memory skill questions
How do I install the cortex-explore-memory skill in Claude Code?
Run npx degit cdeust/Cortex/skills/cortex-explore-memory ~/.claude/skills/cortex-explore-memory. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the cortex-explore-memory skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
How can I check the overall health of my memory system?
You can perform a quick health check using the memory_stats tool to see total memories, heat distribution, entity counts, and decay statistics.
How do I find out what information is missing from my knowledge base?
Use the detect_gaps tool to identify isolated entities, sparse domains, temporal gaps, and orphan clusters.
Can I verify if my memories are still accurate after I move or delete files?
Yes, use the validate_memory tool to flag stale memories that reference deleted files, moved modules, or renamed functions.