homelab-vlan-segmentation

Segmenting home networks into VLANs for IoT, guest, trusted, and server traffic using UniFi, pfSense/OPNsense, and MikroTik — including switch trunk config, firewall rules, and wireless SSID mapping.

Quality

76%

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-vlan-segmentation/SKILL.md

Quality

Content

77%

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

The body is highly actionable with executable commands and clear validation checkpoints across all three platforms, but it is somewhat verbose and monolithic, explaining concepts Claude already knows and inlining per-platform detail that could be split into reference files.

Suggestions

Trim introductory explanations of concepts Claude already knows (flat-network risks, trunk vs access port definitions) to lean on Claude's competence.

Move the per-platform configuration blocks (UniFi, pfSense/OPNsense, MikroTik) into separate reference files and link to them from SKILL.md for progressive disclosure.

Reduce duplication between the VLAN design template, the 'How It Works' diagram, and the worked example scenario.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete templates and commands, but it restates concepts Claude already knows (e.g. what trunk vs access ports are, what a flat network is) and the example scenario plus repeated design tables add length that could be trimmed.	2 / 3
Actionability	Provides fully executable vendor-specific commands for UniFi, pfSense/OPNsense, and MikroTik plus a copy-paste-ready VLAN design template and SSID mapping, matching the 'fully executable code/commands; copy-paste ready' anchor.	3 / 3
Workflow Clarity	Sequenced steps per platform with explicit validation checkpoints ('Apply changes in a maintenance window and verify connectivity between segments after each step', 'Test isolation after every rule change', 'MUST come before the RFC1918 block rule'), satisfying the feedback-loop requirement for risky network changes.	3 / 3
Progressive Disclosure	Content is well-organized into clear sections, but everything is inline in a single monolithic SKILL.md with no bundle files or one-level-deep references — the per-platform configurations and examples are candidates for separate reference files that are not present.	2 / 3
	Total	10 / 12 Passed

Description

75%

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, trigger-rich, and clearly distinct, but it omits an explicit 'Use when...' clause, so the 'when to use' guidance is only implied rather than stated. Adding a trigger clause would lift completeness to full marks.

Suggestions

Append an explicit trigger clause such as 'Use when setting up or troubleshooting VLAN isolation on UniFi, pfSense/OPNsense, or MikroTik.'

Mention inter-VLAN routing or firewall troubleshooting explicitly in the description to surface a common user phrasing.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'switch trunk config', 'firewall rules', and 'wireless SSID mapping' — paired with specific vendors (UniFi, pfSense/OPNsense, MikroTik), matching the 'multiple specific concrete actions' anchor.	3 / 3
Completeness	It clearly answers 'what' (segmenting networks into VLANs with trunk config, firewall rules, SSID mapping) but lacks an explicit 'Use when...' trigger clause, so 'when' is only implied — capping completeness at 2 per the guidelines.	2 / 3
Trigger Term Quality	Covers natural terms a user would say — 'VLANs', 'IoT', 'guest', 'UniFi', 'pfSense', 'MikroTik' — giving good coverage of vocabulary users actually invoke, matching the 'good coverage of natural terms' anchor.	3 / 3
Distinctiveness Conflict Risk	The niche is clearly distinct — VLAN segmentation for homelabs with named vendor platforms — making it unlikely to trigger for unrelated skills, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	11 / 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-vlan-segmentation/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.