Agent skill

Network Analysis

by openshift-eng in openshift-eng/ai-helpers

Analyze network configuration data from sosreport archives, extracting interface configurations, routing tables, active connections, firewall rules (firewalld/iptables), and DNS settings from the…

Apache-2.0Auto-check passedDevOps & Cloud

Install Network Analysis

skills CLI
$ npx skills add openshift-eng/ai-helpers --skill network-analysis -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install openshift-eng/ai-helpers network-analysis --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/sosreport/skills/network-analysis .claude/skills/network-analysis && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
network-analysis
GitHub stars
120
Token cost
~3.7k tokens
SKILL.md length
865 words
Files
1
Skills in repo
118
Repo updated
First seen
Licence
Apache-2.0

At a glance

Analyze network configuration data from sosreport archives, extracting interface configurations, routing tables, active connections, firewall rules (firewalld/iptables), and DNS settings from the…

  • Works in 7 steps: Analyze Network Interfaces → Analyze Routing Configuration → Analyze Network Connectivity → …
  • Tasks that involve Cloud networking
  • SKILL.md covers When to Use This Skill, Prerequisites, Key Network Data Locations in… and Implementation Steps, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Network Analysis is an agent skill from openshift-eng/ai-helpers. Analyze network configuration data from sosreport archives, extracting interface configurations, routing tables, active connections, firewall rules (firewalld/iptables), and DNS settings from the sosreport directory structure to diagnose network connectivity and configuration issues

Its SKILL.md is about 3.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering Cloud networking. The repository describes itself as: Developer productivity tools for Claude Code & other AI assistants. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Cloud networking

Example prompts

  • “/network-analysis”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Analyze Network Interfaces
  2. Analyze Routing Configuration
  3. Analyze Network Connectivity
  4. Analyze Firewall Configuration
  5. Analyze DNS Configuration
  6. Check for Network Errors in Logs
  7. Generate Network Analysis Summary

What it can do on your machine

Read from SKILL.md and the folder at commit a627176. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Network Analysis loads about 3.7k tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 865 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~75
When it runs · the whole SKILL.md, loaded when a task matches
~3.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from openshift-eng/ai-helpers at commit a627176, republished under its Apache-2.0 licence (© openshift-eng). 865 words, ~3,656 tokens.

