agentleFS
Sign inStart free
hazarsozerhazarsozer/ren-os/skills/remember/SKILL.md

remember

Skill2 starsChanged 2 months agoMITView on GitHub

Use when the friend wants to see what the system remembers about a project (or the wiki overall) — "what do you remember about X", "show me my project memory." Triggers on the /ren:remember [project] slash command. Renders the L2 map in human prose, not a raw markdown dump. The cheapest trust-builder in the scope (spec §3.8 A-10) — read-only, always.

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

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

  • 0

    Common

    Most of the 61 edited versions we read keep these.

  • 2

    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:

    no slug and nothing to show at all → what IS known (identity set up?

    line 60
  2. Distinctive:

    Never raises. There is no failure mode here that should ever look like a crash to the friend — worst case is "I don't have memory for that …

    line 62

“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

"Show me what you remember about this project" — spec §3.8 A-10's cheapest trust-builder. Read-only, always: this skill never proposes, approves, applies, or otherwise touches the write-queue. It only reads an already-written L2 map and renders it as prose a friend can actually read, instead of a raw markdown dump of frontmatter and bullet-pointer syntax.

When to use this skill

  • Friend invokes /ren:remember [project-slug] — with a slug, the named project's map; without one, the master wiki index.
  • Friend asks in plain language: "what do you remember about <project>", "show me my project memory", "what do you know about this wiki."

When NOT to use this skill

  • Friend wants to look up something SPECIFIC (a decision, a lesson) → /ren:recall <query>, not this — /ren:remember shows the whole map, /ren:recall searches.
  • Friend wants to CHANGE what's remembered → /ren:pin, not this.

Behavior

  1. Call skills.remember.lib.remember(project_slug).
  2. Print the result verbatim. It already handles every case:
    • a real map exists → title line, Knowledge:/Decision map:/Recent log: sections in prose (decision pointers drop their (write_id) — that's provenance plumbing, not something a friend needs to see), and a footer with counts.
    • the map is quarantined (unreviewed, auto-generated by /ren:ingest-project) → a prominent warning line, before anything else.
    • an unknown project slug → a friendly one-line pointer to /ren:ingest-project//ren:bootstrap-project.
    • no slug and nothing to show at all → what IS known (identity set up? how many global pages?) plus how to get started.

Never raises. There is no failure mode here that should ever look like a crash to the friend — worst case is "I don't have memory for that yet," never a traceback.

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