AI agent skill · by @automateyournetwork

Eve Ng Config Ops

Manage EVE-NG startup configurations stored in lab files. Use when exporting configs natively into the lab, reading embedded startup configs, pushing startup config before boot, clearing config without full NVRAM wipe, or bulk-checking stored configs after lab changes.

Archived 2026-10-23 · Source updated 2026-10-11 · License: Apache-2.0. Check the original repository for the latest version.

SKILL.md instructions

# EVE-NG Config Operations

Use this skill for **startup-config management inside lab files**.

## Workflow

1. Prefer native EVE export tools first for export/backup requests.
2. Read `{baseDir}/references/config-guardrails.md` before export, push, or wipe work.
3. Use summaries first; read full config text only when needed.
4. Stop nodes before writing or clearing startup config.

## Available tools

- `eve_get_node_config`
- `eve_export_node_config`
- `eve_set_node_config`
- `eve_set_node_startup_mode`
- `eve_export_all_node_configs`
- `eve_list_config_summaries`
- `eve_get_all_configs`
- `eve_wipe_node_config`

## Failure Behavior

- If a tool call fails with an authentication or connection error, check that `EVE_PASSWORD`, `EVE_URL`, `EVE_USER` are set and valid before assuming a data or device problem.
- 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.