rune-neural-memory

Captures and recalls cross-session decisions, patterns, and insights via Neural Memory MCP.

1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/dangvu008/VietTruyen --skill rune-neural-memory-dangvu008
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rune-neural-memory
Source: https://github.com/dangvu008/VietTruyen/tree/main/.agents/skills/rune-neural-memory
Command: npx skills add https://github.com/dangvu008/VietTruyen --skill rune-neural-memory-dangvu008

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding sessions lose all context when they end, forcing you to re-explain decisions, rediscover patterns, and repeat past mistakes across projects. This Skill persists decisions, error root causes, and architectural insights in a semantic memory graph that compounds across every session and project. ## Core Features & Use Cases - Recall Mode: Loads relevant past decisions and patterns at session start using project-prefixed semantic queries. - Capture Mode: Saves 2-5 richly-worded memories (decisions, errors, insights, preferences) after each completed task with tags and priorities. - Hypothesis Tracking: Records uncertain architectural decisions, collects supporting or weakening evidence, and verifies falsifiable predictions. - Maintenance Mode: Runs health checks, consolidates episodic memories into semantic ones, and prunes outdated or orphaned entries. - Use Case: After debugging a stale-closure bug in a React project, the Skill saves the root cause and fix pattern; months later, a different project with a similar symptom automatically surfaces that memory during recall. ## Quick Start Ask the agent to recall what it remembers about your current project's authentication decisions before starting work.

Frequently Asked Questions about rune-neural-memory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make an AI remember decisions across sessions?

Use Capture Mode after each completed task to save 2-5 memories with causal language, tags, and priorities via nmem_remember. At the next session start, Recall Mode loads relevant context using project-prefixed queries.

How to track uncertain architecture decisions with evidence?

Use Hypothesis Tracking mode: call nmem_hypothesize with the decision rationale, add supporting or weakening evidence with nmem_evidence, create falsifiable predictions with nmem_predict, and verify outcomes with nmem_verify.

Why does memory recall return irrelevant results from other projects?

Generic queries like "auth" return cross-project noise. Always prefix recall queries with the project name, such as "MyApp PocketBase auth session handling", to scope results to the relevant project.

What should not be saved to neural memory?

Do not save task progress, file paths, git history, or sensitive data like API keys and passwords. File-based state belongs in .rune/ files via session-bridge; neural memory is only for learnable patterns, decisions, and insights.

How do I keep a neural memory store healthy over time?

Run nmem_health to check consolidation, orphan percentage, and connectivity. Use nmem_consolidate weekly to merge episodic memories, nmem_review to surface outdated entries, and nmem_forget to remove stale or sensitive memories.