// Use when the user uploads a project file and you see `<UploadedFile>` in the message. Use when user says "看看這個專案", "分析程式碼", "check this project", "what's in this upload", or asks about the structure of an uploaded file.
| name | zeabur-file |
| description | Use when the user uploads a project file and you see `<UploadedFile>` in the message. Use when user says "看看這個專案", "分析程式碼", "check this project", "what's in this upload", or asks about the structure of an uploaded file. |
Always use
npx zeabur@latestto invoke Zeabur CLI. Never usezeaburdirectly or any other installation method. Ifnpxis not available, install Node.js first.
When the user's message contains <UploadedFile>upload_id</UploadedFile>, extract the upload_id from inside the tag.
# 1. Pull the uploaded project to a local directory
npx zeabur@latest file pull <upload_id> /tmp/project -i=false
# 2. Explore with standard bash tools
ls /tmp/project
cat /tmp/project/package.json
find /tmp/project -name "*.ts" -o -name "*.js" | head -20
# Download all files from an upload to a local directory
npx zeabur@latest file pull <upload_id> [target-dir] -i=false
. (current directory)npx zeabur@latest file pull <upload_id> /tmp/project -i=falsels -la /tmp/project and find /tmp/project -type fcat /tmp/project/package.json (or go.mod, requirements.txt, Cargo.toml)Dockerfile if presentsrc/main.*, index.*, app.*)zeabur-deploy skill| Tip | Details |
|---|---|
| Binary files are skipped | Images, fonts, archives won't be downloaded |
| Use a temp directory | Pull to /tmp/project to keep the workspace clean |
| Use standard tools | After pulling, grep, find, wc, cat all work normally |
Use when debugging services on a user's dedicated server via SSH. Use when needing to inspect pods, check container logs, view k8s resources, or run kubectl commands on the server. Use when "service exec" is insufficient and you need server-level access. Use when user says "check my server", "debug pod", "kubectl", "SSH into server", "check k8s", or "inspect cluster".
Use when deploying a local project or codebase to Zeabur. Use when the user says "deploy this", "deploy to Zeabur", "deploy from GitHub", "search my repos", or "find my repository". Default to direct deploy unless the user explicitly asks for Git-based deployment.
Use when modifying service config without full redeploy. Use when updating env vars and restarting single service. Use when user says "change env var", "update config", "fix variable without redeploying", "upgrade service version", "update image tag", or "change service tag".
Use when deploying a database to Zeabur. Use when user needs MySQL, PostgreSQL, MongoDB, or Redis. Use when user says "I need a database", "add database", "deploy postgres", "set up MySQL", "add Redis", "add MongoDB", or "connect to database". Also use when user mentions data persistence issues like "data lost after restart", "data not saved", "data disappears", "need persistent storage for data", or "how to persist data". Also use when integrating a database with an existing service.
Use when deploying object storage (S3-compatible) to Zeabur. Use when user needs MinIO, RustFS, or S3-compatible storage. Use when user says "object storage", "file storage", "S3", "MinIO", "RustFS", "upload files", "store files", "blob storage", or "OSS". Also use when integrating object storage with an existing service.
Use for ALL Zeabur environment variable operations — create, list, update, delete, or troubleshoot. Use when user says "set env var", "add variable", "create variable", "update variable", "delete variable", "change env var", or "why is my variable empty". Also use when variables are empty or SERVICE_NOT_FOUND errors.