kortix-channel-memory
Memory of a channel or DM thread: Markdown files in the channel's `Memory/` folder (or, in a DM, `/drives/me/Memory/<agent>/`), the same files people see in the Memory tab. Load at the start of a thre
Файлы1
Открыть в GitHubSKILL.mdpackages/starter/templates/managed/skills/kortix-channel-memory/SKILL.md
GitHub<skill name="kortix-channel-memory">
<folders>
A thread in a channel or a DM has memory: Markdown files in Drive. People
read and edit the same files in the channel's or DM's Memory tab. Nothing is
copied: what you write is what they see, and the reverse.
| Memory | Folder | Who reads it |
|---|---|---|
| This channel | the channel's Memory/ folder (/drives/README.md names its path) |
every member, every thread of the channel; a private channel: only its members |
| This DM | /drives/me/Memory/<your agent name>/, beside the user's own memory in /drives/me/Memory/ |
only the user |
The turn's system prompt lists the files of each folder this thread reads, by title and path. A folder marked "not mounted in this thread" is not yours: do not write its facts anywhere else; tell the user.
In a private thread in a channel, the list can show the user's DM memory with you: read it, but save to it only from the DM.
In a private channel (/drives/README.md says so), the channel's Memory/
is the only place you save, team facts included. Every other folder,
the user's included, is read-only in its threads. Never copy what you learn there
into another folder, another channel or anywhere outside the channel.
</folders>
One topic per file.
# <Title>is the first line: a person ("Priya"), a decision, a workstream ("Q4 launch"), a playbook. Add to the file of that topic when it exists; make a new file for a new topic.Folders by type (optional):
people/,decisions/,workstreams/,playbooks/, e.g.people/priya.md. Lowercase file names,-between words.MEMORY.mdis the index of the folder: one line per file,- [Title](path) — one-line summary. Update it with every new file.Front-matter (optional, at the very top), so the Memory tab shows who saved it and where it came from:
--- updated_by: <your agent name> (agent) updated_at: 2026-10-24T17:00:00Z sources: - label: Pricing call notes url: https://example.test/notes --- # PricingSet
updated_byandupdated_aton every save. List a fact from outside the thread (a web page, an email, a file, a connector) undersources:with itslabelandurl. Keep every key you did not write.Notes.mdholds sentences people saved with "Remember this", one line each:- <text> — <name>, <date>. File each line into the right topic file, then delete that line.Read a file just before you edit it, and change only your lines: people and other threads edit the same files.
Facts only. Never a secret, a password, a key or a token.
Never a person's private facts in a channel or a shared folder. Keep them in the DM folder from a DM thread, or in
/drives/me/Memory/(thekortix-user-memoryskill).To forget a fact, delete its line, or the file when nothing is left, and its
</save>MEMORY.mdline.
| Ask | Command |
|---|---|
| rename the channel | kortix spaces rename "<name>" |
| describe it | kortix spaces describe "<text>" |
| see it | kortix spaces get |
| add a tab | kortix spaces tabs add <file|folder|artifact|app|link> "<title>" <ref> |
| remove or move a tab | kortix spaces tabs rm <id|title>, kortix spaces tabs move <id|title> <position> |
| set its agents | kortix spaces agents set <name>... (the first is its default) |
| add or remove people | kortix spaces members add <email>..., kortix spaces members rm <email> |
| post news or a question in the space's main chat | kortix spaces post [<space>] "<text>" (a new top-level message from you) |
| post into one of its threads | kortix spaces post [<space>] "<text>" --thread <thread id> (add --ask when that thread's agent must answer) |
| tag people or agents | write @name, @email or @agent in the text: a person in the space gets a notification |
- A page for a tab: write a
.mdor self-contained.htmlfile in this space's files folder, then add afiletab whose ref is its Drive path (/Company/Channels/<slug>/<file>;kortix spaces getshows the slug). - A 403 means the person may not make that change (only a channel's creator or a workspace manager renames, describes and sets agents; a member adds people). Tell the user in one line; never work around it.
- A space's main chat is its shared feed: post what others there should
know, a question for a person, or a request that needs someone; tag them.
<space>is#slugfor a channel ordm:<agent>for the person's DM. You post only where the person you work for may post; their DM only from a private session of theirs. - Making a channel private, creating a channel or joining one is the user's own step in the web app.</configure>