Saves specific, important facts into permanent memory.
Install
mkdir -p .claude/skills/remember && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/3311" && unzip -o skill.zip -d .claude/skills/remember && rm skill.zipInstalls to .claude/skills/remember
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Explicitly save important knowledge to auto-memory with timestamp and context. Use when a discovery is too important to rely on auto-capture.Key capabilities
- →Save project-specific constraints
- →Store recurring bug root causes
- →Index memory for retrieval
- →Propose promotion to project rules
How it works
Appends user input as a distinct note within a local project-specific `MEMORY.md` file after checking for duplicates.
Inputs & outputs
When to use remember
- →Saving project-specific configuration constraints
- →Recording root cause analysis for recurring bugs
- →Storing coding style preferences
About this skill
/si:remember — Save Knowledge Explicitly
Writes an explicit entry to auto-memory when something is important enough that you don't want to rely on Claude noticing it automatically.
Usage
/si:remember <what to remember>
/si:remember "This project's CI requires Node 20 LTS — v22 breaks the build"
/si:remember "The /api/auth endpoint uses a custom JWT library, not passport"
/si:remember "Reza prefers explicit error handling over try-catch-all patterns"
When to Use
| Situation | Example |
|---|---|
| Hard-won debugging insight | "CORS errors on /api/upload are caused by the CDN, not the backend" |
| Project convention not in CLAUDE.md | "We use barrel exports in src/components/" |
| Tool-specific gotcha | "Jest needs --forceExit flag or it hangs on DB tests" |
| Architecture decision | "We chose Drizzle over Prisma for type-safe SQL" |
| Preference you want Claude to learn | "Don't add comments explaining obvious code" |
Workflow
Step 1: Parse the knowledge
Extract from the user's input:
- What: The concrete fact or pattern
- Why it matters: Context (if provided)
- Scope: Project-specific or global?
Step 2: Check for duplicates
MEMORY_DIR="$HOME/.claude/projects/$(pwd | sed 's|/|%2F|g; s|%2F|/|; s|^/||')/memory"
grep -ni "<keywords>" "$MEMORY_DIR/MEMORY.md" 2>/dev/null
If a similar entry exists:
- Show it to the user
- Ask: "Update the existing entry or add a new one?"
Step 3: Write to MEMORY.md
Append to the end of MEMORY.md:
- {{concise fact or pattern}}
Keep entries concise — one line when possible. Auto-memory entries don't need timestamps, IDs, or metadata. They're notes, not database records.
If MEMORY.md is over 180 lines, warn the user:
⚠️ MEMORY.md is at {{n}}/200 lines. Consider running /si:memory-review to free space.
Step 4: Suggest promotion
If the knowledge sounds like a rule (imperative, always/never, convention):
💡 This sounds like it could be a CLAUDE.md rule rather than a memory entry.
Rules are enforced with higher priority. Want to /si:promote it instead?
Step 5: Confirm
✅ Saved to auto-memory
"{{entry}}"
MEMORY.md: {{n}}/200 lines
Claude will see this at the start of every session in this project.
What NOT to use /si:remember for
- Temporary context: Use session memory or just tell Claude in conversation
- Enforced rules: Use
/si:promoteto write directly to CLAUDE.md - Cross-project knowledge: Use
~/.claude/CLAUDE.mdfor global rules - Sensitive data: Never store credentials, tokens, or secrets in memory files
Tips
- Be concise — one line beats a paragraph
- Include the concrete command or value, not just the concept
- ✅ "Build with
pnpm build, tests withpnpm test:e2e" - ❌ "The project uses pnpm for building and testing"
- ✅ "Build with
- If you're remembering the same thing twice, promote it to CLAUDE.md
When not to use it
- →Storing transient data
- →Replacing system configuration files
Limitations
- →Limited to 200 lines
- →Requires manual cleanup
How it compares
Provides a persistent, human-readable scratchpad for session-specific knowledge that survives beyond the standard conversation window.
Compared to similar skills
remember side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| remember (this skill) | 1 | 4mo | Review | Beginner |
| notion-knowledge-capture | 10 | 9mo | No flags | Intermediate |
| apple-reminders | 25 | 2mo | Review | Beginner |
| memory-keeper-proactive-context-maintenance | 6 | 9mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by alirezarezvani
View all by alirezarezvani →You might also like
notion-knowledge-capture
makenotion
Transforms conversations and discussions into structured documentation pages in Notion. Captures insights, decisions, and knowledge from chat context, formats appropriately, and saves to wikis or databases with proper organization and linking for easy discovery.
apple-reminders
openclaw
Manage Apple Reminders via the `remindctl` CLI on macOS (list, add, edit, complete, delete). Supports lists, date filters, and JSON/plain output.
memory-keeper-proactive-context-maintenance
b4CU-R4U
Automatically detect and maintain memory freshness by monitoring context staleness, significant code changes, task completions, and phase transitions. Proactively suggests and executes memory sync operations with user confirmation. Use when the user says "sync memory", "update context", or when the Skill detects that context is stale (>2 hours), significant changes have occurred (new commits), tasks completed, or major milestones reached. Replaces passive "context is stale" warnings with active maintenance.
notion-meeting-intelligence
openai
Prepare meeting materials with Notion context and Codex research; use when gathering context, drafting agendas/pre-reads, and tailoring materials to attendees.
agent-memory
yamadashy
Use this skill when the user asks to save, remember, recall, or organize memories. Triggers on: 'remember this', 'save this', 'note this', 'what did we discuss about...', 'check your notes', 'clean up memories'. Also use proactively when discovering valuable findings worth preserving.
apple-notes
openclaw
Manage Apple Notes via the `memo` CLI on macOS (create, view, edit, delete, search, move, and export notes). Use when a user asks OpenClaw to add a note, list notes, search notes, or manage note folders.