eve-ng-config-ops

Manage EVE-NG startup configurations stored inside lab files.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Managing startup configurations inside EVE-NG lab files is tedious and error-prone when done manually, especially when exporting backups, pushing configs before boot, or verifying stored configs across many nodes.

Core Features & Use Cases

  • Native Config Export: Export startup configs for a single node or an entire lab using native EVE-NG export tools instead of console scraping.
  • Startup Config Management: Read, write, or clear stored startup configs on stopped nodes, and control startup-config mode so configs apply at next boot.
  • Bulk Verification: Use config summaries to check existence, mode, and size across nodes before pulling full config text.
  • Use Case: After rebuilding a lab, bulk-check that every node has a stored startup config with startup mode enabled, then push updated configs to stopped nodes before booting the topology.

Quick Start

Ask the agent to export all node startup configs from the current EVE-NG lab and verify startup-config mode is enabled on every node.

Frequently Asked Questions about eve-ng-config-ops

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

FAQPage Schema
How do I export startup configs from an EVE-NG lab?

Use the native EVE-NG export tools: eve_export_node_config for a single node or eve_export_all_node_configs for the whole lab. Console scraping should only be a fallback when the native path fails or console output is explicitly requested.

How do I push a startup config to an EVE-NG node before boot?

Stop the node first, then use eve_set_node_config to write the startup config into the lab file. Also verify startup-config mode is enabled with eve_set_node_startup_mode so the config applies at next boot.

What is the difference between wiping config and wiping a node in EVE-NG?

eve_wipe_node_config clears only the stored startup config on a stopped node, while eve_wipe_node clears both NVRAM and the startup config. Use the config-only wipe when you want to preserve the node's NVRAM state.

How can I check stored configs across many EVE-NG nodes quickly?

Use eve_list_config_summaries first to check existence, startup mode, and size for all nodes. Escalate to eve_get_node_config or eve_get_all_configs only when the full configuration text is actually needed.

What credentials and environment does EVE-NG config management require?

It requires python3 and three environment variables: EVE_URL, EVE_USER, and EVE_PASSWORD for authenticating against the EVE-NG server. Nodes must be stopped before any startup config write or clear operation.