remember

Save important knowledge to MEMORY.md with timestamps and context.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/Patasse97/claude-skills --skill remember-patasse97
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: remember
Source: https://github.com/Patasse97/claude-skills/tree/main/engineering-team/self-improving-agent/skills/remember
Command: npx skills add https://github.com/Patasse97/claude-skills --skill remember-patasse97

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Explicitly save important knowledge with timestamped memory and contextual notes, ensuring discoveries are captured beyond automatic prompts.

Core Features & Use Cases

  • Explicit memory entries: write important insights to MEMORY.md with a timestamp and context for future reference.
  • Context-aware recall: reference past decisions, debugging notes, or architectural choices during ongoing work.
  • Use Case: when a finding is too important to rely on memory alone, you can force a memory entry for later review.

Quick Start

Use /si:remember to save a critical insight to MEMORY.md with contextual notes.

Frequently Asked Questions about remember

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

FAQPage Schema
How do I explicitly save important knowledge and insights with a timestamp for future reference?▼

To explicitly save important knowledge with a timestamp, you write insights to MEMORY.md along with contextual notes. This ensures critical discoveries are captured reliably beyond automatic memory prompts for future cross-project reference.

What is the best way to capture debugging notes and architectural decisions across multiple projects?▼

The best way to capture debugging notes and architectural decisions is to write timestamped memory entries to MEMORY.md. This enables context-aware recall of past decisions during ongoing work across multiple projects.

When should I force a memory entry instead of relying on automatic knowledge capture?▼

You should force a memory entry when a finding is too important to rely on automatic capture alone. Explicitly saving to MEMORY.md ensures the discovery is timestamped and preserved for later review.

How does the workflow process handle duplicate memory entries in MEMORY.md?▼

The workflow handles duplicate memory entries by parsing the input and checking for duplicates before writing to MEMORY.md. This prevents redundant records when explicitly saving timestamped knowledge.

Can I promote saved memory entries to permanent rules in CLAUDE.md?▼

Yes, you can promote saved memory entries to CLAUDE.md rules. The workflow suggests promoting memory entries to CLAUDE.md rules when appropriate, turning captured insights into persistent project guidelines.