Skip to content
cccskills
FreePublished on GitHub

kortix-drives

Guide file storage and context retention in Kortix shared folders. Identify accessible folders, save lasting outputs, keep user and team notes across sessions, and handle conflicting file copies according to the documented sharing and synchronization rules.

OriginalShow the original description

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 read or save a file the user should keep, look for the user's notes, preferences or context, keep memory across sessions, or when you see a file named `... (conflict <date> <time>)...`.

kortix-ai/suna
See how to install

Good for

  • Saving outputs for use after the session ends
  • Reusing user notes and preferences across sessions
  • Keeping shared context for the team
  • Checking access permissions and conflicting file copies

Files included (1)

  • SKILL.md3.0 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

<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>

<layout> | Path | What it is | Access | | --- | --- | --- | | `/drives/me` (and `~/Desktop`) | the user's own folder, `Users/<name>` in Files | read-write | | `/drives/me/Memory` | what you keep about this user across sessions | read-write | | `/drives/company` | the project's shared `Company` folder, with `Company/Memory` for what the whole team should know | as shared | | `/drives/<name>` | any other folder shared with you, this agent or this user | as shared |
  • Look in /drives/me for 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; keep what the whole team should know in Company/Memory when 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.md when a path you expected is missing or refuses writes. </layout>
<conflicts> When two writers change the same file at the same time, nothing is lost: one version stays at the path and the other is saved beside it as `<name> (conflict <date> <time>)<ext>`. Kortix tells the user in the web app.
  • 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.db arrives as app (conflict ...).db. </conflicts>
<limits> - A file written here is visible elsewhere within seconds, not instantly. Avoid two sessions editing one file at once. - Writes go through `sync`/close like any disk: close files you write. - Do not put secrets or credentials in Files: other people with access to a folder read the same files. - A session mounts a limited number of folders. Folders that did not fit are listed in `/drives/README.md`; tell the user rather than look for them. </limits> </skill>

Reviews

No reviews yet. Tell others what you thought.

Comments

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.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

access-policy

FreeSummary

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.

  • Reviewing GitHub repository access requests from Slack
  • Preparing AWS IAM permissions for a specific task
  • Routing sensitive access requests for additional review
kortix-ai/suna20.3KUpdated Oct 18, 2026

account-research

FreeSummary

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.

  • Research a prospective customer before outreach
  • Prepare background information for meeting attendees
  • Compare a competitor's products and positioning
kortix-ai/suna20.3KUpdated Oct 18, 2026

ad-performance-review

FreeSummary

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.

  • Checking whether campaign budgets are being spent on schedule
  • Investigating rising acquisition costs or falling ad returns
  • Finding ads and keywords that spend without converting
kortix-ai/suna20.3KUpdated Oct 18, 2026

agent-browser

FreeSummary

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.

  • Automate form entry and page navigation
  • Capture screenshots and extract page data
  • Explore web apps for bugs
kortix-ai/suna20.3KUpdated Oct 18, 2026

ap-invoice-match

FreeSummary

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.

  • Checking incoming invoices against purchase orders
  • Finding duplicate invoices and likely resends
  • Reviewing unit prices and remaining order balances
kortix-ai/suna20.3KUpdated Oct 18, 2026

billing

FreeSummary

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.

  • Update billing logic and its specification together
  • Review how trials and enterprise contracts are handled
  • Find the code that defines prices and allowances
kortix-ai/suna20.3KUpdated Oct 18, 2026

See all skills by kortix-ai

Report a problem with this skill