How do I install the Remember skill?

Run npx skillmds@latest add hatawong/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. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. 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?

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

Remember by hatawong — Agent Skill

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

Remember

Use when the user wants to persistently remember something across sessions (e.g., "always use bun", "never auto-commit", "my name is Alex"). Also use when you detect a clear user preference or constraint worth persisting.

hatawong Updated Sep 10, 2026

File contents

remember

Overview

Saves a user preference, constraint, or fact to REMEMBER.md so it persists across sessions. The user chooses scope (global or project).

When to Use

User explicitly says "remember...", "always...", "never...", "don't forget..."
User states a clear preference or constraint worth persisting (e.g., "I use bun not npm")
User provides identity or context info they'd want every session to know

Instructions

Distill what the user wants to remember into one concise line (imperative form, no filler).
- Good: "Use bun instead of npm for all package management"
- Bad: "The user mentioned they prefer bun over npm and would like us to always use it"
Ask the user which scope using AskUserQuestion:

Which scope should this apply to?
- Global: applies to all projects
- Project: applies only to this project

Get the plugin scripts path from the SessionStart injection in your context: Plugin scripts path: /path/to/scripts
Run the remember script:

bash "<plugin_scripts_path>/remember.sh" "<scope>" "<content>"

Where:

plugin_scripts_path: the path from SessionStart injection
scope: global or project
content: the distilled one-liner (quote it properly for shell)

Rules

One entry per invocation — don't batch multiple items
Distill to a clear imperative statement, not a description of what happened
If the user's intent is ambiguous, ask for clarification before writing
Do NOT remember session-specific or temporary information (e.g., "I'm debugging auth today")

Examples

User says	Distilled entry
"Remember I always use bun"	`Use bun instead of npm for package management`
"Never auto-commit without asking"	`Never auto-commit; always ask before committing`
"My name is Alex"	`User's name is Alex`
"For this project, always run tests with --verbose"	`Run tests with --verbose flag` (project scope)

---name: rememberdescription: Use when the user wants to persistently remember something across sessions (e.g., "always use bun", "never auto-commit", "my name is Alex"). Also use when you detect a clear user preference or constraint worth persisting.---# remember## OverviewSaves a user preference, constraint, or fact to REMEMBER.md so it persists across sessions. The user chooses scope (global or project).## When to Use- User explicitly says "remember...", "always...", "never...", "don't forget..."- User states a clear preference or constraint worth persisting (e.g., "I use bun not npm")- User provides identity or context info they'd want every session to know## Instructions1. Distill what the user wants to remember into **one concise line** (imperative form, no filler). - Good: "Use bun instead of npm for all package management" - Bad: "The user mentioned they prefer bun over npm and would like us to always use it"2. Ask the user which scope using AskUserQuestion:```Which scope should this apply to?- Global: applies to all projects- Project: applies only to this project```3. Get the **plugin scripts path** from the SessionStart injection in your context: `Plugin scripts path: /path/to/scripts`4. Run the remember script:```bashbash "<plugin_scripts_path>/remember.sh" "<scope>" "<content>"```Where:- `plugin_scripts_path`: the path from SessionStart injection- `scope`: `global` or `project`- `content`: the distilled one-liner (quote it properly for shell)## Rules- One entry per invocation — don't batch multiple items- Distill to a clear imperative statement, not a description of what happened- If the user's intent is ambiguous, ask for clarification before writing- Do NOT remember session-specific or temporary information (e.g., "I'm debugging auth today")## Examples| User says | Distilled entry ||---|---|| "Remember I always use bun" | `Use bun instead of npm for package management` || "Never auto-commit without asking" | `Never auto-commit; always ask before committing` || "My name is Alex" | `User's name is Alex` || "For this project, always run tests with --verbose" | `Run tests with --verbose flag` (project scope) |

Frequently asked questions