memory-save

Save user-specified information to UHMS long-term memory with deduplication and validation.

6|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/Acosmi/CrabClaw --skill memory-save-acosmi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory-save
Source: https://github.com/Acosmi/CrabClaw/tree/main/docs/skills/tools/memory/memory-save
Command: npx skills add https://github.com/Acosmi/CrabClaw --skill memory-save-acosmi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Users often need their preferences, habits, and key information persisted across conversations. The Memory Save skill provides a reliable mechanism to explicitly store user-specified data in the UHMS long-term memory so future interactions can reference it.

Core Features & Use Cases

  • Explicitly save memory content with optional memory_type and category metadata.
  • Automatically deduplicate repeated entries and require plan confirmation before persisting to memory.
  • Use cases include saving user preferences, recurring tasks, or important facts to improve continuity and personalization.

Quick Start

Remember the user's preference by calling memory_save with the content to remember.

Frequently Asked Questions about memory-save

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

FAQPage Schema
How do I save user preferences for long-term memory across sessions?

To save user preferences for long-term memory across sessions, you call memory_save with the content to remember. It validates metadata, auto-deduplicates repeated entries, and requires plan confirmation before persisting.

What is long-term memory persistence and how does it handle data deduplication?

Long-term memory persistence explicitly stores user-specified data for future reference. It handles data deduplication by automatically detecting repeated entries and enforcing plan confirmation before saving to memory.

Can I use plan confirmation gating to control what gets saved to memory?

Yes, you can use plan confirmation gating to control memory persistence. The mechanism enforces a confirmation step before any user preferences or facts are committed to long-term memory.

How do I store user habits and profiles with category metadata?

To store user habits and profiles with category metadata, provide the content along with optional memory_type and category fields. The system validates these fields before persisting the data.

Does memory management auto-deduplicate repeated entries when saving facts?

Yes, memory management auto-deduplicates repeated entries when saving facts. This prevents recurring tasks or preferences from being stored multiple times, maintaining clean long-term memory.

When should I not use explicit data persistence for user preferences?

You should not use explicit data persistence for user preferences when the information is only relevant for a single conversation or when it does not require plan confirmation gating for future continuity.