skills.rest
Fantasia1999
Fantasia1999COMMUNITY
Explore all skills by this author →
WebsiteGitHub

remember

Save important knowledge to MEMORY.md with duplicate checks and line limits.

Updated Mar 12, 2026
Search Tags:#debugging#context#memory#persistence#auto-memory#knowledge saving
One-click install
npx skills add https://github.com/Fantasia1999/claude-skills-zh --skill remember-fantasia1999
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: remember
Source: https://github.com/Fantasia1999/claude-skills-zh/tree/main/translations/engineering-team/self-improving-agent/skills/remember
Command: npx skills add https://github.com/Fantasia1999/claude-skills-zh --skill remember-fantasia1999

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill allows you to explicitly save important knowledge to your auto-memory, ensuring that crucial information is not missed by automatic capture mechanisms.

Core Features & Use Cases

  • Explicit Knowledge Saving: Manually add important facts, insights, or project specifications to your persistent memory.
  • Duplicate Checking: Before saving, it checks for existing similar entries to avoid redundancy.
  • Use Case: You discover a critical detail during a complex debugging session, like a specific CORS error cause, and want to ensure Claude remembers it for future reference.

Quick Start

Use the remember skill to save the fact that this project requires Node 20 LTS.

Frequently Asked Questions about remember

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

FAQPage Schema
How do I explicitly save debugging context to persistent memory for future sessions?▼

You explicitly save debugging context by parsing user input for content, importance, and scope, checking for duplicates, and appending the new entry to an auto-memory file for persistent recall.

What is the best way to avoid duplicate knowledge entries when saving project context?▼

The best way to avoid duplicate knowledge entries is to check the existing auto-memory file for similar entries before appending new project context, preventing redundant persistence.

When should I promote saved knowledge to rules instead of keeping it in auto-memory?▼

You should promote saved knowledge to rules when the information is critical, elevating it from the auto-memory file to a higher-level configuration to ensure strict adherence.

What happens when the persistent memory file exceeds its line limit?▼

When the persistent memory file exceeds its line limit, the system issues a warning to alert you, ensuring the auto-memory remains manageable and does not degrade recall performance.

Does the explicit knowledge saving mechanism support scoped persistence for specific projects?▼

Yes, the explicit knowledge saving mechanism supports scoped persistence by parsing user input for scope, allowing you to save important facts and project specifications to specific contexts.

Related Skills

Explore More Software Engineering Skills→
addisonbeckaddisonbeck

create_memory

Create org-roam memory nodes with validated metadata and UUIDs.

Community
Intermediate
stericisherestericishere
1

self-improving-agent

Analyze Claude Code auto-memory to promote patterns and extract reusable skills.

Community
Advanced
HCMUTE-RTICHCMUTE-RTIC

error-diagnostics-smart-debug

Analyze error messages and stack traces to generate ranked root cause hypotheses.

Official
Advanced
darblexdarblex

self-improvement

Capture and organize learnings, errors, and feature requests for AI agents.

Community
Advanced