The body is almost entirely actionable commands with no concept padding, but it is ~1300 lines with notable redundancy — the environment-variable tables appear both in per-service config sections and again verbatim in the bottom 'Environment Variable Quick Reference', and troubleshooting content repeats across decision trees, per-service sections, playbooks, and common workflows. Not a 1 because it avoids explaining things Claude already knows; not a 3 because the duplication and length could be tightened substantially.

Throughout, guidance is concrete and copy-paste ready — e.g. 'harbor pull qwen3:4b && harbor up', 'harbor vllm args --max-model-len 4096', and explicit curl calls for the router API — matching the 'fully executable code/commands' anchor.

Multi-step processes are clearly sequenced with explicit validation checkpoints: decision trees branch on FAIL/OK, setup waits for 'Healthy' output, vLLM startup waits for 'Application startup complete', and troubleshooting playbooks are numbered with verify-then-fix feedback loops (e.g. 'docker logs harbor.<service>' → apply fix → 'harbor restart').

The skill is a single ~1300-line monolithic SKILL.md with no bundle files and no references split out — per-service CLI lists, config tables, and env-var references that belong in separate one-level-deep files are all inline. It is well-organized with clear headers (better than the score-1 wall of text) but matches the score-2 anchor where 'content that should be separate is inline'; the under-50-line simple-skill exception does not apply.

Names many concrete actions ("setting up and running local LLMs", "per-service configuration", "VRAM optimization", "GPU troubleshooting", "profiles, tunnels") rather than vague language, matching the 'lists multiple specific concrete actions' anchor.

Explicitly answers both what (Harbor-based local LLM setup covering Docker through advanced features) and when via an explicit "Use when user wants to run LLMs locally..." trigger clause, satisfying the 'clearly answers both what AND when' anchor.

Covers natural user-facing terms ("run LLMs locally", "Ollama", "Open WebUI", "llama.cpp", "vLLM", "SearXNG", "Open Terminal") that a user would actually say, matching the 'good coverage of natural terms' anchor.

A clear niche (Harbor / local LLM infrastructure) anchored by named tools and specific triggers makes it unlikely to fire for unrelated skills; the trailing "or similar local AI services" adds minor breadth but does not meaningfully raise conflict risk.