memory

Store and retrieve short-term operational memories as semantic vectors.

15|4|Updated Dec 24, 2025
One-click install
npx skills add https://github.com/tao3k/xiuxian-artisan-workshop --skill memory-tao3k
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory
Source: https://github.com/tao3k/xiuxian-artisan-workshop/tree/main/assets/skills/memory
Command: npx skills add https://github.com/tao3k/xiuxian-artisan-workshop --skill memory-tao3k

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires omni.foundation, omni.rag, PyYAML, and includes scripts (resource) components.

What problem does it solve?

Enables agents and developers to persist and recall short-term operational knowledge such as transient findings, workarounds, and recent execution context that would otherwise be lost between sessions.

Core Features & Use Cases

  • Vectorized Memory Storage: Save insights as embeddings and persist them to LanceDB or a Rust-backed vector store for fast semantic retrieval.
  • Semantic Search & Recall: Query recent operational context, incident notes, and temporary workarounds using embedding-based relevance scores.
  • Skill Manifest Loading & Indexing: Load skill manifests into semantic memory, create or optimize IVF-FLAT indexes, and retrieve memory statistics for diagnostics.
  • Use Case: Save a temporary parser timeout workaround during an MCP queue spike and later recall it when troubleshooting repeated timeouts.

Quick Start

Save a transient operational insight by asking the agent to store a one-sentence finding with metadata like domain and kind so it can be semantically retrieved later.

Frequently Asked Questions about memory

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

FAQPage Schema
How do I store transient operational context and workarounds for semantic search in agent workflows?

Store short-term operational insights as vector embeddings to persist transient findings, workarounds, and recent execution context for later semantic recall. You save a one-sentence finding with metadata like domain and kind, enabling fast retrieval across agent sessions.

How does LanceDB work with vector memory management for temporary notes?

LanceDB serves as the vector store for semantic memory management, persisting temporary operational notes as embeddings. It supports IVF-FLAT index creation and optimization to enable fast semantic search and retrieval of recent execution context during agent workflows.

Can I use semantic search to recall incident notes and temporary workarounds across sessions?

Semantic search lets you query recalled incident notes and temporary workarounds using embedding-based relevance scores. By storing short-term operational memories as semantic vectors, you can retrieve past execution context even when troubleshooting issues like repeated timeouts.

Do I need PyYAML to load skill manifests into vector store memory?

PyYAML is required to parse and load skill manifests into semantic memory. Once loaded, the system creates or optimizes IVF-FLAT indexes within the LanceDB or Rust-backed vector store and retrieves memory statistics for diagnostics.

What's the best way to generate embeddings for short-term operational memory in developer tooling?

Generate embeddings for short-term operational memory by saving transient insights through an MCP-facing API. The system handles embedding generation and persists the vectors to a Rust-backed vector store, making them available for semantic search and recall.

When should I not use a vector store for transient operational notes?

Vector stores for transient operational notes are not suited for permanent knowledge retention or structured relational data. They are designed for short-term operational context, temporary workarounds, and recent execution findings that support semantic search rather than long-term archival storage.