AI agent skill · by @automateyournetwork

Eve Lab Topology Validation

Validate EVE-NG topology designs and enforce final delivery structure. Use when reviewing a design, checking build readiness, producing the final design output, building an implementation plan, or running topology QA before implementation.

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 Lab Topology Validation

Use this skill for the **final QA and delivery** phase of topology work.

## Workflow

1. Run the decision gate in `{baseDir}/references/decision-gate.md`.
2. Produce the required output sections from `{baseDir}/references/output-structure.md`.
3. Run the topology checks in `{baseDir}/references/checklists.md`.
4. If the design will be implemented, use the ordered build plan from `{baseDir}/references/build-and-config-rules.md`.

## Guardrails

- Do not approve build work while unresolved gate items remain.
- State PASS, WARN, or FAIL directly.
- Put unresolved items in the final risks/open-questions section; do not silently skip them.

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