본문으로 건너뛰기
cccskills
무료GitHub에 공개

kortix-user-memory

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.

kortix-ai/suna
설치 방법 보기

이럴 때 유용합니다

  • Keeping response preferences across sessions
  • Remembering corrections to the agent's approach
  • Carrying ongoing goals and deadlines into future tasks
  • Removing details the agent should forget

포함된 파일(1)

  • SKILL.md5.0 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

<skill name="kortix-user-memory"> <overview> Each person in a Kortix project has their own folder in Files, `Users/<name>`, mounted in their sessions at `/drives/me` (and `~/Desktop`). Kortix creates `/drives/me/Memory` in it. That folder is this user's memory: what you keep about THIS person, read back in every session they start.
  • It is private to the user until they share their folder.
  • It syncs with the Kortix web app (Drive → My drive → Memory) within seconds. The user can read, edit and delete every file there.
  • It is plain markdown. Use the file tools (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>

<protocol> 1. **Start of a task for a person: read the index.** `cat /drives/me/Memory/MEMORY.md`. Then read only the files it points at that matter for the task. Nothing is injected into your prompt: if you do not read it, you work without it. 2. **Use it.** Apply the preferences and corrections without being asked again. Do not recite the memory back to the user. 3. **Write when something durable shows up** (rubric below). Write it in the same turn: your context can reset at any time. 4. **Say it in one line.** After a write: "Saved to your memory: <fact>." After a delete: "Removed from your memory: <fact>." 5. **Forget on request.** "Forget X" deletes the entry and its index line. Never keep a copy elsewhere.

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

<layout> ``` /drives/me/Memory/ ├── MEMORY.md Index. Read first. One line per file. ├── profile.md Role, team, expertise, time zone, languages. ├── preferences.md Tone, formats, tools, defaults they want. ├── feedback.md Corrections and confirmed approaches, each with the why. └── work.md Ongoing work, goals, deadlines (absolute dates). ```

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>

<rubric>

Keep

  • Who they are: role, team, what they own, their expertise level.
  • How they want you to work: tone, length, format, language, tools, "always / never" rules they state.
  • Corrections: what you did wrong and what to do instead, with the reason they gave. A confirmed approach counts too ("yes, exactly like that").
  • Ongoing work: goals, deadlines, the thing they come back to every week. Convert "next Friday" to YYYY-MM-DD.
  • Pointers: where their things live (a dashboard, a folder in Files, a channel), never the content behind them.

Drop

  • Secrets, passwords, tokens, API keys, card numbers. Those go in the Kortix Secrets Manager.
  • Anything that is only about this conversation.
  • Facts the repo, Files or a connector already holds — point to them.
  • Guesses about the user. Store what they said or did, not what you infer about their personality, health, beliefs or private life.
  • Team facts. Those are project memory (kortix-memory).

Style

  • One fact per bullet. Short, present tense, specific.
  • Date facts that go stale: (2026-10-19).
  • Update an existing bullet instead of adding a near-duplicate.
  • Delete a bullet that turned out wrong.
</rubric> <gotchas> - **Two sessions, one file.** The user may run several sessions at once. Read the file just before you edit it, and change only your lines. A clash leaves a `(conflict ...)` copy beside the file (the `kortix-drives` skill): tell the user, do not delete it. - **The user's edits win.** A file the user changed in the web app is the truth. Do not restore what they removed. - **Shared folder = shared memory.** A user who shares their folder in Files shares `Memory/` with it. Keep it to work facts. - **Small files.** The index stays under ~40 lines and each file under ~200. Split or prune before that. </gotchas> </skill>

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

access-policy

무료

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/suna2만2026년 10월 20일 업데이트

account-research

무료

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/suna2만2026년 10월 20일 업데이트

ad-performance-review

무료

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/suna2만2026년 10월 20일 업데이트

agent-browser

무료

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/suna2만2026년 10월 20일 업데이트

ap-invoice-match

무료

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/suna2만2026년 10월 20일 업데이트

billing

무료

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/suna2만2026년 10월 20일 업데이트

kortix-ai의 스킬 모두 보기

이 스킬의 문제 신고