How to use the Remember agent skill: organise session knowledge

What is an agent skill?

An agent skill is a packaged set of instructions that an AI agent can load when a task matches it. The skill is defined in a file named SKILL.md, which describes when to use the skill and how the agent should work through it.

The remember skill comes from the oh-my-claudecode project (Yeachan-Heo/oh-my-claudecode, MIT licence) and is listed here as skills/remember. Its only file is SKILL.md.

What the remember skill makes the agent do

When you ask the agent to preserve what was learned in a session, the skill tells it to gather the relevant findings and classify each one as a durable project fact, a temporary working note, an operator preference or instruction, or duplicate, stale or conflicting information.

The agent then proposes a destination for each item. The skill names four memory surfaces: project memory for durable team knowledge, a notepad priority store for short high-signal context, a notepad working store for temporary active-session notes, and docs or AGENTS/CLAUDE files for durable instructions and conventions when they truly belong there. It writes only to the appropriate surface and finishes by listing what was stored, where, and any duplicates or conflicts to clean up.

• Do not dump everything into one store.
• Prefer project memory for durable team knowledge.
• Prefer the notepad for short-lived working context.
• Keep entries concise and actionable.
• If something is uncertain, mark it as uncertain rather than storing it as fact.

How to install the remember skill

Option 1: download the ZIP from the skill's page on this site and unzip it into your personal skills folder, ~/.claude/skills/. The skill folder should contain SKILL.md.

Option 2: unzip it into a project's .claude/skills/ folder so that only that project uses the skill.

Option 3: in the Claude apps, upload the ZIP under Settings → Capabilities → Skills.

How to trigger the skill with natural requests

You do not need a special command. The skill is meant for requests where you want session knowledge preserved or organised. Describe what you want kept in plain language, and mention the outcome you expect.

Good requests name the kind of result: that you want findings saved, sorted, or checked for conflicts. The skill also covers the case where you want existing notes reviewed for stale or contradictory entries.

• Save what we learned about the test setup in this session to the right memory place.
• Organise the findings from today's debugging into project memory and notepad as appropriate.
• Review our existing convention notes and flag anything stale or conflicting.
• Preserve the decisions we made about the API design so the next session has them.

Examples of what the agent will do

Suppose a session uncovered that the build needs a specific environment variable, the team prefers a particular naming pattern, and a debugging workaround only matters for the next few turns. Under this skill, the agent should classify these separately: the build requirement and naming convention are durable project facts, and the workaround is temporary working context.

The skill also asks the agent to mark uncertain items rather than store them as fact. If a finding conflicts with a note already in memory, the agent should call out the conflict in its summary so you can resolve it.

What the skill needs and whether it runs code

The item page lists no requirements. The skill runs no scripts and makes no network calls, according to the listing. Its single file, SKILL.md, is a set of written instructions for the agent.

Safety notes before you use it

Review what is written. The agent may store uncertain items or put them in the wrong place, and unchecked writes can clutter or mislead future sessions. Read the proposed destinations and the summary of what was stored.

Keep secrets out of memory. The skill does not explain how sensitive content is filtered, so do not put passwords, keys or other sensitive data into memory files.

Skip it for one-off tasks. If nothing needs to persist, the memory writes add clutter with no lasting benefit.

Tips for getting good results

Ask for the skill at the end of a session, when the useful findings are clear. Keep entries short, and ask the agent to mark anything it is unsure about. For team projects, review convention files before they are committed so that they stay concise and accurate.

• Ask for conflicts to be listed, not silently resolved.
• Periodically ask for a review of stale notes.
• Keep the memory files under version control if your team shares them.