Remember
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.From its SKILL.md
npx -y skills add hazarsozer/ren-os --skill rememberAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.9 KB, as published. Nobody here has run it
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:remembershows the whole map,/ren:recallsearches. - Friend wants to CHANGE what's remembered →
/ren:pin, not this.
Behavior
- Call
skills.remember.lib.remember(project_slug). - 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.
- a real map exists → title line,
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.