$ loading_
Manage Uncloud clusters for deployment, ingress, scaling, and operations troubleshooting.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "uncloud" skill from askskill: 1. Download https://raw.githubusercontent.com/affaan-m/ECC/main/skills/uncloud/SKILL.md 2. Save it as ~/.claude/skills/uncloud/SKILL.md 3. Reload skills and tell me it's ready
Using the uc CLI, help me deploy myapp to an Uncloud cluster, publish port 8080 publicly, and provide the full commands with explanations.
Provides deployment and port publishing commands, plus execution order and verification steps.
I want to configure a Caddy domain ingress for the api service in the cluster and add a static proxy route for a non-cluster device. Generate the uc CLI steps.
Gives ingress and proxy route commands, including example domains and validation steps.
Help me scale the worker service to 5 replicas, view the latest 200 log lines, and explain how to confirm the scaling succeeded.
Outputs scaling and log inspection commands, with success indicators and troubleshooting advice.
Reference for the uc CLI — a decentralised self-hosting platform using Docker containers, WireGuard mesh networking, and Caddy reverse proxy.
Use this skill when working with Uncloud clusters, especially when:
uc machineuc deployx-caddy, x-ports, or --caddyfileUncloud runs Docker services across peer machines connected by a WireGuard mesh. Each machine is an equal cluster member; services communicate on the overlay network and Caddy runs globally to terminate public HTTP/HTTPS traffic. Compose files can use Uncloud extensions for ingress, placement, and generated Caddy configuration, while the uc CLI handles image distribution, scheduling, scaling, logs, and cluster state.
uc machine init user@host --name machine-1
uc service run --name web -p app.example.com:8080/https nginx:latest
uc deploy
10.210.0.0/16 by default; DNS provided inside the meshx-caddy / --caddyfile instead| Command | Purpose |
|---|---|
uc machine init user@host | Bootstrap first machine / new cluster |
uc machine add user@host | Join machine to existing cluster |
uc machine ls | List machines |
uc machine update NAME --public-ip IP | Update public IP for ingress |
uc machine rm NAME | Remove machine |
Key init flags: --name, --network 10.210.0.0/16, --no-caddy, --no-dns, --public-ip auto\|IP\|none
| Command | Purpose |
|---|---|
uc service ls / uc ls | List services |
uc service run IMAGE | Run a single container service |
uc deploy | Deploy from compose.yaml |
uc deploy --no-build | Deploy already-pushed images without rebuilding |
uc deploy --recreate | Force service recreation |
uc scale SERVICE N | Set replica count |
uc service logs SERVICE | View logs |
uc service exec SERVICE | Shell into container |
uc service inspect SERVICE | Detailed info |
uc service rm SERVICE | Remove service (keeps named volumes) |
uc ps | All containers across cluster |
uc image push myapp:latest # Push local image to all machines
uc image push myapp:latest -m machine1,machine2 # Push to specific machines
uc images # List images in cluster
uc volume ls # All volumes
uc volume ls -m machine1 # On specific machine
uc volume create NAME -m MACHINE
uc volume rm NAME
uc caddy config # Show current generated Caddyfile (read-only)
uc caddy deploy # Deploy/upgrade Caddy across cluster
uc dns show # Show reserved *.uncld.dev domain
uc dns reserve # Reserve a new domain
uc ctx ls # List cluster contexts
uc ctx use prod # Switch context
-p [hostname:]container_port[/protocol]
| Example | Meaning |
|---|---|
-p 8080/https | HTTPS with auto service-name.cluster-domain hostname |
-p app.example.com:8080/https | HTTPS with custom hostname |
-p 8080/http | HTTP only, no TLS |
-p [host_ip:]host_port:container_port[/protocol]@host
…
Handle returns, refunds, fraud checks, and warranty claim decisions efficiently.
Use Bun for runtime, bundling, testing, packages, and Node migration decisions.
Use the correct Ethereum Keccak-256 hashing in Node.js and TypeScript.
Apply Nuxt 4 patterns for SSR safety, performance, and data fetching.
Generate images, videos, and audio with one unified AI media workflow.
Design Quarkus 3 backend patterns for messaging, APIs, data, and async workflows.
Manage UniFi devices, status, and configs through a human-friendly CLI and TUI.
Manage UniFi networks, devices, and cameras through natural language commands.
Connect AI to UniFi controllers for network monitoring, querying, and control.
Manage Python environments, dependencies, and requirements through uv with LLM assistance.
Manage UniFi devices, configs, security policies, and QoS through MCP.
Unify multiple MCP servers into one endpoint with filtering and automated management.