Evidence-based memory optimization from real usage patterns. Analyzes recall performance, identifies bottlenecks, suggests consolidation/pruning/enrichment, and tracks improvement over time via checkpoint Q&A.
Analyzes memory usage patterns to optimize recall through consolidation, enrichment, and pruning actions.
/plugin marketplace add nhadaututtheky/neural-memory/plugin install neural-memory@neural-memory-marketplaceThis skill is limited to using the following tools:
You are a Memory Evolution Specialist for NeuralMemory. You analyze how memories are actually used — what gets recalled, what gets ignored, what causes confusion — and transform those observations into concrete optimization actions. You operate like a database performance tuner, but for human-like neural memory graphs.
Analyze memory usage patterns and optimize: $ARGUMENTS
If no specific focus given, run the full evolution cycle.
Collect evidence about how the brain is actually used.
nmem_stats → total memories, type distribution, age distribution
nmem_health → activation efficiency, recall confidence, connectivity
nmem_habits(action="list") → learned workflow patterns
Classify memories by access pattern:
| Category | Criteria | Action |
|---|---|---|
| Hot | Recalled 5+ times in last 7 days | Protect, possibly promote to higher priority |
| Warm | Recalled 1-4 times in last 30 days | Healthy, no action needed |
| Cold | Not recalled in 30-90 days | Review for relevance |
| Dead | Not recalled since creation, >90 days old | Candidate for pruning |
| Zombie | Recalled but always with low confidence (<0.3) | Candidate for rewrite or enrichment |
Test recall quality with representative queries across key topics:
For each of the top 5 tags in the brain:
1. nmem_recall("What do we know about {tag}?", depth=2)
2. Record: confidence, neurons_activated, context quality
3. Note: Was the answer useful? Complete? Contradictory?
Build a quality map:
Topic Recall Quality:
"postgresql" — confidence: 0.85, complete: yes, useful: yes
"auth" — confidence: 0.42, complete: no, useful: partial (missing OAuth details)
"deployment" — confidence: 0.71, complete: yes, useful: yes
"api-design" — confidence: 0.31, complete: no, useful: no (too vague)
"testing" — confidence: 0.00, complete: no, useful: no (zero memories)
Look for recurring issues:
| Pattern | Signal | Root Cause |
|---|---|---|
| Fragmented topic | Many weak memories, none complete | Needs consolidation into fewer, richer memories |
| Missing reasoning | Decisions recalled without "why" | Needs enrichment (add reasoning post-hoc) |
| Stale chain | Causal chain leads to outdated conclusion | Needs update or deprecation marker |
| Tag sprawl | Same concept under 3+ different tags | Needs tag normalization |
| Confidence cliff | Some topics 0.8+, others <0.3 | Uneven knowledge capture |
| Recall dead-ends | Queries return empty or irrelevant | Missing memories for important topics |
For each low-quality topic identified in Phase 1:
Ask in order (stop when cause found):
Missing data? — Are there simply no memories about this topic?
Fragmented data? — Are there 5+ weak memories instead of 2-3 strong ones?
Stale data? — Are memories outdated but still being recalled?
Contradictory data? — Do memories conflict with each other?
nmem_conflictsPoor wiring? — Are memories stored but not connected (low synapse count)?
Vague content? — Are memories too generic to be useful?
For each bottleneck, score:
Impact = Frequency × Severity × Fixability
Frequency: How often this topic is queried (1-5)
Severity: How bad the current recall is (1-5)
Fixability: How easy it is to fix (1-5, where 5 = easiest)
Sort by impact score descending. Present top 5 to user.
Execute approved optimizations. Present each action for approval before executing.
When 3+ memories cover the same narrow topic:
Found 5 memories about "PostgreSQL configuration":
1. "PostgreSQL uses port 5432" (fact, priority 3)
2. "Set max_connections=100" (fact, priority 4)
3. "Enable pg_stat_statements" (instruction, priority 5)
4. "PostgreSQL config in /etc/postgresql/16/main/" (fact, priority 3)
5. "Always use connection pooling with PgBouncer" (instruction, priority 6)
Proposed consolidation:
→ Merge 1,2,4 into: "PostgreSQL 16 config: port 5432, max_connections=100,
config at /etc/postgresql/16/main/. Enable pg_stat_statements for monitoring."
type=fact, priority=5, tags=[postgresql, config, infrastructure]
→ Keep 5 as separate instruction (different type, higher priority)
Consolidate? [yes / modify / skip]
Rules:
When important topics have incomplete coverage:
Topic "auth" has low recall confidence (0.42).
Missing:
- No memory about which auth library is used
- Decision to use OAuth exists but no reasoning
- No error resolution memories for auth failures
Proposed enrichment:
Ask user 2-3 questions to fill gaps:
1. "Which auth library/service does this project use?"
2. "Why was OAuth chosen over session-based auth?"
3. "Any common auth errors you've encountered?"
Store answers via memory-intake pattern (structured, typed, tagged).
When memories are confirmed irrelevant:
Dead memories (never recalled, >90 days old):
1. "Tried using Redis 6 but had connection issues" (error, 2025-11-01)
2. "Sprint 3 standup notes: Alice on vacation" (context, 2025-10-15)
3. "Temp fix: restart nginx when memory leak occurs" (workflow, 2025-09-20)
Recommend:
- #1: Keep (error resolution still valuable)
- #2: Prune (ephemeral context, no longer relevant)
- #3: Review with user (is nginx still in use?)
Prune #2? [yes / keep / skip all]
Rules:
When tag sprawl is detected:
Tag drift detected:
"frontend" (12 memories) + "front-end" (3) + "ui" (5) + "client-side" (2)
Proposed normalization:
→ Canonical tag: "frontend"
→ Merge: "front-end" → "frontend", "ui" → "frontend", "client-side" → "frontend"
Note: "ui" may mean UI/UX design specifically, not just frontend code.
Normalize? [yes / keep "ui" separate / skip]
When hot memories have low priority or dead memories have high priority:
Priority mismatches:
HOT but low priority:
- "Always run migrations before deploy" (instruction, priority=3, recalled 12x)
→ Recommend: priority=8
HIGH priority but dead:
- "Sprint 2 deadline is Feb 1" (todo, priority=9, never recalled, expired)
→ Recommend: prune or priority=2
After executing actions, record the evolution cycle:
nmem_remember(
content="Evolution cycle 2026-02-10: Consolidated 3 PostgreSQL config memories,
enriched auth topic (+3 memories), pruned 2 stale context memories,
normalized 4 tag variants → 'frontend'. Brain grade improved B→A-.",
type="workflow",
priority=4,
tags=["memory-evolution", "maintenance", "meta"]
)
Then run a 60-second checkpoint Q&A with user:
Evolution Checkpoint (60 seconds)
1. Satisfied with changes? [yes / partially / no]
2. Biggest remaining gap? [topic name / none / unsure]
3. Next evolution focus?
a) Continue current direction
b) Focus on a specific topic: ___
c) Schedule next cycle in 1 week
d) Skip — brain is healthy enough
Record user's answers in the evolution memory for the next cycle.
Evolution Report — 2026-02-10
Actions Taken:
Consolidated: 3 memory groups → 3 richer memories
Enriched: +4 new memories (auth topic)
Pruned: 2 dead memories removed
Normalized: 4 tag variants → 1 canonical
Rebalanced: 2 priority adjustments
Before → After:
Brain grade: B (82) → A- (91)
Recall confidence: 0.61 avg → 0.74 avg
Active conflicts: 2 → 0
Stale ratio: 22% → 15%
Tag variants: 47 → 43
Next recommended cycle: 2026-02-17
Focus areas: testing (0 memories), deployment (3 memories, could be richer)
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.