Conciseness

Dense operator-grade facts with zero explanation of concepts Claude already knows — no cloud-server tutorials, no library intros — and every line carries non-obvious behavior ("MTU is 1450", "rebuild wipes the disk but keeps all IPs", "Grow-only, online"). Matches the lean 'every token earns its place' anchor; not 4 because no padded or over-explained passage stands out.

Actionability

Copy-paste-ready commands cover the common cases: orphan sweeps ("hcloud volume list -o json | jq -r '.[] | select(.server==null) | .name'"), an in-place resize chain with --keep-disk, fstab options ("discard,nofail"), and IaC fixes ("ignoreChanges: [\"userData\"]", "firewall.id.apply(Number)"). Matches the fully-executable 5 anchor; not 4 because concrete commands exist for every subsection.

Workflow Clarity

The provisioning workflow is a numbered 5-step sequence with explicit per-step "Checkpoint" validation (e.g. "firewall rules list SSH restricted to admin IPs, never 0.0.0.0/0"), a pre-data "Gate" on protection, and a recovery loop for broken cloud-init (fix template, rebuild). Matches the explicit-validation-with-error-recovery 5 anchor; the destructive-ops cap does not apply since validation is present.

Progressive Disclosure

Sections are well organized with a clear one-level References table of external links, but the single-file body (~90 lines) is denser than a lean overview and the "**deployment** capability skill" reference has no resolvable path. Fits the 4 anchor (good structure, minor organization gaps); not 5 because navigation to sibling material is vague.

Specificity

Names concrete capabilities across every Hetzner resource type ("servers, volumes, private networks, firewalls, backups and snapshots") and both tooling paths ("hcloud CLI or Pulumi/Terraform"), matching the comprehensive multi-action 5 anchor like the PDF extract/fill/merge/convert example. Not 4 because coverage spans the whole domain with no evident gaps.

Completeness

Explicitly answers both: what ("Hetzner Cloud servers, volumes, private networks, firewalls, backups and snapshots, through the hcloud CLI or Pulumi/Terraform") and when ("Use when provisioning, resizing or scripting Hetzner resources, or choosing a server type"). Mirrors the 5 anchor's what+when structure with concrete trigger phrases; not 4 because the when-clause is fully explicit.

Trigger Term Quality

Includes the natural terms users would actually say: "Hetzner", "hcloud", "provisioning", "resizing", "server", "volume", "firewall", "backup", "snapshot", "server type", plus Pulumi/Terraform. Not 4 because no commonly-said variation of significance is missing — the brand names dominate how users refer to this need.

Distinctiveness Conflict Risk

A clear niche anchored on brand-specific triggers ("Hetzner", "hcloud", "Pulumi/Terraform") that no generic cloud or deployment skill would match. Minimal conflict risk; not 4 because there is no meaningful overlap with adjacent skills.