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

cua-volume

Save agent memory and outputs in Cua Volume, shared storage that persists beyond a Space, the working environment. Hand files to the user, read shared references, and check synchronization, version history, and conflicting edits.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Use Cua Volume, the one volume every Space and agent of this user shares. Inside a Space it is mounted as a folder (/volume on Linux, ~/Cua Volume on macOS), so any program reads and writes it directly. Use it for anything that must outlive this Space - your memory and outputs in your agent home, shared reference in public/ - and to hand files to the user or to other agents. Use when the user mentions the volume, Cua Volume, shared files, your home or memory, or saving results.

설치 방법 보기

이럴 때 유용합니다

  • Keep outputs after a working environment ends
  • Save agent memory for later work
  • Deliver files to the user
  • Check file sync status and conflicting edits

포함된 파일(1)

  • SKILL.md3.8 KB

SKILL.md(원문)

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

Cua Volume

One versioned volume per user. Every write is a new version; deletes keep history. The same files appear on the user's Mac (Finder) and in every Space, within seconds.

Where it is

Where you runPath
A Linux Space/volume (or ~/Cua Volume when /volume is absent)
A macOS Space~/Cua Volume
No mount (Windows for now, or the Space has none)use the volume_* tools below

Check that it is mounted, not just present: mountpoint -q /volume on Linux, ls ~/"Cua Volume" on macOS. A /volume holding only CUA-VOLUME-UNAVAILABLE.txt (read-only) is not the volume: the file says why (for example, a container without /dev/fuse). If it is not mounted, use the tools; nothing written to an unmounted folder is saved.

Layout and what you may do

FolderYou (an agent in a Space)
public/read only: shared reference from the user
agents/<you>/read and write: your home (memory, outputs/, inbox/)
spaces/<this space>/read and write: this Space's scratch and outputs
another agent's home, another Spacenot visible; ask with volume_request_access

Put results the user should see in agents/<you>/outputs/ (or this Space's folder) and tell them the path. A refused write means the folder is not yours: do not retry elsewhere to get around it, ask.

Tools (the cua MCP server)

ToolUse
volume_ls, volume_read, volume_writeThe same files without the mount; each file's sync state
volume_delete, volume_history, volume_restoreWhere offered: delete, old versions, restore one
volume_request_accessAsk the user for more (a folder, r or rw, and why); they approve in Cua
volume_sync_statusSync health, each device's last sync, your files still uploading, conflicts

Inside a Space these tools answer from the user's machine, so they show its view of sync, not only this Space's.

Sync and conflicts

  • A file another device just wrote can take a few seconds to arrive. Before relying on one, check volume_sync_status: feed is live (syncing), off (storage on this machine only: nothing to wait for) or offline (the bucket is unreachable, see last_error: say so rather than trust a stale file). devices shows when each device last synced.
  • volume_ls and volume_read mark a file with sync when it matters: pending_upload (not yet stored, other devices cannot see it yet), conflict (a write lost to a later one; kept at conflict_path), conflict_copy, and written_by when another device wrote it last.
  • Your own writes through the mount upload when you close the file (or after a moment without writes). Close files before telling the user they are ready.
  • When two devices change the same file, the later write wins and the other is kept next to it as name (conflict from <device> <date>).ext. Nothing is lost. Do not delete a conflict copy yourself: tell the user, or merge the two into the current file if the task asks for it.

Never put secrets in the volume

API keys, tokens, passwords and private keys belong in the user's Keyvault. Writes to agent homes are scanned; a write with a secret is refused (secret_detected) and logged. Do not work around the refusal: remove the secret.

리뷰

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

댓글

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

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

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

0 / 1,000자

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

같은 저장소의 스킬

Operate native apps on macOS, Windows, and Linux using identified controls, menu paths, or screen coordinates. Target a specific window, verify the result after each action, and consult available recent activity when resuming work.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Operate a specific app window
  • Click controls and enter text
  • Adjust window positions and sizes
trycua/cua3만2026년 10월 19일 업데이트

Create disposable Linux or macOS computers for running code, testing apps, operating desktop interfaces, and browsing websites. Use isolated environments locally or in the Cua cloud, then delete them when the work is complete.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Run code in an isolated environment
  • Test an app or reproduce an issue
  • Fill web forms and capture page screenshots
trycua/cua3만2026년 10월 19일 업데이트

Work in a local or remote computer environment whose screen you can watch. Run commands, transfer files, launch coding agents, move signed-in app sessions, and share the host computer’s network when needed.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Run tasks in an isolated environment you can watch
  • Transfer files into and out of a Space
  • Launch and monitor coding agents
trycua/cua3만2026년 10월 19일 업데이트

Operate apps and websites by inspecting screenshots, clicking controls, typing, and dragging. Use it to fill forms, check layouts, and test complete user flows, with recorded actions available for replay and review.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Fill forms and use file upload dialogs
  • Test buttons and complete user flows
  • Check layouts and capture screenshots
trycua/cua3만2026년 10월 19일 업데이트

jev-use

무료

Build a computer-control loop where Cua Driver observes and acts, while TypeSafe Jev chooses from predefined actions. Validate each choice, execute one action at a time, and verify the result before continuing.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Build a Jev integration for browser automation
  • Create action candidates for native desktop apps
  • Reject stale or unknown action choices
trycua/cua3만2026년 10월 19일 업데이트

Review open GitHub issues, proposals, and pull requests to identify useful maintainer work. Get ranked candidates with evidence, dependencies, and validation needs, then begin work only on an item you explicitly select.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Choose the next maintenance task
  • Prioritize a backlog for the available work window
  • Find pull requests that need review
trycua/cua3만2026년 10월 19일 업데이트

trycua의 스킬 모두 보기

이 스킬의 문제 신고