Individual skill

memory

Persist and retrieve agent memory across sessions — recall via the three-stage protocol (structure route → semantic search → navigation fallback), read via memory_load, see the wiki structure via memory_browse, write well-placed pages via memory_write (including section-level append/rewrite), maintain via memory_curate. Use whenever the user asks to remember/forget something, when you need to look up past decisions or context, or when episodic state matters beyond the current turn. Primary surface is the NATIVE memory_* tools (a `prismer memory` CLI appendix exists for code agents running in a shell).

sdk/cloud/catalog/skills/memory/SKILL.md

Read pinned source

Source commit f83b859a173802a73d978197e92328ab2bf57a6e

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 3, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,364
Repository last updated
Oct 22, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Memory

For an explicitly requested Markdown wiki artifact, read
`references/llm-wiki/GUIDE.md` relative to this skill. Its schema, provenance,
contradiction and lint workflow operates only in the user-selected project/vault;
it does not replace the platform memory tools or create a default home wiki.

Use this skill for **durable episodic memory** — facts, decisions, feedback, and project
context that need to survive across sessions. Memory has four canonical types: `user`,
`feedback`, `project`, `reference`. Pages live at semantic paths and are organized as a
wiki: an `INDEX.pkf` at the top, **hub** pages per topic, and **leaf** pages under hubs.

**Richness is the goal.** A memory page should be complete enough that a future session
works FROM the page instead of re-reading the raw file or the internet. There is no