agentleFS
Sign inStart free
MasRamaMasRama/peka/skills/remember/SKILL.md

remember

Skill1 starsChanged 29 days agoMITView on GitHub

Keep something for future sessions in PEKA. PEKA decides whether it becomes a memory (facts, preferences, corrections) or a skill (procedures). Use when the user runs /peka:remember, asks you to remember or note something, corrects you, or teaches you how to do something.

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

5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 61 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If that is empty, use what the user just asked you to keep.

    line 13
  2. Very specific:

    If it says PEKA is not set up, tell the user to run /peka:setup and stop.

    line 22
  3. Very specific:

    Follow the instruction it prints: launch peka:learner with that prompt, putting the user's request in the Request: line in their own words, …

    line 23
  4. Distinctive:

    When it finishes, tell the user in one line what was saved and whether it became a memory, a skill, or both.

    line 26
  5. Distinctive:

    Do not write the memory or skill yourself.

    line 29

“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 this

What to keep: $ARGUMENTS

If that is empty, use what the user just asked you to keep. If it is still unclear, ask one short question first.

  1. Run:

    node "${CLAUDE_PLUGIN_ROOT}/scripts/peka.mjs" learn --session "${CLAUDE_SESSION_ID}" --mode decide

    If it says PEKA is not set up, tell the user to run /peka:setup and stop.

  2. Follow the instruction it prints: launch peka:learner with that prompt, putting the user's request in the Request: line in their own words, plus any details from this conversation the request depends on.
  3. When it finishes, tell the user in one line what was saved and whether it became a memory, a skill, or both.

Do not write the memory or skill yourself; the learner keeps the store consistent.

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