homelab-network-setup

Practical home and homelab network planning for gateways, switches, access points, IP ranges, DHCP reservations, DNS, cabling, and common beginner mistakes.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/homelab-network-setup/SKILL.md

Quality

Content

87%

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

A lean, highly actionable self-contained planning skill with concrete values and clean sectioning; its main gap is the absence of explicit validation/verification checkpoints in the workflow, which caps workflow clarity at 2.

Suggestions

Add explicit validation checkpoints to the Examples, e.g. after the Beginner Upgrade steps: 'Verify DNS resolves (ping nas.home.arpa) and confirm no secondary router is handing out DHCP.'

Include a short 'verify your plan' checklist (check for overlapping subnets, confirm gateway/DNS settings propagated, test inter-VLAN rules once enabled) to turn the design sequence into a feedback-looped workflow.

Dimension	Reasoning	Score
Conciseness	The body is lean throughout, assumes Claude's networking competence (it never defines VLAN/DHCP/DNS), and every section earns its place with practical specifics like the home.arpa rationale and the 192.168.1.0/24 VPN-conflict note.	3 / 3
Actionability	Despite being instruction-only with no shell commands, it gives concrete, copy-pasteable values (192.168.10.0/24 subnets, .1 gateway convention, .2-.49 reservations, .50-.240 DHCP pool, nas.home.arpa names) and specific recommendations, which the rubric rewards for actionable instruction-only skills.	3 / 3
Workflow Clarity	A clear design sequence exists ('How It Works' top-down roles then IP plan/DHCP/DNS/cabling) and the Examples are numbered steps, but there are no explicit validation checkpoints or verify-and-retry feedback loops, leaving checkpoints implicit.	2 / 3
Progressive Disclosure	The skill is self-contained with no bundle files and is organized into clearly signaled sections (When to Use, How It Works, IP Plan, DHCP And DNS, Cabling And Wi-Fi, Examples, Anti-Patterns, See Also); the only cross-references are one-level sibling-skill pointers in See Also.	3 / 3
	Total	11 / 12 Passed

Description

72%

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

The description is specific and well-stocked with natural trigger terms in a clear niche, but it lacks an explicit 'Use when...' clause, which caps completeness, and it leans on a single action verb rather than enumerating multiple concrete actions.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when planning a new home/homelab network, choosing gateway/switch/AP roles, or designing IP, DHCP, and DNS layouts.'

Lead with concrete action verbs (design, lay out, reserve, configure) instead of the single verb 'planning' to lift specificity toward the anchor-3 bar.

Dimension	Reasoning	Score
Specificity	It enumerates many concrete domain objects ('gateways, switches, access points, IP ranges, DHCP reservations, DNS, cabling') but relies on a single action verb ('planning'), so it names the domain and some actions rather than listing multiple distinct concrete actions like the anchor-3 example (extract, fill, merge).	2 / 3
Completeness	The 'what' is clearly stated ('Practical home and homelab network planning for...'), but there is no explicit 'Use when...' trigger clause, so 'when' is only implied and completeness is capped at 2 per the rubric guidelines.	2 / 3
Trigger Term Quality	Natural trigger terms a user would actually say are well covered: 'home', 'homelab', 'network', 'gateways', 'switches', 'access points', 'IP ranges', 'DHCP reservations', 'DNS', 'cabling'.	3 / 3
Distinctiveness Conflict Risk	The 'home and homelab network planning' niche with its specific equipment and protocol triggers is clearly distinct and unlikely to fire for unrelated skills such as interface health or config validation.	3 / 3
	Total	10 / 12 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/homelab-network-setup/SKILL.md
Commit: 754b8dd

Reviewed: 2 days 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.