agentleFS
Sign inStart free
usernameisthebestofthebestusernameisthebestofthebest/claude-recap/skills/remember/SKILL.md

remember

Skill2 starsChanged 9 months agoMITView on GitHub

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.

69 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use agent-context-isolation, agentica-infrastructure and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 61 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask the user which scope using AskUserQuestion:

    line 24
  2. Distinctive:

    Run the remember script:

    line 35
  3. Distinctive:

    If the user's intent is ambiguous, ask for clarification before writing

    line 50
  4. Distinctive:

    Do NOT remember session-specific or temporary information (e.g., "I'm debugging auth today")

    line 51

“Common” is measured: kept by at least 6 in 10 of the 61 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. 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
  1. Get the plugin scripts path from the SessionStart injection in your context: Plugin scripts path: /path/to/scripts
  2. 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 saysDistilled 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)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free