AI agent skill · by @automateyournetwork

Eve Ng Console Ops

Execute live CLI commands on running EVE-NG nodes over telnet console. Use when running show commands, making live config changes, verifying protocol state, testing connectivity, checking console readiness, or interacting with IOS, Junos, VPCS, EOS, or NX-OS nodes.

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 Console Operations

Use this skill for **live console interaction** with running nodes.

## Workflow

1. Discover the node console first.
2. Determine the landed mode before sending commands.
3. Use the OS-specific execution tool.
4. For config changes, verify command results in the returned transcript before claiming success.
5. Read `{baseDir}/references/console-guardrails.md` when boot state, mode handling, or Junos commit behavior matters.

## Available tools

- `eve_discover_node`
- `eve_exec_ios`
- `eve_exec_junos`
- `eve_exec_vpcs`
- `eve_exec_eos`
- `eve_exec_nxos`

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