eve-lab-topology-discovery

Gathers requirements and options for EVE-NG network topology design through structured discovery questions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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."

Frequently Asked Questions about eve-lab-topology-discovery

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

FAQPage Schema
How do I plan an EVE-NG lab topology before building it?

Start by clarifying topology type, scale, hierarchy, routing protocol, and redundancy targets. This Skill asks only the missing questions, then summarizes answers into a connectivity matrix, required links list, and resilience declaration before any design begins.

What images should I use for EVE-NG network labs?

Use Cisco IOL L3 for routers, IOL L2 for switches, and VPCS for hosts as lightweight defaults. Choose vEOS-lab, vMX, or NX-OSv 9000 when platform-specific behavior matters, keeping in mind their heavier RAM footprints.

Which routing protocol fits a campus versus service provider lab?

OSPF single area fits campus and small WAN labs, while eBGP suits WAN edges and inter-DC designs. IS-IS is appropriate for service provider cores, and static routes only work for tiny stub labs without failover needs.

When should I use leaf-spine instead of a three-tier design?

Use leaf-spine for data center labs beyond very small scale, with no leaf-to-leaf or spine-to-spine links. Three-tier or collapsed core designs fit enterprise campus labs, with collapsed core reserved for small environments.

What are the limitations of this discovery skill?

It only covers the requirements and options phase and does not generate topologies or configurations. It will not produce a generic design before topology type and scale are known, and it limits questioning to five questions per turn.