Download SKILL.mdSave it as .claude/skills/network-analysis/SKILL.md (or your agent's skills folder).
name
network-analysis
description
Analyze network configuration data from sosreport archives, extracting interface configurations, routing tables, active connections, firewall rules (firewalld/iptables), and DNS settings from the sosreport directory structure to diagnose network connectivity and configuration issues

Network Analysis Skill

This skill provides detailed guidance for analyzing network configuration and connectivity from sosreport archives, including interfaces, routing, firewall rules, and DNS configuration.

When to Use This Skill

Use this skill when:

  • Analyzing the /sosreport:analyze command's network analysis phase
  • Investigating network connectivity issues
  • Diagnosing firewall or routing problems
  • Verifying network configuration

Prerequisites

  • Sosreport archive must be extracted to a working directory
  • Path to the sosreport root directory must be known
  • Understanding of Linux networking concepts

Key Network Data Locations in Sosreport

  1. Network Interfaces:

    • sos_commands/networking/ip_-o_addr - IP addresses
    • sos_commands/networking/ip_link - Link status
    • sos_commands/networking/ip_-s_link - Link statistics with errors
    • etc/sysconfig/network-scripts/ - Network configuration files (RHEL)
  2. Routing:

    • sos_commands/networking/ip_route - Routing table
    • sos_commands/networking/ip_-6_route - IPv6 routing table
    • proc/net/route - Kernel routing table
  3. Network Connections:

    • sos_commands/networking/netstat_-neopa - Active connections
    • sos_commands/networking/ss_-tupna - Socket statistics
    • proc/net/tcp - TCP connections
    • proc/net/udp - UDP connections
  4. Firewall:

    • sos_commands/firewalld/ - Firewalld configuration
    • sos_commands/iptables/iptables_-vnxL - iptables rules
    • sos_commands/nftables/ - nftables configuration
  5. DNS and Resolution:

    • etc/resolv.conf - DNS servers
    • etc/hosts - Static hostname mappings
    • etc/nsswitch.conf - Name resolution order
  6. Network Services:

    • sos_commands/networking/networkmanager_info - NetworkManager status
    • systemctl status NetworkManager output

Implementation Steps

Step 1: Analyze Network Interfaces
  1. List all network interfaces:

    bash
    if [ -f sos_commands/networking/ip_-o_addr ]; then
      cat sos_commands/networking/ip_-o_addr
    fi
  2. Check interface states:

    bash
    if [ -f sos_commands/networking/ip_link ]; then
      # Look for interface states (UP/DOWN)
      grep -E "^[0-9]+:" sos_commands/networking/ip_link
    fi
  3. Parse interface information:

    • Interface name (eth0, ens192, etc.)
    • State (UP/DOWN)
    • IP addresses (IPv4 and IPv6)
    • MAC address
    • MTU size
  4. Check for interface errors:

    bash
    if [ -f sos_commands/networking/ip_-s_link ]; then
      # Look for RX/TX errors, drops, overruns
      cat sos_commands/networking/ip_-s_link
    fi
  5. Identify interface issues:

    • Interfaces with no IP address (when expected)
    • Interfaces in DOWN state (when should be UP)
    • High error counts (RX/TX errors, drops)
    • Duplicate IP addresses
    • MTU mismatches
Step 2: Analyze Routing Configuration
  1. Check default route:

    bash
    if [ -f sos_commands/networking/ip_route ]; then
      grep "^default" sos_commands/networking/ip_route || echo "No default route found"
    fi
  2. Review routing table:

    bash
    if [ -f sos_commands/networking/ip_route ]; then
      cat sos_commands/networking/ip_route
    fi
  3. Check IPv6 routing:

    bash
    if [ -f sos_commands/networking/ip_-6_route ]; then
      cat sos_commands/networking/ip_-6_route
    fi
  4. Identify routing issues:

    • Missing default route
    • Multiple default routes (conflicting)
    • Incorrect gateway addresses
    • Route to nowhere (unreachable gateway)
Step 3: Analyze Network Connectivity
  1. Check active connections:

    bash
    if [ -f sos_commands/networking/netstat_-neopa ]; then
      cat sos_commands/networking/netstat_-neopa
    elif [ -f sos_commands/networking/ss_-tupna ]; then
      cat sos_commands/networking/ss_-tupna
    fi
  2. Count connections by state:

    bash
    # Count TCP connection states
    if [ -f sos_commands/networking/netstat_-neopa ]; then
      grep "^tcp" sos_commands/networking/netstat_-neopa | awk '{print $6}' | sort | uniq -c
    fi
  3. Find listening services:

    bash
    # Show what's listening on which ports
    if [ -f sos_commands/networking/netstat_-neopa ]; then
      grep "LISTEN" sos_commands/networking/netstat_-neopa
    fi
  4. Check for connection issues:

    • Excessive TIME_WAIT connections
    • Many connections in SYN_SENT (connection attempts failing)
    • High number of CLOSE_WAIT (application not closing)
    • Port conflicts (multiple services on same port)
Step 4: Analyze Firewall Configuration
  1. Check if firewalld is active:

    bash
    if [ -d sos_commands/firewalld ]; then
      # Firewalld is present
      if [ -f sos_commands/firewalld/firewall-cmd_--list-all-zones ]; then
        cat sos_commands/firewalld/firewall-cmd_--list-all-zones
      fi
    fi
  2. Review iptables rules:

    bash
    if [ -f sos_commands/iptables/iptables_-vnxL ]; then
      cat sos_commands/iptables/iptables_-vnxL
    fi
  3. Check firewall zones and rules:

    • Active zones
    • Allowed services
    • Allowed ports
    • Rich rules
    • Drop/reject policies
  4. Identify firewall issues:

    • Required ports blocked
    • Overly permissive rules (any any accept)
    • Conflicting rules
    • Missing rules for services
Step 5: Analyze DNS Configuration
  1. Check DNS servers:

    bash
    if [ -f etc/resolv.conf ]; then
      cat etc/resolv.conf
    fi
  2. Review /etc/hosts:

    bash
    if [ -f etc/hosts ]; then
      # Show non-comment, non-empty lines
      grep -v "^#\|^$" etc/hosts
    fi
  3. Check hostname resolution:

    bash
    # Check hostname
    if [ -f hostname ]; then
      cat hostname
    fi
    
    # Check FQDN
    if [ -f etc/hostname ]; then
      cat etc/hostname
    fi
  4. Verify nsswitch configuration:

    bash
    if [ -f etc/nsswitch.conf ]; then
      grep "^hosts:" etc/nsswitch.conf
    fi
  5. Identify DNS issues:

    • No DNS servers configured
    • Unreachable DNS servers (check connectivity in logs)
    • Incorrect search domains
    • Hostname resolution failures in logs
Step 6: Check for Network Errors in Logs
  1. Look for network-related errors:

    bash
    # Connection refused errors
    grep -i "connection refused" sos_commands/logs/journalctl_--no-pager 2>/dev/null | head -20
    
    # Timeout errors
    grep -i "timeout\|timed out" sos_commands/logs/journalctl_--no-pager 2>/dev/null | head -20
    
    # Network unreachable
    grep -i "network.*unreachable\|no route to host" sos_commands/logs/journalctl_--no-pager 2>/dev/null | head -20
    
    # DNS resolution failures
    grep -i "could not resolve\|dns.*fail\|name resolution" sos_commands/logs/journalctl_--no-pager 2>/dev/null | head -20
  2. Check for link state changes:

    bash
    grep -i "link.*up\|link.*down\|carrier.*lost" sos_commands/logs/journalctl_--no-pager 2>/dev/null | head -20
  3. Look for network device errors:

    bash
    grep -i "network.*error\|eth[0-9].*error\|transmit.*error" var/log/dmesg 2>/dev/null
Show full SKILL.md (427 more words)Show less
Step 7: Generate Network Analysis Summary

Create a structured summary with the following sections:

  1. Interface Summary:

    • List of all interfaces with status
    • IP addresses assigned
    • Interface errors/drops
    • Link speeds and duplex settings
  2. Routing Summary:

    • Default gateway
    • Number of routes
    • Any routing anomalies
  3. Connectivity Summary:

    • Active connection count by state
    • Listening services and ports
    • Connection issues detected
  4. Firewall Summary:

    • Firewall type (firewalld/iptables/nftables)
    • Active zones (if firewalld)
    • Key allowed services/ports
    • Potential blocking rules
  5. DNS Summary:

    • DNS servers configured
    • Search domains
    • Hostname configuration
    • DNS resolution issues
  6. Network Issues:

    • Critical network problems
    • Warnings and recommendations
    • Evidence from logs

Error Handling

  1. Missing network files:

    • Different sosreport versions may have different file names
    • Fall back to alternative files (netstat vs ss)
    • Document missing data in summary
  2. Multiple network configurations:

    • System may use NetworkManager, systemd-networkd, or traditional ifcfg
    • Identify which is in use and analyze accordingly
  3. IPv6 presence:

    • Check if IPv6 is enabled
    • Analyze IPv6 configuration if present
    • Note if IPv6 is disabled when expected

Output Format

The network analysis should produce:

bash
NETWORK CONFIGURATION SUMMARY
==============================

NETWORK INTERFACES
------------------
Interface: {name}
  State: {UP|DOWN}
  IP Addresses: {ipv4}, {ipv6}
  MAC: {mac_address}
  MTU: {mtu}
  RX Errors: {rx_errors} packets, {rx_dropped} dropped
  TX Errors: {tx_errors} packets, {tx_dropped} dropped
  Status: {OK|WARNING|CRITICAL}

ROUTING
-------
Default Gateway: {gateway_ip} via {interface}
Total Routes: {count}

Key Routes:
  {destination} via {gateway} dev {interface}

Status: {OK|WARNING|CRITICAL}
Issues:
  - {routing_issue_description}

CONNECTIVITY
------------
Total Active Connections: {count}

Connections by State:
  ESTABLISHED: {count}
  TIME_WAIT: {count}
  CLOSE_WAIT: {count}
  SYN_SENT: {count}

Listening Services:
  {port}/{protocol} - {service_name} (PID {pid})

Status: {OK|WARNING|CRITICAL}
Issues:
  - {connectivity_issue_description}

FIREWALL
--------
Type: {firewalld|iptables|nftables|none}
Default Zone: {zone_name} (if firewalld)

Allowed Services: {service1}, {service2}, ...
Allowed Ports: {port1/protocol}, {port2/protocol}, ...

Active Rules Count: {count}

Status: {OK|WARNING|CRITICAL}
Potential Issues:
  - {firewall_issue_description}

DNS CONFIGURATION
-----------------
DNS Servers: {dns1}, {dns2}, {dns3}
Search Domains: {domain1}, {domain2}
Hostname: {hostname}
FQDN: {fqdn}

Status: {OK|WARNING|CRITICAL}
Issues:
  - {dns_issue_description}

NETWORK ERRORS FROM LOGS
------------------------
Connection Refused: {count} occurrences
Timeouts: {count} occurrences
DNS Failures: {count} occurrences
Link State Changes: {count} occurrences

Recent Network Errors:
  {timestamp}: {error_message}

CRITICAL NETWORK ISSUES
-----------------------
{severity}: {issue_description}
  Evidence: {file_path_or_log_excerpt}
  Impact: {impact_description}
  Recommendation: {remediation_action}

RECOMMENDATIONS
---------------
1. {actionable_recommendation}
2. {actionable_recommendation}

DATA SOURCES
------------
- Interfaces: {sosreport_path}/sos_commands/networking/ip_-o_addr
- Routes: {sosreport_path}/sos_commands/networking/ip_route
- Connections: {sosreport_path}/sos_commands/networking/netstat_-neopa
- Firewall: {sosreport_path}/sos_commands/firewalld/
- DNS: {sosreport_path}/etc/resolv.conf

Examples

Example 1: Interface Analysis
bash
# Check interface IP addresses
$ cat sos_commands/networking/ip_-o_addr
1: lo    inet 127.0.0.1/8 scope host lo
2: eth0  inet 192.168.1.100/24 brd 192.168.1.255 scope global eth0
2: eth0  inet6 fe80::a00:27ff:fe4e:66a1/64 scope link

# Check for errors
$ cat sos_commands/networking/ip_-s_link | grep -A 4 "eth0"
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500
    RX: bytes  packets  errors  dropped overrun mcast
    15234567   98234    0       0       0       123
    TX: bytes  packets  errors  dropped carrier collsns
    8765432    54321    15      0       0       0

# Interpretation: eth0 has 15 TX errors - investigate cable/switch
Example 2: Firewall Rule Analysis
bash
# Check firewalld active zone
$ grep -A 20 "public" sos_commands/firewalld/firewall-cmd_--list-all-zones
public (active)
  target: default
  services: ssh dhcpv6-client http https
  ports: 8080/tcp 9090/tcp
  ...

# Interpretation: HTTP/HTTPS allowed, custom ports 8080 and 9090 open
Example 3: Connection State Issues
bash
# Count connection states
$ grep "^tcp" sos_commands/networking/netstat_-neopa | awk '{print $6}' | sort | uniq -c
    234 ESTABLISHED
   1523 TIME_WAIT
     12 CLOSE_WAIT
      5 SYN_SENT

# Interpretation:
# - Excessive TIME_WAIT (normal after closing connections)
# - CLOSE_WAIT suggests application not properly closing sockets
# - SYN_SENT indicates outbound connection attempts failing

Tips for Effective Analysis

  1. Check interface consistency: Ensure IP addresses match expected configuration
  2. Verify gateway reachability: Default gateway should be on the same subnet
  3. Look for asymmetric routing: Packets in/out may take different paths
  4. Check MTU settings: MTU mismatches can cause packet fragmentation issues
  5. Correlate with logs: Network errors in logs often explain configuration issues
  6. Consider network topology: Understand expected network layout
  7. Check both IPv4 and IPv6: Be sure to check IPv6 if it's in use

Common Network Patterns and Issues

  1. No default route: "Network unreachable" errors, can't reach internet
  2. Interface down: "Network is down" errors, no connectivity
  3. Duplicate IP: ARP conflicts, intermittent connectivity
  4. Firewall blocking: "Connection refused/timeout" for specific ports
  5. DNS failure: Can't resolve hostnames, but IP connectivity works
  6. Port exhaustion: Too many TIME_WAIT connections, can't create new connections
  7. MTU issues: Large packets fail, small packets work (PMTUD failure)

Network Issue Severity Classification

Issue TypeSeverityImpact
No network interfaceCriticalComplete loss of connectivity
No default routeCriticalNo external connectivity
Interface errors >1%WarningPotential packet loss
Excessive TIME_WAITWarningMay indicate performance issue
Missing DNS serverCriticalName resolution failure
Firewall blocking required portHighService unavailable
IPv6 autoconfiguration failureLowIPv6 connectivity issue

See Also

  • Logs Analysis Skill: For detailed network error log analysis
  • System Configuration Analysis Skill: For network service status
  • Resource Analysis Skill: For network I/O statistics

© openshift-eng, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/sosreport/skills/network-analysis of openshift-eng/ai-helpers.

Open the folder on GitHubat commit a627176

Compare with similar skills

Network Analysis next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Network Analysis compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Network Analysis this skillopenshift-eng/ai-helpers120—~3.7kAutomated safety check: PassApache-2.0
Kubeshark KFL2 Filter Referencekubeshark/kubeshark12k—~3.6kAutomated safety check: PassApache-2.0
Nginx To Higress Migrationhigress-group/higress9.5k—~3.9kAutomated safety check: PassApache-2.0
Bfe Rd Workflowbfenetworks/bfe6.3k—~1.3kAutomated safety check: PassApache-2.0
NGINX Ingress Controller Feature Checklistsnginx/kubernetes-ingress5.1k—~1.4kAutomated safety check: PassApache-2.0
NGINX Ingress Policy CRD Guidenginx/kubernetes-ingress5.1k—~2kAutomated safety check: PassApache-2.0

Similar skills

  • Syntax reference for KFL2, the CEL-based display filter language used to search Kubernetes network traffic captured by Kubeshark, loaded before any filter is written.

    12k GitHub stars~3.6k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Nginx To Higress Migration

    higress-group/higress

    Migrate from ingress-nginx to Higress in Kubernetes environments.

    9.5k GitHub stars~3.9k tokensUpdated 3 days ago
    DevOps & CloudAuto-check passed
  • Bfe Rd Workflow

    bfenetworks/bfe

    引导用户在 bfe 代码库中完成一次完整的功能研发流程,包括需求对齐、文档修改、代码实现、集成测试与回归验证. An agent skill from bfenetworks/bfe.

    6.3k GitHub stars~1.3k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Gives step-by-step checklists for adding Ingress annotations, VirtualServer fields and Helm values to the NGINX Kubernetes Ingress Controller, with common gotchas.

    5.1k GitHub stars~1.4k tokensUpdated today
    DevOps & CloudAuto-check passed
  • NGINX Ingress Policy CRD Guide

    nginx/kubernetes-ingress

    Step-by-step checklist for adding a new Policy CRD type to the NGINX Ingress Controller, from the Go types and validation to config generation and templates.

    5.1k GitHub stars~2k tokensUpdated today
    DevOps & CloudAuto-check passed
  • ArvanCloud API Operator

    erfnzdeh/arvancloud-agent-skill

    Drives ArvanCloud's REST APIs for CDN, DNS, cloud servers, object storage and more, with helper scripts for calls, account inventory and certificates.

    135 GitHub stars~3.9k tokensUpdated 10 days ago
    DevOps & CloudAuto-check passed

More from openshift-eng/ai-helpers

All 118 skills in this repo
  • Investigate CI Reliability

    openshift-eng/ai-helpers

    Find and independently validate actionable reliability defects across OpenShift release jobs and presubmits, then export portable issue handoffs.

    120 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed
  • Address Review PR

    openshift-eng/ai-helpers

    Fetch and address all PR review comments — categorize by priority, make code changes, post replies, and push.

    120 GitHub stars~2.9k tokensUpdated yesterday
    Auto-check passed
  • Categorize Activity Types

    openshift-eng/ai-helpers

    Categorize Jira issues into Red Hat Sankey Activity Type categories using MCP Jira tools.

    120 GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed
  • Has Review Work

    openshift-eng/ai-helpers

    Decide whether a GitHub PR has unanswered authorized review comments or new required CI failures worth a follow-up agent.

    120 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed
  • Must Gather Analyzer

    openshift-eng/ai-helpers

    Analyze OpenShift must-gather diagnostic data including cluster operators, pods, nodes, and network components.

    120 GitHub stars~2.3k tokensUpdated yesterday
    Auto-check passed
  • Payload Autodl JSON

    openshift-eng/ai-helpers

    Schema for the autodl JSON data file produced by payload-analysis for database ingestion — you must use this skill whenever generating the autodl JSON file

    120 GitHub stars~2.6k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Network Analysis

What does Network Analysis do?

Analyze network configuration data from sosreport archives, extracting interface configurations, routing tables, active connections, firewall rules (firewalld/iptables), and DNS settings from the…. Network Analysis is an agent skill from openshift-eng/ai-helpers.

When should I use Network Analysis?

Network Analysis fits situations like: tasks that involve Cloud networking.

How do I install Network Analysis in Claude Code?

Run `npx skills add openshift-eng/ai-helpers --skill network-analysis -a claude-code`. Or copy the skill folder (plugins/sosreport/skills/network-analysis in openshift-eng/ai-helpers) into .claude/skills/network-analysis in your project. Claude Code loads it when a task matches its description.

How do I install Network Analysis in Codex?

Run `npx skills add openshift-eng/ai-helpers --skill network-analysis -a codex`. Or copy the skill folder (plugins/sosreport/skills/network-analysis in openshift-eng/ai-helpers) into .agents/skills/network-analysis in your project. Codex loads it when a task matches its description.

Can I use Network Analysis in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add openshift-eng/ai-helpers --skill network-analysis -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/network-analysis, .gemini/skills/network-analysis, .github/skills/network-analysis and .opencode/skills/network-analysis in your project.

What does Network Analysis need to run?

SKILL.md names no scripts, command-line tools or credentials: Network Analysis is instructions for the agent only.

Does Network Analysis access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Network Analysis safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Network Analysis use?

Network Analysis is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Network Analysis use?

About 3.7k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Network Analysis?

Skills that share tags, products or a category with Network Analysis: Kubeshark KFL2 Filter Reference (kubeshark/kubeshark, 12k stars), Nginx To Higress Migration (higress-group/higress, 9.5k stars), Bfe Rd Workflow (bfenetworks/bfe, 6.3k stars) and NGINX Ingress Controller Feature Checklists (nginx/kubernetes-ingress, 5.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Network Analysis?

openshift-eng (a GitHub organization) maintains it in openshift-eng/ai-helpers, which has 120 GitHub stars. The repository holds 118 skills in this directory. The repository was last updated on October 6, 2026.

Source: openshift-eng/ai-helpers on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.