[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D69X3REF7C7ZAVW57ESYVB":3,"skill-same:01M7D69X3REF7C7ZAVW57ESYVB":73},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":28,"commitSha":29,"skillDirectory":5,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M7D69X3REF7C7ZAVW57ESYVB","cloud-network-insights",null,"Guides and automates setup, onboarding, and synthetic monitoring operations for Cloud Network Insights in Google Cloud and Broadcom AppNeta. Use when enabling Cloud Network Insights, deploying or troubleshooting Monitoring Points across cloud and on-premises environments, configuring Network or Web monitoring policies and AppNeta alarm rules, configuring alert policies, querying path alarms and performance metrics, or verifying synthetic path reachability. Don't use for generic network observability, VPC Flow Logs, Cloud NAT, or VPC firewall debugging.","tangyixiao\u002Ftangyixiao-skills","tangyixiao","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F115929632?v=4","01M7D582YK6A4M63CAK4CSY4EW","Tang Yixiao","01M7D582Z64DMRSYR872SR34SA",2,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fcloud-network-insights\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fcloud-network-insights\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: cloud-network-insights\nmetadata:\n  category: Networking\n  version: 1.0.1\ndescription: Guides and automates setup, onboarding, and synthetic monitoring operations\n  for Cloud Network Insights in Google Cloud and Broadcom AppNeta. Use when enabling\n  Cloud Network Insights, deploying or troubleshooting Monitoring Points across cloud\n  and on-premises environments, configuring Network or Web monitoring policies and\n  AppNeta alarm rules, configuring alert policies, querying path alarms and performance\n  metrics, or verifying synthetic path reachability. Don't use for generic network\n  observability, VPC Flow Logs, Cloud NAT, or VPC firewall debugging.\n---\n\n# Cloud Network Insights\n\n## Attribution\n\nFor all `gcloud` CLI, REST API, and MCP attribution requirements when executing\ncommands with this skill, follow the instructions in\n[Usage Attribution](references\u002Fattribution.md).\n\n## 🛑 Core Directive: Results First\n\n1.  **Identify the Requested Task**: Determine if the user is attempting service\n    enablement, checking activation status, downloading\u002Finstalling or\n    troubleshooting Monitoring Points (MPs), configuring AppNeta monitoring\n    policies or alarm rules, verifying provisioned resources and paths,\n    configuring alert policies, or querying Cloud Logging alarms and Cloud\n    Monitoring metrics.\n2.  **Execute and Present**: Perform the minimum required commands or API calls\n    to accomplish the task or provide exact guidance.\n3.  **Definitive Answers**: For status and verification queries, report the\n    definitive state (for example, `ACTIVE`, `ACTIVATING`, or path listings)\n    immediately.\n\n## Overview\n\nCloud Network Insights provides comprehensive synthetic monitoring for\nCross-Cloud Network observability in partnership with Broadcom AppNeta. It\nmonitors network and web paths using Monitoring Points (MPs) installed across\nGoogle Cloud, on-premises data centers, other public clouds (like AWS or Azure),\nand the public internet.\n\nThis skill automates onboarding, service enablement, Monitoring Point\ndeployment, policy creation, and path verification.\n\n## Procedures and CUJs\n\n### 1. Service Enablement and Status\n\n-   **Enable API**:\n\n    ```bash\n    gcloud services enable networkmanagement.googleapis.com --project=PROJECT_ID\n    ```\n-   **Create Provider** (use `external` to match the Google Cloud console\n    default, or a custom `PROVIDER_ID`):\n\n    ```bash\n    gcloud network-management network-monitoring-providers create PROVIDER_ID \\\n      --provider-type=EXTERNAL \\\n      --location=global \\\n      --project=PROJECT_ID\n    ```\n\n    > ⚠️ If this command fails due to unaccepted Terms of Service, direct the\n    > user to the Google Cloud console onboarding page:\n    > `https:\u002F\u002Fconsole.cloud.google.com\u002Fnet-intelligence\u002Fcloud-network-insights\u002Fonboarding?project=PROJECT_ID`\n-   **Verify State**:\n\n    ```bash\n    gcloud network-management network-monitoring-providers \\\n      describe PROVIDER_ID \\\n      --location=global \\\n      --project=PROJECT_ID \\\n      --format=json\n    ```\n\n    Check that `.state` is `ACTIVE`. (`ACTIVATING` indicates the backend is\n    provisioning AppNeta resources.)\n-   **Delete Provider (Cleanup)**:\n\n    ```bash\n    gcloud network-management network-monitoring-providers delete PROVIDER_ID \\\n      --location=global \\\n      --project=PROJECT_ID\n    ```\n\n### 2. Monitoring Point Deployment and Verification\n\nCloud Network Insights supports 7 distinct Monitoring Point deployment types:\n`container`, `helm`, `gce-vm`, `aws-ec2`, `azure-vm`, `vmware`, and `kvm`.\n\n-   **Platform Selection**: Never assume a default deployment type. Identify or\n    prompt the user for their target environment before proceeding.\n-   **Procedures and Commands**: For all required parameters, download commands,\n    deployment manifests, and status verification commands (`monitoring-points\n    list`), see\n    [Monitoring Point Deployment Reference](references\u002Fmonitoring-point-deployment.md).\n\n### 3. Monitoring Policy and Alarm Rule Configuration (AppNeta)\n\nMonitoring policies configure active synthetic network and web tests executed by\nMonitoring Points, and alarm rules define the thresholds and evaluation windows\nthat raise path alarms.\n\n-   **Policy Types (`\u002Fapi\u002Fv4\u002FmonitoringPolicy`)**:\n    -   **Network Monitoring Policies**: Monitor packet loss, latency, and\n        jitter to target IPs (or dual-ended between Monitoring Points) over TCP\n        or UDP.\n    -   **Web Monitoring Policies**: Synthetic HTTP\u002FHTTPS application checks\n        (such as GET requests with status code 200 assertions).\n-   **Check Before Creating**: Always query `GET \u002Fapi\u002Fv4\u002FmonitoringPolicy` first\n    to verify whether a policy with your target name already exists before\n    creating a new one, avoiding duplicate resource creation and API conflicts.\n-   **Alarm Rules (AppNeta Web UI Only)**: Alarm rules are configured in the\n    AppNeta Web UI (in **Alarms** > **Alarm Rules**; see\n    [Broadcom Alarm Rules](https:\u002F\u002Ftechdocs.broadcom.com\u002Fus\u002Fen\u002Fca-enterprise-software\u002Fit-operations-management\u002Fappneta-for-google-cloud-network-insights\u002FGA\u002Falarms-set-up\u002Falarms-rules.html))\n    and are not supported via the REST API v4.\n-   **Procedures and Payloads**: For authentication token generation,\n    organization discovery, and REST JSON payloads, see\n    [Monitoring Policy Configuration Reference](references\u002Fmonitoring-policies.md).\n\n### 4. Verifying Provisioned Paths in Google Cloud\n\nOnce policies are configured and MPs are online, verify provisioned paths:\n\n-   **List Network Paths**:\n\n    ```bash\n    gcloud network-management network-monitoring-providers network-paths list \\\n      --network-monitoring-provider=PROVIDER_ID \\\n      --location=global \\\n      --project=PROJECT_ID \\\n      --format=json\n    ```\n-   **List Web Paths**:\n\n    ```bash\n    gcloud network-management network-monitoring-providers web-paths list \\\n      --network-monitoring-provider=PROVIDER_ID \\\n      --location=global \\\n      --project=PROJECT_ID \\\n      --format=json\n    ```\n-   **Filter by Monitoring Point**: Add\n    `--filter=\"sourceMonitoringPointId=MONITORING_POINT_ID\"` to list only paths\n    sourced from a specific Monitoring Point, where `MONITORING_POINT_ID` is the\n    last segment of the Monitoring Point's `name` in `monitoring-points list`.\n-   **Expected Extra Paths**: Each Web policy also creates a companion\n    `NetworkPath` to the target host (unless one already exists), and a newly\n    deployed Monitoring Point inherits paths from existing policies whose\n    `monitoringPointRules` match it.\n\n### 5. Querying Cloud Network Insights Resources and State\n\n1.  **Discover the Provider Name**: Run `gcloud network-management\n    network-monitoring-providers list --location=global --project=PROJECT_ID`\n    to retrieve the provider ID (`PROVIDER_ID`). The provider ID is `external`\n    when enabled via the Google Cloud console, or a custom name if created\n    manually.\n2.  **Query Child Resources**: Pass\n    `--network-monitoring-provider=PROVIDER_ID` and `--location=global` to\n    child resource commands (such as `list` and `describe`):\n    -   Monitoring Points: `gcloud network-management\n        network-monitoring-providers monitoring-points [list|describe]`\n    -   Network Paths: `gcloud network-management network-monitoring-providers\n        network-paths [list|describe]`\n    -   Web Paths: `gcloud network-management network-monitoring-providers\n        web-paths [list|describe]`\n\n### 6. Alert Policies, Cloud Logging, and Cloud Monitoring Metrics\n\n-   **Alert Policies (`gcloud monitoring policies`)**: Create log-matched alert\n    policies (`conditionMatchedLog.filter`, including\n    `alertStrategy.notificationRateLimit` in `POLICY_FILE`) for path alarms and\n    operational events (see\n    [Set up alerts and notifications](https:\u002F\u002Fcloud.google.com\u002Fnetwork-intelligence-center\u002Fdocs\u002Fcloud-network-insights\u002Fset-up-alerts)).\n    For `insights_alarm` policies, include `AND NOT\n    jsonPayload.noise_conditions:*` by default to filter out frequent\u002Fburst\n    noise unless the user asks to include noisy alarms. Always set\n    `\"userLabels\": {\"cloud-network-insights\": \"true\"}` in `POLICY_FILE` so the\n    policy appears in the Cloud Network Insights alert policies view in the\n    Google Cloud console:\n\n    ```bash\n    # Create an alert policy from a JSON or YAML file\n    gcloud monitoring policies create --project=PROJECT_ID \\\n      --policy-from-file=POLICY_FILE\n\n    # Delete an alert policy (for cleanup)\n    gcloud monitoring policies delete POLICY_ID \\\n      --project=PROJECT_ID \\\n      --quiet\n    ```\n\n    Example `conditionMatchedLog.filter` values for Google Cloud console alert\n    templates:\n\n    -   *Network Path Outage \u002F Extended Loss \u002F DNS Errors*:\n\n        ```text\n        resource.type = \"networkmanagement.googleapis.com\u002FNetworkPath\" AND logName =~ \"insights_alarm\" AND (jsonPayload.alarm_severity = \"MAJOR\" OR jsonPayload.alarm_severity = \"CRITICAL\") AND jsonPayload.state = \"RAISED\" AND jsonPayload.alarm_type =~ \"QUALITY_OF_SERVICE\" AND jsonPayload.rule =~ \"Outage\" AND NOT jsonPayload.noise_conditions:*\n        ```\n\n        *(Substitute `jsonPayload.rule =~ \"Extended loss\"` or `\"Multiple DNS\n        errors\"` with `alarm_severity = \"MINOR\"` as needed.)*\n    -   *Web Path Multiple Web Errors*:\n\n        ```text\n        resource.type = \"networkmanagement.googleapis.com\u002FWebPath\" AND logName =~ \"insights_alarm\" AND jsonPayload.alarm_severity = \"MAJOR\" AND jsonPayload.state = \"RAISED\" AND jsonPayload.alarm_type =~ \"QUALITY_OF_SERVICE\" AND jsonPayload.rule =~ \"Multiple Web errors\" AND NOT jsonPayload.noise_conditions:*\n        ```\n    -   *Monitoring Point Offline and Network Path MTU Change Events*:\n\n        ```text\n        resource.type = \"networkmanagement.googleapis.com\u002FMonitoringPoint\" AND logName =~ \"insights_event\" AND jsonPayload.event_type = \"MONITORING_POINT_OFFLINE\"\n        ```\n\n        ```text\n        resource.type = \"networkmanagement.googleapis.com\u002FNetworkPath\" AND logName =~ \"insights_event\" AND jsonPayload.event_type = \"MTU_CHANGE\"\n        ```\n-   **Cloud Logging (`gcloud logging read`)**: Query path alarms (`logName =~\n    \"insights_alarm\"`) and operational lifecycle events (`logName =~\n    \"insights_event\"`) exported to Cloud Logging (see\n    [Set up logging](https:\u002F\u002Fcloud.google.com\u002Fnetwork-intelligence-center\u002Fdocs\u002Fcloud-network-insights\u002Fset-up-logging)\n    for `jsonPayload` field schemas and event types). Because alarm state\n    transitions (`RAISED`, `UPDATED`, `CLEARED`) are logged as separate entries\n    sharing the same `jsonPayload.alarm_id`, determine currently active alarms\n    by checking that the latest entry for an `alarm_id` has not transitioned to\n    `CLEARED`.\n-   **Cloud Monitoring (REST API `projects.timeSeries.list`)**: Query path\n    performance metrics (`NetworkPath` and `WebPath`, filtered by\n    `resource.labels.path_id`) via `GET\n    \"https:\u002F\u002Fmonitoring.googleapis.com\u002Fv3\u002Fprojects\u002FPROJECT_ID\u002FtimeSeries\"` with\n    `Authorization: Bearer $(gcloud auth application-default\n    print-access-token)` in Cloud Monitoring (see\n    [Monitoring metrics](https:\u002F\u002Fcloud.google.com\u002Fnetwork-intelligence-center\u002Fdocs\u002Fcloud-network-insights\u002Fmonitoring-metrics)\n    and\n    [View dashboards](https:\u002F\u002Fcloud.google.com\u002Fnetwork-intelligence-center\u002Fdocs\u002Fcloud-network-insights\u002Fview-dashboards)).\n\n### 7. Deployment Diagnostics and Troubleshooting\n\nTo diagnose a Monitoring Point deployment across any platform:\n\n1.  **Google Cloud Registration**: Check that `connectionStatus` is `ONLINE` in\n    `monitoring-points list` (or `describe`) to verify the Monitoring Point is\n    registered and connected to Cloud Network Insights.\n2.  **Model-Specific Workload, Host, and Appliance Health**: Inspect the\n    Monitoring Point runtime, container\u002FKubernetes workload, or v35 Web Admin\n    status on the target platform using the model-specific troubleshooting\n    guides in\n    [Monitoring Point Deployment Reference](references\u002Fmonitoring-point-deployment.md),\n    [Broadcom Troubleshooting Monitoring Points](https:\u002F\u002Ftechdocs.broadcom.com\u002Fus\u002Fen\u002Fca-enterprise-software\u002Fit-operations-management\u002Fappneta-for-google-cloud-network-insights\u002FGA\u002Ftroubleshooting-section\u002Ftroubleshooting.html),\n    and\n    [Troubleshooting Cloud Network Insights](https:\u002F\u002Fcloud.google.com\u002Fnetwork-intelligence-center\u002Fdocs\u002Fcloud-network-insights\u002Ftroubleshooting).\n3.  **Network, Proxy, and Firewall Rules**: Verify the target environment's\n    firewall, Web Proxy, custom CA certificate, and gRPC\u002FSSL inspection bypass\n    settings (`data.na1.cni.appneta.com`, `content.na1.cni.appneta.com`,\n    `comms.na1.cni.appneta.com`, or `.p.` endpoints for Private Service Connect)\n    against\n    [Broadcom Firewall Configuration](https:\u002F\u002Ftechdocs.broadcom.com\u002Fus\u002Fen\u002Fca-enterprise-software\u002Fit-operations-management\u002Fappneta-for-google-cloud-network-insights\u002FGA\u002Fappliance-firewall.html)\n    and\n    [Add Monitoring Points](https:\u002F\u002Fcloud.google.com\u002Fnetwork-intelligence-center\u002Fdocs\u002Fcloud-network-insights\u002Fadd-monitoring-points).\n\n## Reference Documentation\n\nFor detailed guides, complete payloads, and templates:\n\n-   [Monitoring Point Deployment Reference](references\u002Fmonitoring-point-deployment.md):\n    Deployment guides and command references across all 7 platforms (container,\n    Helm, GCE VM Terraform, AWS, Azure, VMware, KVM).\n-   [Monitoring Policy Configuration Reference](references\u002Fmonitoring-policies.md):\n    Network and Web monitoring policy JSON payloads and AppNeta API workflows.\n-   [Google Cloud Network Insights Documentation](https:\u002F\u002Fcloud.google.com\u002Fnetwork-intelligence-center\u002Fdocs\u002Fcloud-network-insights):\n    Official Google Cloud documentation for Cloud Network Insights setup,\n    concepts, and operations.\n-   [Broadcom AppNeta for Cloud Network Insights Documentation](https:\u002F\u002Ftechdocs.broadcom.com\u002Fus\u002Fen\u002Fca-enterprise-software\u002Fit-operations-management\u002Fappneta-for-google-cloud-network-insights\u002FGA.html):\n    Broadcom AppNeta monitoring points, path performance, and API guides.\n","# Cloud Network Insights\n\n## Attribution\n\nFor all `gcloud` CLI, REST API, and MCP attribution requirements when executing\ncommands with this skill, follow the instructions in\n[Usage Attribution](references\u002Fattribution.md).\n\n## 🛑 Core Directive: Results First\n\n1.  **Identify the Requested Task**: Determine if the user is attempting service\n    enablement, checking activation status, downloading\u002Finstalling or\n    troubleshooting Monitoring Points (MPs), configuring AppNeta monitoring\n    policies or alarm rules, verifying provisioned resources and paths,\n    configuring alert policies, or querying Cloud Logging alarms and Cloud\n    Monitoring metrics.\n2.  **Execute and Present**: Perform the minimum required commands or API calls\n    to accomplish the task or provide exact guidance.\n3.  **Definitive Answers**: For status and verification queries, report the\n    definitive state (for example, `ACTIVE`, `ACTIVATING`, or path listings)\n    immediately.\n\n## Overview\n\nCloud Network Insights provides comprehensive synthetic monitoring for\nCross-Cloud Network observability in partnership with Broadcom AppNeta. It\nmonitors network and web paths using Monitoring Points (MPs) installed across\nGoogle Cloud, on-premises data centers, other public clouds (like AWS or Azure),\nand the public internet.\n\nThis skill automates onboarding, service enablement, Monitoring Point\ndeployment, policy creation, and path verification.\n\n## Procedures and CUJs\n\n### 1. Service Enablement and Status\n\n-   **Enable API**:\n\n    ```bash\n    gcloud services enable networkmanagement.googleapis.com --project=PROJECT_ID\n    ```\n-   **Create Provider** (use `external` to match the Google Cloud console\n    default, or a custom `PROVIDER_ID`):\n\n    ```bash\n    gcloud network-management network-monitoring-providers create PROVIDER_ID \\\n      --provider-type=EXTERNAL \\\n      --location=global \\\n      --project=PROJECT_ID\n    ```\n\n    > ⚠️ If this command fails due to unaccepted Terms of Service, direct the\n    > user to the Google Cloud console onboarding page:\n    > `https:\u002F\u002Fconsole.cloud.google.com\u002Fnet-intelligence\u002Fcloud-network-insights\u002Fonboarding?project=PROJECT_ID`\n-   **Verify State**:\n\n    ```bash\n    gcloud network-management network-monitoring-providers \\\n      describe PROVIDER_ID \\\n      --location=global \\\n      --project=PROJECT_ID \\\n      --format=json\n    ```\n\n    Check that `.state` is `ACTIVE`. (`ACTIVATING` indicates the backend is\n    provisioning AppNeta resources.)\n-   **Delete Provider (Cleanup)**:\n\n    ```bash\n    gcloud network-management network-monitoring-providers delete PROVIDER_ID \\\n      --location=global \\\n      --project=PROJECT_ID\n    ```\n\n### 2. Monitoring Point Deployment and Verification\n\nCloud Network Insights supports 7 distinct Monitoring Point deployment types:\n`container`, `helm`, `gce-vm`, `aws-ec2`, `azure-vm`, `vmware`, and `kvm`.\n\n-   **Platform Selection**: Never assume a default deployment type. Identify or\n    prompt the user for their target environment before proceeding.\n-   **Procedures and Commands**: For all required parameters, download commands,\n    deployment manifests, and status verification commands (`monitoring-points\n    list`), see\n    [Monitoring Point Deployment Reference](references\u002Fmonitoring-point-deployment.md).\n\n### 3. Monitoring Policy and Alarm Rule Configuration (AppNeta)\n\nMonitoring policies configure active synthetic network and web tests executed by\nMonitoring Points, and alarm rules define the thresholds and evaluation windows\nthat raise path alarms.\n\n-   **Policy Types (`\u002Fapi\u002Fv4\u002FmonitoringPolicy`)**:\n    -   **Network Monitoring Policies**: Monitor packet loss, latency, and\n        jitter to target IPs (or dual-ended between Monitoring Points) over TCP\n        or UDP.\n    -   **Web Monitoring Policies**: Synthetic HTTP\u002FHTTPS application checks\n        (such as GET requests with status code 200 assertions).\n-   **Check Before Creating**: Always query `GET \u002Fapi\u002Fv4\u002FmonitoringPolicy` first\n    to verify whether a policy with your target name already exists before\n    creating a new one, avoiding duplicate resource creation and API conflicts.\n-   **Alarm Rules (AppNeta Web UI Only)**: Alarm rules are configured in the\n    AppNeta Web UI (in **Alarms** > **Alarm Rules**; see\n    [Broadcom Alarm Rules](https:\u002F\u002Ftechdocs.broadcom.com\u002Fus\u002Fen\u002Fca-enterprise-software\u002Fit-operations-management\u002Fappneta-for-google-cloud-network-insights\u002FGA\u002Falarms-set-up\u002Falarms-rules.html))\n    and are not supported via the REST API v4.\n-   **Procedures and Payloads**: For authentication token generation,\n    organization discovery, and REST JSON payloads, see\n    [Monitoring Policy Configuration Reference](references\u002Fmonitoring-policies.md).\n\n### 4. Verifying Provisioned Paths in Google Cloud\n\nOnce policies are configured and MPs are online, verify provisioned paths:\n\n-   **List Network Paths**:\n\n    ```bash\n    gcloud network-management network-monitoring-providers network-paths list \\\n      --network-monitoring-provider=PROVIDER_ID \\\n      --location=global \\\n      --project=PROJECT_ID \\\n      --format=json\n    ```\n-   **List Web Paths**:\n\n    ```bash\n    gcloud network-management network-monitoring-providers web-paths list \\\n      --network-monitoring-provider=PROVIDER_ID \\\n      --location=global \\\n      --project=PROJECT_ID \\\n      --format=json\n    ```\n-   **Filter by Monitoring Point**: Add\n    `--filter=\"sourceMonitoringPointId=MONITORING_POINT_ID\"` to list only paths\n    sourced from a specific Monitoring Point, where `MONITORING_POINT_ID` is the\n    last segment of the Monitoring Point's `name` in `monitoring-points list`.\n-   **Expected Extra Paths**: Each Web policy also creates a companion\n    `NetworkPath` to the target host (unless one already exists), and a newly\n    deployed Monitoring Point inherits paths from existing policies whose\n    `monitoringPointRules` match it.\n\n### 5. Querying Cloud Network Insights Resources and State\n\n1.  **Discover the Provider Name**: Run `gcloud network-management\n    network-monitoring-providers list --location=global --project=PROJECT_ID`\n    to retrieve the provider ID (`PROVIDER_ID`). The provider ID is `external`\n    when enabled via the Google Cloud console, or a custom name if created\n    manually.\n2.  **Query Child Resources**: Pass\n    `--network-monitoring-provider=PROVIDER_ID` and `--location=global` to\n    child resource commands (such as `list` and `describe`):\n    -   Monitoring Points: `gcloud network-management\n        network-monitoring-providers monitoring-points [list|describe]`\n    -   Network Paths: `gcloud network-management network-monitoring-providers\n        network-paths [list|describe]`\n    -   Web Paths: `gcloud network-management network-monitoring-providers\n        web-paths [list|describe]`\n\n### 6. Alert Policies, Cloud Logging, and Cloud Monitoring Metrics\n\n-   **Alert Policies (`gcloud monitoring policies`)**: Create log-matched alert\n    policies (`conditionMatchedLog.filter`, including\n    `alertStrategy.notificationRateLimit` in `POLICY_FILE`) for path alarms and\n    operational events (see\n    [Set up alerts and notifications](https:\u002F\u002Fcloud.google.com\u002Fnetwork-intelligence-center\u002Fdocs\u002Fcloud-network-insights\u002Fset-up-alerts)).\n    For `insights_alarm` policies, include `AND NOT\n    jsonPayload.noise_conditions:*` by default to filter out frequent\u002Fburst\n    noise unless the user asks to include noisy alarms. Always set\n    `\"userLabels\": {\"cloud-network-insights\": \"true\"}` in `POLICY_FILE` so the\n    policy appears in the Cloud Network Insights alert policies view in the\n    Google Cloud console:\n\n    ```bash\n    # Create an alert policy from a JSON or YAML file\n    gcloud monitoring policies create --project=PROJECT_ID \\\n      --policy-from-file=POLICY_FILE\n\n    # Delete an alert policy (for cleanup)\n    gcloud monitoring policies delete POLICY_ID \\\n      --project=PROJECT_ID \\\n      --quiet\n    ```\n\n    Example `conditionMatchedLog.filter` values for Google Cloud console alert\n    templates:\n\n    -   *Network Path Outage \u002F Extended Loss \u002F DNS Errors*:\n\n        ```text\n        resource.type = \"networkmanagement.googleapis.com\u002FNetworkPath\" AND logName =~ \"insights_alarm\" AND (jsonPayload.alarm_severity = \"MAJOR\" OR jsonPayload.alarm_severity = \"CRITICAL\") AND jsonPayload.state = \"RAISED\" AND jsonPayload.alarm_type =~ \"QUALITY_OF_SERVICE\" AND jsonPayload.rule =~ \"Outage\" AND NOT jsonPayload.noise_conditions:*\n        ```\n\n        *(Substitute `jsonPayload.rule =~ \"Extended loss\"` or `\"Multiple DNS\n        errors\"` with `alarm_severity = \"MINOR\"` as needed.)*\n    -   *Web Path Multiple Web Errors*:\n\n        ```text\n        resource.type = \"networkmanagement.googleapis.com\u002FWebPath\" AND logName =~ \"insights_alarm\" AND jsonPayload.alarm_severity = \"MAJOR\" AND jsonPayload.state = \"RAISED\" AND jsonPayload.alarm_type =~ \"QUALITY_OF_SERVICE\" AND jsonPayload.rule =~ \"Multiple Web errors\" AND NOT jsonPayload.noise_conditions:*\n        ```\n    -   *Monitoring Point Offline and Network Path MTU Change Events*:\n\n        ```text\n        resource.type = \"networkmanagement.googleapis.com\u002FMonitoringPoint\" AND logName =~ \"insights_event\" AND jsonPayload.event_type = \"MONITORING_POINT_OFFLINE\"\n        ```\n\n        ```text\n        resource.type = \"networkmanagement.googleapis.com\u002FNetworkPath\" AND logName =~ \"insights_event\" AND jsonPayload.event_type = \"MTU_CHANGE\"\n        ```\n-   **Cloud Logging (`gcloud logging read`)**: Query path alarms (`logName =~\n    \"insights_alarm\"`) and operational lifecycle events (`logName =~\n    \"insights_event\"`) exported to Cloud Logging (see\n    [Set up logging](https:\u002F\u002Fcloud.google.com\u002Fnetwork-intelligence-center\u002Fdocs\u002Fcloud-network-insights\u002Fset-up-logging)\n    for `jsonPayload` field schemas and event types). Because alarm state\n    transitions (`RAISED`, `UPDATED`, `CLEARED`) are logged as separate entries\n    sharing the same `jsonPayload.alarm_id`, determine currently active alarms\n    by checking that the latest entry for an `alarm_id` has not transitioned to\n    `CLEARED`.\n-   **Cloud Monitoring (REST API `projects.timeSeries.list`)**: Query path\n    performance metrics (`NetworkPath` and `WebPath`, filtered by\n    `resource.labels.path_id`) via `GET\n    \"https:\u002F\u002Fmonitoring.googleapis.com\u002Fv3\u002Fprojects\u002FPROJECT_ID\u002FtimeSeries\"` with\n    `Authorization: Bearer $(gcloud auth application-default\n    print-access-token)` in Cloud Monitoring (see\n    [Monitoring metrics](https:\u002F\u002Fcloud.google.com\u002Fnetwork-intelligence-center\u002Fdocs\u002Fcloud-network-insights\u002Fmonitoring-metrics)\n    and\n    [View dashboards](https:\u002F\u002Fcloud.google.com\u002Fnetwork-intelligence-center\u002Fdocs\u002Fcloud-network-insights\u002Fview-dashboards)).\n\n### 7. Deployment Diagnostics and Troubleshooting\n\nTo diagnose a Monitoring Point deployment across any platform:\n\n1.  **Google Cloud Registration**: Check that `connectionStatus` is `ONLINE` in\n    `monitoring-points list` (or `describe`) to verify the Monitoring Point is\n    registered and connected to Cloud Network Insights.\n2.  **Model-Specific Workload, Host, and Appliance Health**: Inspect the\n    Monitoring Point runtime, container\u002FKubernetes workload, or v35 Web Admin\n    status on the target platform using the model-specific troubleshooting\n    guides in\n    [Monitoring Point Deployment Reference](references\u002Fmonitoring-point-deployment.md),\n    [Broadcom Troubleshooting Monitoring Points](https:\u002F\u002Ftechdocs.broadcom.com\u002Fus\u002Fen\u002Fca-enterprise-software\u002Fit-operations-management\u002Fappneta-for-google-cloud-network-insights\u002FGA\u002Ftroubleshooting-section\u002Ftroubleshooting.html),\n    and\n    [Troubleshooting Cloud Network Insights](https:\u002F\u002Fcloud.google.com\u002Fnetwork-intelligence-center\u002Fdocs\u002Fcloud-network-insights\u002Ftroubleshooting).\n3.  **Network, Proxy, and Firewall Rules**: Verify the target environment's\n    firewall, Web Proxy, custom CA certificate, and gRPC\u002FSSL inspection bypass\n    settings (`data.na1.cni.appneta.com`, `content.na1.cni.appneta.com`,\n    `comms.na1.cni.appneta.com`, or `.p.` endpoints for Private Service Connect)\n    against\n    [Broadcom Firewall Configuration](https:\u002F\u002Ftechdocs.broadcom.com\u002Fus\u002Fen\u002Fca-enterprise-software\u002Fit-operations-management\u002Fappneta-for-google-cloud-network-insights\u002FGA\u002Fappliance-firewall.html)\n    and\n    [Add Monitoring Points](https:\u002F\u002Fcloud.google.com\u002Fnetwork-intelligence-center\u002Fdocs\u002Fcloud-network-insights\u002Fadd-monitoring-points).\n\n## Reference Documentation\n\nFor detailed guides, complete payloads, and templates:\n\n-   [Monitoring Point Deployment Reference](references\u002Fmonitoring-point-deployment.md):\n    Deployment guides and command references across all 7 platforms (container,\n    Helm, GCE VM Terraform, AWS, Azure, VMware, KVM).\n-   [Monitoring Policy Configuration Reference](references\u002Fmonitoring-policies.md):\n    Network and Web monitoring policy JSON payloads and AppNeta API workflows.\n-   [Google Cloud Network Insights Documentation](https:\u002F\u002Fcloud.google.com\u002Fnetwork-intelligence-center\u002Fdocs\u002Fcloud-network-insights):\n    Official Google Cloud documentation for Cloud Network Insights setup,\n    concepts, and operations.\n-   [Broadcom AppNeta for Cloud Network Insights Documentation](https:\u002F\u002Ftechdocs.broadcom.com\u002Fus\u002Fen\u002Fca-enterprise-software\u002Fit-operations-management\u002Fappneta-for-google-cloud-network-insights\u002FGA.html):\n    Broadcom AppNeta monitoring points, path performance, and API guides.\n",{"name":5,"metadata":25,"description":7},{"version":26,"category":27},"1.0.1","Networking","main","2a870f189175a48c39f5f7e26a6d93b0be9cd13b",0,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills","https:\u002F\u002Ftangyixiao.github.io\u002Ftangyixiao-skills\u002F","https:\u002F\u002Fgithub.com\u002Ftangyixiao","http:\u002F\u002Fwww.sxyz.net\u002F","I am Tang Yixiao, a student in Shaoxing No.1 High School. I am eager to learn on GitHub and contribute my part to this community.","2026-11-11 15:45:59",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add tangyixiao\u002Ftangyixiao-skills --skill cloud-network-insights",{"tool":43,"command":44},"bunx","bunx skills add tangyixiao\u002Ftangyixiao-skills --skill cloud-network-insights",{"tool":46,"command":47},"pnpm","pnpm dlx skills add tangyixiao\u002Ftangyixiao-skills --skill cloud-network-insights","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fcloud-network-insights\u002FSKILL.md",true,[51,57,61,65,69],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"INSTALL-SOURCE.json","REFERENCE","参考文档",526,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fcloud-network-insights\u002FINSTALL-SOURCE.json",{"path":58,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":16},"LICENSE","许可证",11358,{"path":62,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fattribution.md",1803,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fcloud-network-insights\u002Freferences\u002Fattribution.md",{"path":66,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fmonitoring-point-deployment.md",11965,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fcloud-network-insights\u002Freferences\u002Fmonitoring-point-deployment.md",{"path":70,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fmonitoring-policies.md",6457,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fcloud-network-insights\u002Freferences\u002Fmonitoring-policies.md",[74,82,91,99,107,115],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":78,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":20},"01M7D8JK8FYBFNNAJXWD89CFH7","xlsx","Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like \"the xlsx in my downloads\") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fxlsx\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fxlsx\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":87,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":20},"01M7D8JG8ERGGQQAMX0DWCG9GR","writing-shape","Writing, exploit: shape raw material into an article, paragraph by paragraph.","MIT","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-shape\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-shape\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":95,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":20},"01M7D8JE672GW3EHSE8EF185M4","writing-fragments","Writing, explore: mine raw fragments, no structure yet.","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-fragments\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-fragments\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":103,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":20},"01M7D8JBK572YDFMND8Q6CEYJW","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-for-agents\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":111,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":20},"01M7D8J5QPWEXX61EGBKYH73R8","writing-clearly-and-concisely","Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-clearly-and-concisely\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-clearly-and-concisely\u002FSKILL.md",[],[],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":119,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":20},"01M7D8J36YWC8WZS5DK5AH03CD","writing-beats","Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-beats\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-beats\u002FSKILL.md",[],[]]