Architecture
nteract/nteract
Architecture and documentation framing for cross-cutting repo decisions, docs taxonomy placement, ADRs, memos, PRDs, implementation plans, audits, measurements, runbooks, and source-grounded…
Entry point for designing EVE-NG network labs: classifies the request, gathers missing requirements, proposes options and validates the resulting topology.
Install EVE-NG Lab Topology Design
$ npx skills add automateyournetwork/netclaw --skill eve-lab-topology-design -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install automateyournetwork/netclaw eve-lab-topology-design --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/workspace/skills/eve-lab-topology-design .claude/skills/eve-lab-topology-design && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "eve-lab-topology-design" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/eve-lab-topology-design into .claude/skills/eve-lab-topology-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eve-lab-topology-design", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/eve-lab-topology-designType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add automateyournetwork/netclaw --skill eve-lab-topology-design -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install automateyournetwork/netclaw eve-lab-topology-design --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .agents/skills && cp -r skills-src/workspace/skills/eve-lab-topology-design .agents/skills/eve-lab-topology-design && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "eve-lab-topology-design" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/eve-lab-topology-design into .agents/skills/eve-lab-topology-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eve-lab-topology-design", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add automateyournetwork/netclaw --skill eve-lab-topology-design -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install automateyournetwork/netclaw eve-lab-topology-design --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/workspace/skills/eve-lab-topology-design .cursor/skills/eve-lab-topology-design && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "eve-lab-topology-design" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/eve-lab-topology-design into .cursor/skills/eve-lab-topology-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eve-lab-topology-design", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/automateyournetwork/netclaw.git --path workspace/skills/eve-lab-topology-design--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add automateyournetwork/netclaw --skill eve-lab-topology-design -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install automateyournetwork/netclaw eve-lab-topology-design --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/workspace/skills/eve-lab-topology-design .gemini/skills/eve-lab-topology-design && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "eve-lab-topology-design" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/eve-lab-topology-design into .gemini/skills/eve-lab-topology-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eve-lab-topology-design", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install automateyournetwork/netclaw eve-lab-topology-designInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add automateyournetwork/netclaw --skill eve-lab-topology-design -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .github/skills && cp -r skills-src/workspace/skills/eve-lab-topology-design .github/skills/eve-lab-topology-design && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "eve-lab-topology-design" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/eve-lab-topology-design into .github/skills/eve-lab-topology-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eve-lab-topology-design", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add automateyournetwork/netclaw --skill eve-lab-topology-design -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install automateyournetwork/netclaw eve-lab-topology-design --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/workspace/skills/eve-lab-topology-design .opencode/skills/eve-lab-topology-design && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "eve-lab-topology-design" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/eve-lab-topology-design into .opencode/skills/eve-lab-topology-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eve-lab-topology-design", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
eve-lab-topology-design- GitHub stars
- 677
- Token cost
- ~612 tokens
- SKILL.md length
- 274 words
- Files
- 5 (incl. scripts, references)
- Skills in repo
- 120
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Entry point for designing EVE-NG network labs: classifies the request, gathers missing requirements, proposes options and validates the resulting topology.
- Works in 7 steps: Classify the request: campus,… → If requirements are incomplete, read… → Summarize requirements and assumptions… → …
- Planning a new EVE-NG lab before building it
- SKILL.md covers Core workflow, Guardrails, When to read references and Failure Behavior
- Runs Python scripts from its folder
What it does
This skill is the starting point for EVE-NG topology work. It classifies the request as campus, branch or WAN, ISP or service provider, data center or hybrid, reads a discovery reference to ask only for missing requirements, summarizes requirements and assumptions, presents options with trade-offs and recommends one design. The design is delivered as both a physical topology and a logical or protocol topology.
Before a design counts as complete, it runs the QA structure from the validation reference, and any `.unl` file that exists or gets built is checked with `scripts/validate_unl_topology.py`. Guardrails: no building or configuring while requirements are vague, work at the physical, logical and lab-platform layers, state assumptions, add protocols only when requested, chosen or labeled as assumptions, and match icons to device roles. On tool errors it reports them instead of guessing, and it checks state before retrying anything that changes state.
When your agent uses it
- Planning a new EVE-NG lab before building it
- Reviewing an EVE-NG topology design or lab architecture
- Producing a build plan for a lab with structured requirements and validation
Example prompts
- “Design an EVE-NG lab for a two-site branch WAN with redundant uplinks.”
- “Review this lab topology and check the .unl file against the validator.”
- “I need a build plan for a data center lab; ask me what is missing first.”
Requirements
- An EVE-NG environment for building labs
- Python 3 to run the .unl topology validator
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Classify the request: campus, branch/WAN, ISP/SP, data center, or hybrid.
- If requirements are incomplete, read {baseDir}/references/discovery-workflow.md and gather only the missing details.
- Summarize requirements and assumptions before proposing a design.
- Present relevant options and trade-offs; recommend one design.
- Produce both the physical topology and the logical/protocol topology.
- Before calling the design complete, read {baseDir}/references/validation-workflow.md and run the required QA structure.
- If a .unl exists or is built, validate it with {baseDir}/scripts/validate_unl_topology.py and the notes in…
What it can do on your machine
Read from SKILL.md and the folder at commit f943637. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
EVE-NG Lab Topology Design loads about 612 tokens when it runs, and up to ~2.5k if it reads all its reference files. Until then it costs about 71 tokens; SKILL.md has 274 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from automateyournetwork/netclaw at commit f943637, republished under its Apache-2.0 licence (© automateyournetwork). 274 words, ~612 tokens.
Download SKILL.mdSave it as
.claude/skills/eve-lab-topology-design/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- eve-lab-topology-design
- description
- Design EVE-NG lab topology and coordinate the design workflow. Use when the user asks for lab design, architecture advice, topology planning, design review, or a build plan, especially when requirements, trade-offs, or validation need to be structured first.
EVE Lab Topology Design
Use this skill as the entrypoint for EVE-NG topology design work.
Core workflow
- Classify the request: campus, branch/WAN, ISP/SP, data center, or hybrid.
- If requirements are incomplete, read
{baseDir}/references/discovery-workflow.mdand gather only the missing details. - Summarize requirements and assumptions before proposing a design.
- Present relevant options and trade-offs; recommend one design.
- Produce both the physical topology and the logical/protocol topology.
- Before calling the design complete, read
{baseDir}/references/validation-workflow.mdand run the required QA structure. - If a
.unlexists or is built, validate it with{baseDir}/scripts/validate_unl_topology.pyand the notes in{baseDir}/references/unl-validator.md.
Guardrails
- Never jump into build or config when requirements are vague.
- Work at three layers every time: physical topology, logical/protocol topology, and lab/platform capability.
- State assumptions explicitly.
- Do not include protocols or services unless requested, chosen, or clearly labeled as assumptions.
- Match icons and platform choices to the actual device role.
When to read references
- Read
{baseDir}/references/discovery-workflow.mdfor question flow, defaults, design options, domain guidance, and image selection. - Read
{baseDir}/references/validation-workflow.mdfor output sections, QA gates, build-plan rules, and topology checks. - Read
{baseDir}/references/unl-validator.mdwhen you need validator usage, expected outputs, or requirements-file schema.
Failure Behavior
- On a tool error (timeout, unreachable host, malformed response), report the failure and its error message directly to the user rather than fabricating or guessing at results.
- For a confirmed read-only call, check connectivity and retry once if appropriate. For any call that changes state or sends a message, a timeout does not prove the action failed: inspect current state or delivery status before retrying, preserve the required approval/change gates, and do not repeat an action whose outcome is unknown.
© automateyournetwork, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (scripts, references) in workspace/skills/eve-lab-topology-design of automateyournetwork/netclaw.
- SKILL.md
- references/discovery-workflow.md
- references/unl-validator.md
- references/validation-workflow.md
- scripts/validate_unl_topology.py
Open the folder on GitHubat commit f943637
Compare with similar skills
EVE-NG Lab Topology Design next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| EVE-NG Lab Topology Design this skillautomateyournetwork/netclaw | 677 | — | ~612 | Automated safety check: Pass | Apache-2.0 | |
| Architecturenteract/nteract | 180 | — | ~497 | Automated safety check: Pass | BSD-3-Clause | |
| NIC Task Planningnginx/kubernetes-ingress | 5.1k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Rfc Writermohitagw15856/pm-claude-skills | 1.4k | — | ~4.1k | Automated safety check: Pass | MIT | |
| N Agentic Harnesses CodexNateBJones-Projects/OB1 | 4.7k | — | ~2k | Automated safety check: Pass | Custom licence | |
| Executing Plans Inlineobra/superpowers | 297k | 2 repos | ~5.1k | Automated safety check: Pass | MIT |
Similar skills
NIC Task Planning
nginx/kubernetes-ingress
Plans a change to the NGINX Ingress Controller before any code: acceptance criteria, security impact, affected layers, invariants, test surface and an ordered file list.
Rfc Writer
mohitagw15856/pm-claude-skills
Write an engineering RFC (Request for Comments) for a technical decision, architectural change, or significant implementation approach.
N Agentic Harnesses Codex
NateBJones-Projects/OB1
Designs, evaluates, and improves agentic harnesses for developer tools, assistants, workflow runtimes, copilots, and AI-powered products.
Executing Plans Inline
obra/superpowers
Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.
Monitor CI
nrwl/nx
Monitor Nx Cloud CI pipeline and handle self-healing fixes. An agent skill from nrwl/nx.
More from automateyournetwork/netclaw
All 120 skills in this repoACI Policy Change Deployment
automateyournetwork/netclaw
Deploys Cisco ACI policy changes only behind an approved ServiceNow Change Request, capturing pre and post-change fault baselines and rolling back automatically on a fault delta.
Cisco ACI Fabric Health Audit
automateyournetwork/netclaw
Runs a phased health audit of a Cisco ACI fabric through MCP tools: node status, links, tenant and policy review, faults and endpoint learning.
Anta Validation
automateyournetwork/netclaw
Validate Arista EOS network state against ANTA's pre-built 208-test catalogue, with structured pass/fail verdicts.
Arista Cvp
automateyournetwork/netclaw
Arista CloudVision Portal (CVP) automation via REST API — device inventory, events, connectivity monitoring, tag management (4 tools).
AWS Cloud Monitoring
automateyournetwork/netclaw
AWS CloudWatch monitoring — metrics, alarms, log queries, VPC flow log analysis, network performance.
Batfish Config Analysis
automateyournetwork/netclaw
Batfish network configuration analysis -- pre-deployment validation, reachability testing, ACL/firewall tracing, differential analysis, compliance checking.
Related
Categories
Questions about EVE-NG Lab Topology Design
What does EVE-NG Lab Topology Design do?
Entry point for designing EVE-NG network labs: classifies the request, gathers missing requirements, proposes options and validates the resulting topology. This skill is the starting point for EVE-NG topology work. It classifies the request as campus, branch or WAN, ISP or service provider, data center or hybrid, reads a discovery reference to ask only for missing requirements, summarizes requirements and assumptions, presents options with trade-offs and recommends one design.
When should I use EVE-NG Lab Topology Design?
EVE-NG Lab Topology Design fits situations like: planning a new EVE-NG lab before building it; reviewing an EVE-NG topology design or lab architecture; producing a build plan for a lab with structured requirements and validation.
How do I install EVE-NG Lab Topology Design in Claude Code?
Run `npx skills add automateyournetwork/netclaw --skill eve-lab-topology-design -a claude-code`. Or copy the skill folder (workspace/skills/eve-lab-topology-design in automateyournetwork/netclaw) into .claude/skills/eve-lab-topology-design in your project. Claude Code loads it when a task matches its description.
How do I install EVE-NG Lab Topology Design in Codex?
Run `npx skills add automateyournetwork/netclaw --skill eve-lab-topology-design -a codex`. Or copy the skill folder (workspace/skills/eve-lab-topology-design in automateyournetwork/netclaw) into .agents/skills/eve-lab-topology-design in your project. Codex loads it when a task matches its description.
Can I use EVE-NG Lab Topology Design in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add automateyournetwork/netclaw --skill eve-lab-topology-design -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/eve-lab-topology-design, .gemini/skills/eve-lab-topology-design, .github/skills/eve-lab-topology-design and .opencode/skills/eve-lab-topology-design in your project.
What does EVE-NG Lab Topology Design need to run?
Going by SKILL.md and its folder, EVE-NG Lab Topology Design needs Python for the scripts in its folder. Our summary lists: An EVE-NG environment for building labs; Python 3 to run the .unl topology validator.
Does EVE-NG Lab Topology Design access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is EVE-NG Lab Topology Design safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does EVE-NG Lab Topology Design use?
EVE-NG Lab Topology Design is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does EVE-NG Lab Topology Design use?
About 612 tokens (SKILL.md is roughly 2.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.9k tokens, read only when the agent opens those files.
What are the alternatives to EVE-NG Lab Topology Design?
Skills that share tags, products or a category with EVE-NG Lab Topology Design: Architecture (nteract/nteract, 180 stars), NIC Task Planning (nginx/kubernetes-ingress, 5.1k stars), Rfc Writer (mohitagw15856/pm-claude-skills, 1.4k stars) and N Agentic Harnesses Codex (NateBJones-Projects/OB1, 4.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains EVE-NG Lab Topology Design?
automateyournetwork (a GitHub user) maintains it in automateyournetwork/netclaw, which has 677 GitHub stars. The repository holds 120 skills in this directory. The repository was last updated on October 11, 2026.
Source: automateyournetwork/netclaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.