Store and recall user memories and preferences in a private 3D knowledge graph via MCP/REST API.
npx skills add https://github.com/neooriginal/Aether --skill aether-neooriginal
Please help me install this Agent Skill. Skill: aether Source: https://github.com/neooriginal/Aether/tree/main/public Command: npx skills add https://github.com/neooriginal/Aether --skill aether-neooriginal
Aether helps you connect, recall, store, and retrieve memories, preferences, and knowledge from a private 3D knowledge graph, enabling quick context recall and personalized interactions.
Use Aether to recall a memory from your last chat and store a new preference for tone.
High-intent search queries and answers about installing and using this skill.
A private knowledge graph stores user facts and preferences locally, applied at every conversation turn to surface relevant memories for context recall. It queries a semantic graph to retrieve relationships across conversations, ensuring personalized interactions without losing past topics.
A local-first knowledge graph is a private memory storage system where data never leaves your machine. It manages private memories by storing user preferences and personality cues as semantic nodes, enabling secure recall and personalized interactions across multiple conversations.
You store and retrieve user preferences in a semantic knowledge graph by applying the memory management process at every conversation turn. This saves new preferences for tone or personality cues and queries the graph to surface relevant past topics and relationships.
Yes, you need an MCP or REST API with authentication keys to use a private knowledge graph for memory recall. A front-end that visualizes the semantic graph is also required to manage and retrieve stored memories, preferences, and context effectively.
Local-first memory storage is secure for sensitive user context because everything runs locally and data never leaves your machine. This approach ensures that private memories, personality cues, and preferences remain isolated within your private 3D knowledge graph.
You should not use a local-first knowledge graph for conversation memory if you lack an MCP or REST API with authentication keys, or if your workflow requires multi-device synchronization. It requires a local front-end for visualization and does not support remote data access.
DavidKkManage Gist-based MagickMonkey scripts via REST and MCP endpoints.
OriNachumQuery Neo4j knowledge graphs to retrieve entities and relationships.
qualixarCombine semantic similarity, knowledge graph traversal, and full-text search to recall memories.
bmsull560Integrate vector-based memory with knowledge graphs for multi-session conversation context.
