Record useful facts from a channel or direct message in its shared Markdown memory, then load relevant notes at the start of later threads. Keep information organized by topic and respect who can read or edit each memory folder.
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 thread in a channel or DM, when the user says remember / note / you should know, and when you learn something the next thread there should know.
Run score Not tested
See how to installThis skill records facts from channel and direct message conversations that later threads should know, then loads relevant notes when a related conversation begins. It separates channel, direct message, and company memories according to where they are stored and who can read them. Each topic gets its own file, while MEMORY.md serves as an index with a short description of each file. Before editing an existing file, the skill rereads it and changes only the lines it added.
Use it to keep decisions made in a channel available to future threads, or to organize information someone asked you to remember in a direct message. It also helps when you need to find information across conversations and save it in a memory location that matches its sharing scope.
People can read and edit the same memory files. Respect the access scope of each location, including channel and DM folders. Do not save secrets, passwords, keys, or tokens.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).
Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 28, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
| 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 |
| Company | /drives/company/Memory/ | every member, every thread |
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. Company memory and the
user's folder are read-only in its threads. Never copy what you learn there
into Company memory, 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.md is 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
---
# Pricing
Set updated_by and updated_at on every save. List a fact from outside
the thread (a web page, an email, a file, a connector) under sources:
with its label and url. Keep every key you did not write.
Notes.md holds 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 Company folder. Keep them
in the DM folder from a DM thread, or in /drives/me/Memory/ (the
kortix-user-memory skill).
To forget a fact, delete its line, or the file when nothing is left, and
its MEMORY.md line.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Review Slack access requests against Okta role and team information, then prepare narrowly scoped GitHub or AWS IAM permissions. Apply changes only after an eligible person's approval and record the grant, reasoning, approver, and timestamp.
Research companies and people before outreach or meetings. Combines business profiles, recent news, hiring signals, and key contacts into a sourced brief with talking points and suggested questions, adding relationship history when CRM data is connected.
Review daily Google Ads and Meta Ads results for budget pacing, declining performance, and unusual activity. Get prioritized findings with supporting numbers and concrete recommendations for a marketing team to assess and carry out.
Automate website tasks such as navigating pages, filling forms, clicking buttons, taking screenshots, and extracting data. The skill also supports web app testing, with specialized guides for Electron desktop apps, Slack, and cloud browsers.
Process emailed vendor invoices by extracting details, comparing them with purchase orders and invoice history, and recording duplicates, overcharges, or missing orders. Summarize results in Slack for human review; payment approval and execution remain with people.
Guide changes to Kortix billing code, admin controls, and pricing screens. Explain how plans, trials, enterprise contracts, and access exceptions should work, where pricing is defined, and which audited routes must handle account changes.