memento_skill

This skill provides local memory for OpenClaw agents by capturing conversations, extracting facts, and recalling relevant knowledge before each turn.
  • Python

2.6k

GitHub Stars

13

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill memento

  • _meta.json798 B
  • CHANGELOG.md6.5 KB
  • DESIGN.md11.6 KB
  • MIGRATION-SPEC.md4.1 KB
  • openclaw.plugin.json4.1 KB
  • package-lock.json17.9 KB
  • package.json708 B
  • PHASE2-SPEC.md7.7 KB
  • README.md14.2 KB
  • ROADMAP.md21.2 KB
  • SKILL.md8.7 KB
  • tsconfig.build.json310 B
  • tsconfig.json249 B

Overview

This skill provides local persistent memory for OpenClaw agents. It captures conversations, extracts structured facts via a configurable LLM, and auto-injects relevant knowledge before each agent turn. All data is stored locally in SQLite and JSONL to prioritize privacy and offline operation.

How this skill works

Memento listens to message events and buffers multi-turn conversation segments. It optionally sends segments to a configured extraction model to produce structured facts (preferences, decisions, action items, people) and stores facts with provenance and privacy labels. Before each AI turn, Memento recalls relevant facts using FTS5 keyword search and optional semantic embeddings, scoring matches by recency, frequency, and category weight.

When to use it

  • Give agents long-term memory of user preferences, decisions, and action items.
  • Maintain local-only storage for privacy-sensitive deployments without cloud sync.
  • Bootstrap knowledge across agents while keeping private facts siloed.
  • Improve agent context with automated recall of relevant facts before responses.
  • Migrate existing workspace memory files into a single local store for archives or backups.

Best practices

  • Keep autoExtract disabled until you confirm your extraction model and privacy needs.
  • Use ollama/<model> for fully air-gapped extraction to ensure no text leaves the machine.
  • Tune recall.maxFacts and extraction.minTurnsForExtraction to balance context size and relevance.
  • Mark highly sensitive categories as secret so they never participate in extraction or cross-agent recall.
  • Run migration dry-runs first to verify which files will be imported.

Example use cases

  • A customer support agent that remembers recurring user issues and suggested fixes across sessions.
  • Internal team assistants that retain project decisions and action items while keeping HR or payroll notes private.
  • An archive/backup tool for all versions of skills and agent conversations stored locally for compliance.
  • Offline deployments where embeddings and extraction use local models for semantic recall without cloud access.

FAQ

By default captured data stays local. autoExtract will send segments to the configured extraction model if that model is a cloud provider; use ollama/* for fully local extraction.

Can private facts be shared across agents?

No. Facts are classified as shared, private, or secret. Private and secret facts never cross agent boundaries; shared facts flow with provenance tags.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
memento skill by openclaw/skills | VeilStrat