What problem does it solve?
Network lab requests are often vague or incomplete, leading to poorly designed EVE-NG topologies. This Skill structures the requirements-gathering phase so topology type, scale, routing, redundancy, and image choices are clarified before any design work begins.
Core Features & Use Cases
- Guided Discovery: Asks only the missing questions from a curated question bank, never more than five per turn, covering topology type, scale, hierarchy, routing, redundancy, images, resources, and scope.
- Labeled Defaults and Trade-offs: Offers explicit defaults (OSPF single area, IOL images, single-link tolerance) and option tables comparing L2 vs L3 access, routing protocols, and fabric styles.
- Requirements Artifacts: Summarizes gathered input into a connectivity matrix, required links list, and resilience declaration.
- Use Case: A user says "build me a data center lab." The Skill asks about scale, leaf-spine vs three-tier, redundancy targets, and available RAM, then recommends vEOS or NX-OSv images before any topology is proposed.
Quick Start
Ask the assistant to help scope an EVE-NG lab by describing your rough idea, such as "I want a small campus lab with redundant distribution switches."