eve-lab-topology-validation

Validates EVE-NG topology designs against decision gates, checklists, and build-plan rules.

650|182|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/automateyournetwork/netclaw --skill eve-lab-topology-validation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eve-lab-topology-validation
Source: https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/eve-lab-topology-validation
Command: npx skills add https://github.com/automateyournetwork/netclaw --skill eve-lab-topology-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Network engineers designing EVE-NG labs often skip structured QA, leading to orphan nodes, broken adjacencies, missing redundancy, and failed builds. This Skill enforces a final validation and delivery phase so topology designs are checked against explicit gates before any implementation begins.

Core Features & Use Cases

  • Decision Gate Enforcement: Blocks build work until ten prerequisites are confirmed, including finalized node and link lists, image availability, and host resource fit.
  • Structured Validation Checklists: Runs structural, role/adjacency, resilience, and protocol checks, reporting PASS, WARN, or FAIL plus an overall resilience rating.
  • Standardized Design Output: Produces the required nine-section deliverable covering requirements, physical and logical topology, build plan, and open risks.
  • Use Case: Before building a leaf-spine lab in EVE-NG, run this Skill to confirm spine nodes connect only to leaf nodes, verify no orphan nodes exist, and generate the ordered 13-step build plan.

Quick Start

Ask the AI to validate your EVE-NG topology design and produce the final design output with a build readiness assessment.

Frequently Asked Questions about eve-lab-topology-validation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate an EVE-NG topology design before building it?

Run the decision gate first to confirm the node list, link list, redundancy level, image availability, and host capacity are all finalized. Then apply the structural, adjacency, resilience, and protocol checklists, stating PASS, WARN, or FAIL for each area.

What checks should a network topology QA process include?

A thorough topology QA covers structural checks like orphan nodes and connected graphs, role and adjacency rules such as spine-to-leaf-only links, resilience checks for articulation points and redundancy symmetry, and protocol checks for routing coverage and black holes.

What should a final network design deliverable contain?

The required output has nine sections: requirement summary, best-practice recommendations, image and platform recommendations, physical topology, logical/protocol topology, design validation check, build plan, configuration plan if requested, and risks with open questions.

When should build work be blocked during lab design?

Build work must not be approved while any decision-gate items remain unresolved, such as unconfirmed scope, missing image availability, or unchecked host resource fit. Unresolved items go into the final risks and open-questions section rather than being silently skipped.

What is the correct order for building an EVE-NG lab?

The build plan follows thirteen ordered steps: verify the lab, confirm images, check host capacity, create and verify nodes, map interfaces, create network objects, connect interfaces, verify topology, run the UNL validator, start nodes, apply startup configs, and verify connectivity.