Keeps work preferences, corrections, and ongoing goals in a personal Kortix folder so agents can refer to them across sessions. Users can inspect, edit, or delete the saved Markdown files and request specific details be forgotten.
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, private to them. Load at the start of a task for a person, when the user says remember / forget / you should know, when they correct how you work, or when you learn a durable fact about them.
Review the instructions the agent will receive before you install.
read, write, edit, bash).
The memory tool covers only the project brain at memory/, not this
folder.User memory is not project memory. Facts the whole team needs go in the
project brain (memory/, the kortix-memory skill) or in Company/Memory
when it is mounted (the kortix-drives skill).
</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. When /drives/me is absent (Volumes off for the project, 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>
YYYY-MM-DD.kortix-memory).(2026-10-19).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.