Uncloud Cluster Management
Manage an Uncloud cluster with Muse: deploy services from Compose files, configure Caddy ingress, publish ports, inspect logs, and manage machines and volumes with the `uc` CLI.
- What
- Manage an Uncloud cluster with Muse: deploy services from Compose files, configure Caddy ingress, publish ports, inspect logs, and manage machines and volumes with the `uc` CLI.
- Cost
- Free
- Needs
- Docker installed and running — that is a system prerequisite of the tool (the `uc` CLI drives Docker on each machine), and I install it myself if it is missing. The `uc` CLI itself is installed in the steps below, from the official psviderski/uncloud releases (or Homebrew). No account is needed to install; a real machine, cluster, and domain only matter later, when I actually use it.
- Level
- Intermediate — Docker installed and running…
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a reference for managing Uncloud clusters, a decentralised self-hosting platform running Docker containers over a WireGuard mesh with Caddy as reverse proxy. No central control plane: every machine is an equal cluster member, services communicate on the overlay network (10.210.0.0/16 by default, DNS inside the mesh), and Caddy runs globally to terminate public HTTP/HTTPS traffic with auto-obtained Let's Encrypt TLS. Deploy services from Compose files with `uc deploy`, run one-off services with `uc service run`, publish HTTP, HTTPS, TCP or UDP ports through Uncloud, configure Caddy ingress with `x-caddy`, `x-ports` or `--caddyfile` (the Caddyfile is autogenerated, never edit it directly), add static proxy routes for non-cluster LAN devices, bootstrap or join machines with `uc machine init` / `uc machine add`, and inspect logs, service state, volumes, DNS and machine placement. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: you need the `uc` CLI installed and machines that can run Docker; this is real self-hosting with real machines on a real network, so broken networking means unreachable services, test changes on one machine first. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Uncloud Cluster Management is a free Muse skill that helps your Muse manage an Uncloud cluster, deploying services from Compose files, configuring Caddy ingress, publishing ports, inspecting logs, and managing machines and volumes with the uc CLI. Uncloud is a decentralised self-hosting platform running Docker containers over a WireGuard mesh, with Caddy terminating public traffic with auto-obtained Let's Encrypt TLS.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 4eb71d9Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: Docker installed and running — that is a system prerequisite of the tool (the `uc` CLI drives Docker on each machine), and I install it myself if it is missing. The `uc` CLI itself is installed in the steps below, from the official psviderski/uncloud releases (or Homebrew). No account is needed to install; a real machine, cluster, and domain only matter later, when I actually use it. Install "Uncloud Cluster Management" for me. It is the reference and workflow skill for managing an Uncloud cluster with the `uc` CLI: deploying services, configuring Caddy ingress, publishing ports, scaling, and inspecting logs, machines, and volumes across machines joined by a WireGuard mesh. Repository: https://raw.githubusercontent.com/affaan-m/ECC/4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2/skills/uncloud/SKILL.md Pinned version: install the code at commit 4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file from the repository path into a temporary folder and look inside. 2. Integrity check: Skill Harbor reviewed this listing on 2026-10-10 and recorded the fingerprint below. I want you to compute the SHA-256 of the downloaded file and compare: - SKILL.md: SHA-256 cc2383ca4459a686ccda87ac08b2a1953028d91076e6a83f29e4c99de5f2fb7f If a fingerprint does not match, I want you to stop before installing and tell me the files changed since Skill Harbor's review, so the new version is unverified. Show me your safety findings and give me three choices: (a) wait for Skill Harbor to re-review the listing (recommended), (b) analyze the new files in detail first and then decide, (c) install anyway knowing the risk. Then wait for my answer before doing anything else. 3. Safety check: I want to see your findings explicitly, in short separate items: - every network address the code contacts (expected: none from the skill file itself, which is plain Markdown guidance; the `uc` binary installed below comes only from the official psviderski/uncloud GitHub releases. When the skill is used later, `uc` talks to my own machines and to the cluster) - every shell command it runs (expected: none during the skill installation; the CLI install below downloads and extracts one release archive) - every place credentials, API keys or personal data are read, stored or sent (expected: none during installation; cluster access later relies on my own SSH keys, which stay on my machine) - any obfuscated or encoded code (expected: none in the skill file — plain Markdown text) If anything looks suspicious, stop and explain it to me before continuing. 4. Confirmation: before installing, give me a short summary of what the skill does plus your safety findings, and wait for my explicit "yes, install". 5. Install it as a skill: copy SKILL.md into the agent's skills directory, in a folder named "uncloud". Then install the `uc` CLI: from the latest release at github.com/psviderski/uncloud/releases (v0.21.0 at the time of this review), download the archive for my operating system and architecture (uc_linux_amd64.tar.gz, uc_linux_arm64.tar.gz, uc_macos_amd64.tar.gz, or uc_macos_arm64.tar.gz) together with the release's checksums.txt, verify the archive's SHA-256 against checksums.txt before extracting anything, and put the `uc` binary somewhere on my PATH (for example ~/.local/bin). With Homebrew, `brew install psviderski/tap/uncloud` is an accepted alternative. 6. Verify with no network calls: frontmatter valid, the skill file in place, and the `uc` CLI answers (uc --help or uc version) without contacting anything. 7. Report what was installed, where, and what I still need to do myself (for example: make sure Docker is installed and running; creating or joining a cluster — `uc machine init user@host` with a real machine, and the domain and DNS that go with it — needs real infrastructure and is deliberately not part of this installation). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
- It can download and install software packages.
What the scan found — excerpts from the install prompt
- installs packages — 5. Install it as a skill: copy SKILL.md into the agent's skills directory, in a folder named "uncloud". Then i · 5. Installe-le comme un skill : copie SKILL.md dans le répertoire des skills de l'agent, dans un dossier nommé
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 4eb71d9 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 21, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : installs packages
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.