How do I install the Remember skill?

Run npx skillmds@latest add sneg55/remember in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Remember safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Remember?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Remember free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Remember?

sneg55 (@sneg55) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Remember by sneg55 — Agent Skill

Name: Remember
Rating: 4.2 (5 reviews)
Author: sneg55

File contents

Memory Review

Goal

Review the user's memory landscape and produce a clear report of proposed changes, grouped by action type. Do NOT apply changes - present proposals for user approval.

Steps

1. Gather all memory layers

Read CLAUDE.md and CLAUDE.local.md from the project root (if they exist). Your auto-memory content is already in your system prompt - review it there. Note which team memory sections exist, if any.

Success criteria: You have the contents of all memory layers and can compare them.

2. Classify each auto-memory entry

For each substantive entry in auto-memory, determine the best destination:

Destination	What belongs there	Examples
CLAUDE.md	Project conventions and instructions for Claude that all contributors should follow	"use bun not npm", "API routes use kebab-case", "test command is bun test", "prefer functional style"
CLAUDE.local.md	Personal instructions for Claude specific to this user, not applicable to other contributors	"I prefer concise responses", "always explain trade-offs", "don't auto-commit", "run tests before committing"
Team memory	Org-wide knowledge that applies across repositories (only if team memory is configured)	"deploy PRs go through #deploy-queue", "staging is at staging.internal", "platform team owns infra"
Stay in auto-memory	Working notes, temporary context, or entries that don't clearly fit elsewhere	Session-specific observations, uncertain patterns

Important distinctions:

CLAUDE.md and CLAUDE.local.md contain instructions for Claude, not user preferences for external tools (editor theme, IDE keybindings, etc. don't belong in either)
Workflow practices (PR conventions, merge strategies, branch naming) are ambiguous - ask the user whether they're personal or team-wide
When unsure, ask rather than guess

Success criteria: Each entry has a proposed destination or is flagged as ambiguous.

3. Identify cleanup opportunities

Scan across all layers for:

Duplicates: Auto-memory entries already captured in CLAUDE.md or CLAUDE.local.md → propose removing from auto-memory
Outdated: CLAUDE.md or CLAUDE.local.md entries contradicted by newer auto-memory entries → propose updating the older layer
Conflicts: Contradictions between any two layers → propose resolution, noting which is more recent

Success criteria: All cross-layer issues identified.

4. Present the report

Output a structured report grouped by action type:

Promotions - entries to move, with destination and rationale
Cleanup - duplicates, outdated entries, conflicts to resolve
Ambiguous - entries where you need the user's input on destination
No action needed - brief note on entries that should stay put

If auto-memory is empty, say so and offer to review CLAUDE.md for cleanup.

Success criteria: User can review and approve/reject each proposal individually.

Rules

Present ALL proposals before making any changes
Do NOT modify files without explicit user approval
Do NOT create new files unless the target doesn't exist yet
Ask about ambiguous entries - don't guess

---name: rememberdescription: Review auto-memory entries and propose promotions to CLAUDE.md, CLAUDE.local.md, or shared memory. Also detects outdated, conflicting, and duplicate entries across memory layers.---# Memory Review## GoalReview the user's memory landscape and produce a clear report of proposed changes, grouped by action type. Do NOT apply changes - present proposals for user approval.## Steps### 1. Gather all memory layersRead CLAUDE.md and CLAUDE.local.md from the project root (if they exist). Your auto-memory content is already in your system prompt - review it there. Note which team memory sections exist, if any.**Success criteria**: You have the contents of all memory layers and can compare them.### 2. Classify each auto-memory entryFor each substantive entry in auto-memory, determine the best destination:| Destination | What belongs there | Examples ||---|---|---|| **CLAUDE.md** | Project conventions and instructions for Claude that all contributors should follow | "use bun not npm", "API routes use kebab-case", "test command is bun test", "prefer functional style" || **CLAUDE.local.md** | Personal instructions for Claude specific to this user, not applicable to other contributors | "I prefer concise responses", "always explain trade-offs", "don't auto-commit", "run tests before committing" || **Team memory** | Org-wide knowledge that applies across repositories (only if team memory is configured) | "deploy PRs go through #deploy-queue", "staging is at staging.internal", "platform team owns infra" || **Stay in auto-memory** | Working notes, temporary context, or entries that don't clearly fit elsewhere | Session-specific observations, uncertain patterns |**Important distinctions:**- CLAUDE.md and CLAUDE.local.md contain instructions for Claude, not user preferences for external tools (editor theme, IDE keybindings, etc. don't belong in either)- Workflow practices (PR conventions, merge strategies, branch naming) are ambiguous - ask the user whether they're personal or team-wide- When unsure, ask rather than guess**Success criteria**: Each entry has a proposed destination or is flagged as ambiguous.### 3. Identify cleanup opportunitiesScan across all layers for:- **Duplicates**: Auto-memory entries already captured in CLAUDE.md or CLAUDE.local.md → propose removing from auto-memory- **Outdated**: CLAUDE.md or CLAUDE.local.md entries contradicted by newer auto-memory entries → propose updating the older layer- **Conflicts**: Contradictions between any two layers → propose resolution, noting which is more recent**Success criteria**: All cross-layer issues identified.### 4. Present the reportOutput a structured report grouped by action type:1. **Promotions** - entries to move, with destination and rationale2. **Cleanup** - duplicates, outdated entries, conflicts to resolve3. **Ambiguous** - entries where you need the user's input on destination4. **No action needed** - brief note on entries that should stay putIf auto-memory is empty, say so and offer to review CLAUDE.md for cleanup.**Success criteria**: User can review and approve/reject each proposal individually.## Rules- Present ALL proposals before making any changes- Do NOT modify files without explicit user approval- Do NOT create new files unless the target doesn't exist yet- Ask about ambiguous entries - don't guess

Frequently asked questions

Remember