Event test

agent_factory_schema/equinix/fabric/v1/EventDriven.json

@@ -37,6 +37,12 @@
             "description": "Upgrade FCR Package",
             "uri": "https://raw.githubusercontent.com/equinix/agent-factory/refs/heads/main/agent_factory_schema/equinix/fabric/v1/event_driven/upgrade-fcr-package.md",
             "releaseStatus": "released"
+        },
+        {
+            "name": "equinix.fabric.connection.list.notify",
+            "description": "Email connection-list that over metros have latency alert",
+            "uri": "https://raw.githubusercontent.com/equinix/agent-factory/refs/heads/main/agent_factory_schema/equinix/fabric/v1/event_driven/metro-latency-notify.md",
+            "releaseStatus": "released"
         }
     ]
 }

agent_factory_schema/equinix/fabric/v1/event_driven/metro-latency-notify.md

@@ -0,0 +1,32 @@
+# Collect connection and email
+
+## Overview
+This skill sets up and activate an Equinix agent that automatically email a list of connections that are over the metros where latency spike.
+
+## Prerequisites
+Connections should be in PROVISIONED state 
+
+## Capabilities
+- Detect metro latency alerts
+- Identify the source and destination metros
+- Identify the active connections over the metros
+- Email notification with the connections list
+- Log all actions and decisions
+
+## Follow the action step by step below:
+1. Once the cloud event is received, look at the metro latency alert, from type extract source and destination metro codes
+2. Search for the active connections, using the source metro code as aside and destination metro code as aside
+3. Next, send an email notification to the designated email address, using the outcome of the search connection command as the email body so the recipient is clearly informed of the connections list to follow up.
+
+## Available Tools
+This skill can use the following tools:
+*   **`search_connection`**: Searches for active connections with aside and zside metro codes
+*   **`send_email_notification`**: Sends an email notification given an email address and email body.
+
+## Guidelines
+*   **Prioritize Clarity**: Ensure all parameters for the MCP tools are clearly identified from the user's request before making the tool call.
+*   **Error Handling**: If parameters are invalid or operations fail, log errors and stop the process.
+*   **Token Efficiency**: Only call the tools when all necessary information is present, avoiding unnecessary context loading.
+*   **Required Parameters** User should specify source and destination metro code.
+*   **Required Parameters** User should specify an email address.
+