EVE-NG Lab Management
Use this skill for lab inventory, lifecycle, health, and image checks.
Workflow
- Use
eve_statusandeve_authto verify platform state when needed. - Use
eve_list_labs/eve_get_labfor lab discovery and metadata. - Before creating, starting, or deleting labs, apply
{baseDir}/references/operational-guardrails.md. - For image questions, follow
{baseDir}/references/image-and-pagination.md. - For import/export work, use native lab ZIP workflows first.
Available tools
eve_statuseve_autheve_list_imageseve_list_labseve_get_labeve_create_labeve_delete_labeve_export_labeve_import_lab
Notes
- Lab paths should include the folder prefix, for example
/Labs/BGP.unl. .unlis added automatically if omitted.- ZIP lab export includes the lab package, not node images.
Failure Behavior
- If a tool call fails with an authentication or connection error, check that
EVE_PASSWORD,EVE_URL,EVE_USERare 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.


