Agent skill · software engineering · affaan-m
uncloud
Use when managing an Uncloud cluster — deploying services, configuring Caddy ingress, adding static proxy routes for non-cluster devices, publishing ports, scaling, inspecting logs, or managing machines and volumes with the `uc` CLI.
Why this skill is useful
Provides specific commands and workflows for managing Uncloud clusters that the AI wouldn't reliably generate on its own.
What it needs
Requires docker installed locally. About 5k tokens when loaded. Last updated 2026-08-06. 238,342 stars on the source repository.
What this skill does
Uncloud Cluster Management Reference for the uc CLI — a decentralised self-hosting platform using Docker containers, WireGuard mesh networking, and Caddy reverse proxy. When to Activate Use this skill when working with Uncloud clusters, especially when: Bootstrapping or joining machines with uc machine Deploying services from Compose files with uc deploy Publishing HTTP, HTTPS, TCP, or UDP ports through Uncloud Configuring Caddy ingress with x-caddy, x-ports, or --caddyfile Routing external LAN devices through the cluster proxy Inspecting logs, service state, volumes, DNS, or machine placement How It Works Uncloud 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. Examples Core Concepts No central control plane — all machines are equal peers connected by WireGuard Caddy runs as a global service on every machine; auto-obtains TLS from Let's Encrypt Overlay network — services communicate via 10.210.0.0/16 by default; DNS provided inside the mesh Caddyfile is autogenerated — never edit it directly; use x-caddy / --caddyfile instead --- CLI Quick Reference Machines 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 Services 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 depl …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills affaan-m/uncloud--db841e