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.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-structured CLI reference with executable commands and complete examples, strong on actionability and workflow sequencing. Its main weakness is progressive disclosure: it is a single monolithic file with no references to deeper materials, and a couple of prose sections could be tightened.

Suggestions

Split the bulkier reference material (Compose File Extensions, full multi-service examples, Image Tag Templates) into one-level-deep reference files under ./references/ and link to them from a concise overview section, so SKILL.md acts as a navigable hub rather than a monolithic reference.

Consolidate the overlapping 'How It Works' prose and 'Core Concepts' bullets into a single tight section to remove the minor redundancy.

Add an explicit validation/verification step to destructive operations — e.g. after `uc service rm` or `uc deploy --recreate`, note checking `uc service ls` / `uc service inspect` to confirm the intended state — so destructive workflows have a feedback checkpoint.

Dimension	Reasoning	Score
Conciseness	The body is a lean, table-and-code-driven reference that assumes competence and avoids explaining generic concepts Claude already knows, but the "How It Works" prose paragraph partially overlaps the "Core Concepts" bullet list, leaving minor instances of over-explanation that could be trimmed — the score-4 anchor rather than the fully-lean score-5.	4 / 5
Actionability	It provides copy-paste-ready `uc` commands with concrete flags, complete port-publishing tables, and full executable compose YAML examples covering the common cases (multi-service deploy, external-device proxy, placement, image tagging), matching the score-5 anchor for fully executable guidance.	5 / 5
Workflow Clarity	Multi-step processes like the external-device routing flow are clearly numbered with an explicit verify step ("3. Verify: uc caddy config"), and zero-downtime deploy describes the built-in health-check gate; however destructive single commands (uc service rm, uc deploy --recreate) lack an explicit validation/verification checkpoint, a minor gap that keeps it at score 4 rather than 5.	4 / 5
Progressive Disclosure	There are no bundle files and no external references at all — the ~340-line detailed CLI reference is inlined monolithically in SKILL.md with good section headers but no signaling to deeper one-level-deep materials, matching the score-3 anchor where content that could live in separate files is inlined.	3 / 5
	Total	16 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description with an explicit Use-when trigger and a comprehensive enumeration of concrete actions tied to a distinct niche. The only minor gap is a few natural trigger terms (compose files, containers) that round out the vocabulary users would actually say.

Dimension	Reasoning	Score
Specificity	The description enumerates multiple concrete actions — "deploying services, configuring Caddy ingress, adding static proxy routes for non-cluster devices, publishing ports, scaling, inspecting logs, or managing machines and volumes" — giving comprehensive coverage of the skill's capabilities, matching the score-5 anchor rather than the score-4 anchor which expects minor gaps.	5 / 5
Completeness	It opens with an explicit "Use when managing an Uncloud cluster — ..." trigger clause and pairs it with a concrete list of what the skill does via the `uc` CLI, clearly and explicitly answering both what and when with concrete trigger phrases per the score-5 anchor.	5 / 5
Trigger Term Quality	It surfaces natural terms a cluster operator would say ("deploying services", "scaling", "inspecting logs", "publishing ports", "Caddy ingress", "uc CLI") with good synonym coverage, but omits common phrasings like "compose file" / "docker compose" and "containers" that users would naturally say, so it falls just below the comprehensive score-5 anchor.	4 / 5
Distinctiveness Conflict Risk	The niche is tightly scoped to Uncloud clusters and the `uc` CLI with Caddy-specific triggers, making it clearly distinguishable from other skills with minimal conflict risk, matching the score-5 anchor.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/uncloud/SKILL.md
Commit: d8409a4

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.