kortix-user-memory
Per-user memory in the user's own Drive folder: `/drives/me/Memory`. Who this user is, how they like to work, what they corrected, what they are working on — kept across every session they start, priv
SKILL.mdpackages/starter/templates/managed/skills/kortix-user-memory/SKILL.md
GitHub<skill name="kortix-user-memory">
<overview>
Each person in a Kortix workspace has their own folder in Drive,
`Users/<name>`, mounted in their sessions at `/drives/me` (and
`~/Desktop`). Kortix creates `/drives/me/Memory` in it. That folder is this
user's memory: what you keep about THIS person, read back in every session
they start.
- It is private to the user until they share their folder.
- It syncs with the Kortix web app (Drive → My files → Memory) within seconds. The user can read, edit and delete every file there.
- It is plain markdown. Use the file tools (
read,write,edit,bash). Memory/mykortix/in it is My Kortix's: one page per fact that My Kortix keeps with itskortix_memorytool. Read it if it helps; leave its files to My Kortix and the user.
User memory is not workspace or team memory. Where every other fact goes is
the one table in the kortix-drives skill (<memory>).
</overview>
/drives/me is the folder of the session's owner. In a session several
people use (a shared session, a channel thread), keep only the owner's facts
there. In a private channel's thread /drives/me is read-only: save nothing
there, and keep what you learn in the channel's memory (the
kortix-channel-memory skill). When /drives/me is absent (Volumes off for the workspace, or no
personal folder in /drives/README.md), there is no user memory: do not
write one anywhere else, and tell the user if they asked you to remember
something.
</protocol>
Create a file the first time it has content, not before. Add a new
kebab-case file when one topic outgrows its file. Keep MEMORY.md in sync,
one line per file:
- [preferences.md](preferences.md) — short answers, tables over prose, EU date format
Create the folder if it is missing: mkdir -p /drives/me/Memory.
</layout>
Keep
- Who they are: role, team, what they own, their expertise level.
- How they want you to work: tone, length, format, language, tools, "always / never" rules they state.
- Corrections: what you did wrong and what to do instead, with the reason they gave. A confirmed approach counts too ("yes, exactly like that").
- Ongoing work: goals, deadlines, the thing they come back to every
week. Convert "next Friday" to
YYYY-MM-DD. - Pointers: where their things live (a dashboard, a folder in Drive, a channel), never the content behind them.
Drop
- Secrets, passwords, tokens, API keys, card numbers. Those go in the Kortix Secrets Manager.
- Anything that is only about this conversation.
- Facts the repo, Drive or a connector already holds — point to them.
- Guesses about the user. Store what they said or did, not what you infer about their personality, health, beliefs or private life.
- Team and channel facts. Save them where the
kortix-drivestable says.
Style
- One fact per bullet. Short, present tense, specific.
- Date facts that go stale:
(2026-10-19). - Update an existing bullet instead of adding a near-duplicate.
- Delete a bullet that turned out wrong.