kortix-drives
The project's Files under `/drives`: the user's own folder (their desktop, also at `~/Desktop`) and the folders shared with you, synced with the Kortix web app and every other session. Load before you
SKILL.mdpackages/starter/templates/managed/skills/kortix-drives/SKILL.md
GitHub<skill name="kortix-drives">
<overview>
**Files** is the project's shared folder tree. It lives outside this sandbox,
syncs both ways within seconds with the Kortix web app and with every other
session that mounts it, keeps a version history, and outlives this session.
Each folder under `/drives` is one folder of Files that this session may use;
everything else on this machine is session scratch.
/drives/README.md is the live map for THIS session: which folders are
mounted, where, read-only or read-write, and any open conflicts. Kortix
rewrites it whenever access changes. Read it first; never edit it.
</overview>
- Look in
/drives/mefor the user's context before you ask them for it. - Save files you make for the user in
/drives/me. - Keep what you learn about the user in
/drives/me/Memory: load thekortix-user-memoryskill for the protocol. Keep what the whole team should know inCompany/Memorywhen it is mounted. - You see only folders someone shared. If you need another folder, ask the user to share it with you in Files.
- Access can change while you run. Re-read
/drives/README.mdwhen a path you expected is missing or refuses writes.</layout>
- Tell the user about a conflict copy that touches your work.
- Do not delete or rename a conflict copy on your own. Merge the two versions only when the user asks.
- SQLite databases are kept whole: a conflicting
app.dbarrives asapp (conflict ...).db.</conflicts>
| Command | What it does |
|---|---|
kortix drive ls [<path>] |
List a folder (default: the top of Files) |
kortix drive cat <path> |
Print a file |
kortix drive put <local> <path> |
Upload a local file |
kortix drive mkdir <path> |
Create a folder |
kortix drive mv <from> <to> |
Move or rename |
kortix drive rm <path> [-r] |
Delete a file, or a folder with -r |
kortix drive access <path> |
Who has access to a folder, with grant ids |
kortix drive share <path> (--everyone | --user <email> | --agent <name>) [--write] |
Share a folder (read, or write) |
kortix drive unshare <path> <grantId> |
Stop one share |
- Every command takes
--json. kortix driveworks only in the user's own private session. In a shared, chat or scheduled session it answers 403: use the folders mounted in the session, or ask the user to make the change in Files.</commands>