Stage Compose
Orkas-AI/Orkas-VideoStudio
Authoring knowledge for Orkas/OVS HTML video compositions -- write an index.html, drive animation from a paused timeline, declare canvas + duration, then run the VideoStudio draft gate to render an…
Analyze Open vSwitch data from sosreport. An agent skill from openshift-eng/ai-helpers.
Apache-2.0Auto-check: notes
Install Ovs DB Analysis
$ npx skills add openshift-eng/ai-helpers --skill ovs-db-analysis -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install openshift-eng/ai-helpers ovs-db-analysis --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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/ovs-db-analysis .claude/skills/ovs-db-analysis && rm -rf skills-srcUse ~/.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/
Install the "ovs-db-analysis" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/sosreport/skills/ovs-db-analysis into .claude/skills/ovs-db-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ovs-db-analysis", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/openshift-eng/ai-helpers/tree/main/plugins/sosreport/skills/ovs-db-analysisType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add openshift-eng/ai-helpers --skill ovs-db-analysis -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install openshift-eng/ai-helpers ovs-db-analysis --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/sosreport/skills/ovs-db-analysis .agents/skills/ovs-db-analysis && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ovs-db-analysis" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/sosreport/skills/ovs-db-analysis into .agents/skills/ovs-db-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ovs-db-analysis", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add openshift-eng/ai-helpers --skill ovs-db-analysis -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install openshift-eng/ai-helpers ovs-db-analysis --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/sosreport/skills/ovs-db-analysis .cursor/skills/ovs-db-analysis && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ovs-db-analysis" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/sosreport/skills/ovs-db-analysis into .cursor/skills/ovs-db-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ovs-db-analysis", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/openshift-eng/ai-helpers.git --path plugins/sosreport/skills/ovs-db-analysis--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add openshift-eng/ai-helpers --skill ovs-db-analysis -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install openshift-eng/ai-helpers ovs-db-analysis --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/sosreport/skills/ovs-db-analysis .gemini/skills/ovs-db-analysis && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ovs-db-analysis" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/sosreport/skills/ovs-db-analysis into .gemini/skills/ovs-db-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ovs-db-analysis", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install openshift-eng/ai-helpers ovs-db-analysisInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add openshift-eng/ai-helpers --skill ovs-db-analysis -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/sosreport/skills/ovs-db-analysis .github/skills/ovs-db-analysis && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ovs-db-analysis" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/sosreport/skills/ovs-db-analysis into .github/skills/ovs-db-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ovs-db-analysis", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add openshift-eng/ai-helpers --skill ovs-db-analysis -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install openshift-eng/ai-helpers ovs-db-analysis --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/sosreport/skills/ovs-db-analysis .opencode/skills/ovs-db-analysis && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ovs-db-analysis" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/sosreport/skills/ovs-db-analysis into .opencode/skills/ovs-db-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ovs-db-analysis", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
ovs-db-analysis- GitHub stars
- 120
- Token cost
- ~2.8k tokens
- SKILL.md length
- 739 words
- Files
- 2 (incl. scripts)
- Skills in repo
- 118
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Analyze Open vSwitch data from sosreport. An agent skill from openshift-eng/ai-helpers.
- Works in 7 steps: Locate the Analysis Script → Run the Analysis → Custom Queries (Optional, requires --db) → …
- SKILL.md covers When to Use This Skill, Prerequisites, File Locations in Sosreport and Analysis Script, plus 8 more sections
- Runs Python scripts from its folder; calls python3, dnf and apt
What it does
Ovs DB Analysis is an agent skill from openshift-eng/ai-helpers. Analyze Open vSwitch data from sosreport
Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/analyze_ovs_db.py`).
The repository describes itself as: Developer productivity tools for Claude Code & other AI assistants. The licence is Apache-2.0.
Example prompts
- “/ovs-db-analysis”
Requirements
- Python 3
Workflow steps
7 steps, taken from the step headings in SKILL.md.
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
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python3dnfapt
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
github.com
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
Ovs DB Analysis loads about 2.8k tokens when it runs. Until then it costs about 14 tokens; SKILL.md has 739 words of instructions outside code blocks.
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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteRuns commands with sudoSKILL.md:37
- Fedora/RHEL: `sudo dnf install openvswitch` - NoteRuns commands with sudoSKILL.md:38
- Ubuntu/Debian: `sudo apt install openvswitch-common`
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); the scripts in this folder 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). 739 words, ~2,840 tokens.
Download SKILL.mdSave it as
.claude/skills/ovs-db-analysis/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- ovs-db-analysis
- description
- Analyze Open vSwitch data from sosreport
OVS Database and Flow Analysis
This skill provides detailed analysis of Open vSwitch (OVS) data collected via sosreport. It operates in four modes:
- Default mode: Full analysis - conf.db + all text files (requires ovsdb-tool, falls back to text files if not available)
- Database mode (
--db): Database only - analyze conf.db (requires ovsdb-tool) - Text files mode (
--flows-only): Text files only - no ovsdb-tool needed - Query mode (
--query): Run custom OVSDB JSON queries (requires ovsdb-tool)
When to Use This Skill
Use this skill when:
- Troubleshooting packet drops - Find drop flows being hit
- Analyzing flow performance - View top flows by packet count
- Analyzing OVS configuration from a sosreport
- Troubleshooting bridge, port, or interface issues
- Investigating DPDK vs kernelspace datapath
- Reviewing tunnel configurations (VXLAN, Geneve, GRE)
- Checking port statistics (drops, errors, traffic)
- Mapping Kubernetes pods to OVS interfaces
Prerequisites
Default mode (full analysis):
- ovsdb-tool must be installed (from openvswitch package)
- Falls back to
--flows-onlyif ovsdb-tool not found - Sosreport with
sos_commands/openvswitch/directory andconf.db
Database mode (--db):
- ovsdb-tool must be installed (from openvswitch package)
- Check:
which ovsdb-tool - Fedora/RHEL:
sudo dnf install openvswitch - Ubuntu/Debian:
sudo apt install openvswitch-common
- Check:
- Sosreport with
conf.dbfile
Text files mode (--flows-only):
- No special tools needed - works out of the box!
- Sosreport with
sos_commands/openvswitch/directory
Query mode (--query):
- ovsdb-tool must be installed
- Incompatible with
--flows-only
File Locations in Sosreport
The sosreport collects:
sosreport-hostname-date/
├── etc/openvswitch/conf.db (OVS database - for --db mode)
├── var/lib/openvswitch/conf.db (alternate location)
└── sos_commands/openvswitch/ (default mode uses these)
├── ovs-vsctl_-t_5_show (topology)
├── ovs-vsctl_-t_5_list_bridge (bridge details)
├── ovs-vsctl_-t_5_list_interface (interface details)
├── ovs-vsctl_-t_5_list_Open_vSwitch (system info)
├── ovs-ofctl_dump-flows_<bridge> (OpenFlow entries)
├── ovs-ofctl_dump-ports_<bridge> (Port statistics)
├── ovs-appctl_coverage.show (internal stats)
├── ovs-appctl_upcall.show (datapath health)
├── ovs-appctl_tnl.ports.show_-v (tunnel ports)
└── ...Analysis Script
The analysis script is located at:
<plugin-root>/skills/ovs-db-analysis/scripts/analyze_ovs_db.pyImplementation Steps
Step 1: Locate the Analysis Script
SCRIPT_PATH=$(find ~ -name "analyze_ovs_db.py" -path "*/sosreport/skills/ovs-db-analysis/scripts/*" 2>/dev/null | head -1)
if [ -z "$SCRIPT_PATH" ]; then
echo "ERROR: analyze_ovs_db.py script not found."
exit 1
fiStep 2: Run the Analysis
# Default: Full analysis - conf.db + text files (requires ovsdb-tool)
python3 "$SCRIPT_PATH" /path/to/sosreport-hostname-date/
# Analyze from archive
python3 "$SCRIPT_PATH" /path/to/sosreport-hostname-date.tar.xz
# Database only mode (requires ovsdb-tool)
python3 "$SCRIPT_PATH" /path/to/sosreport/ --db
# Text files only mode (no ovsdb-tool needed)
python3 "$SCRIPT_PATH" /path/to/sosreport/ --flows-onlyStep 3: Custom Queries (Optional, requires --db)
For specific investigations, use raw OVSDB queries:
# Query all bridges
python3 "$SCRIPT_PATH" /path/to/sosreport/ --query '["Open_vSwitch", {"op":"select", "table":"Bridge", "where":[], "columns":["name","datapath_type","fail_mode"]}]'
# Query VXLAN interfaces
python3 "$SCRIPT_PATH" /path/to/sosreport/ --query '["Open_vSwitch", {"op":"select", "table":"Interface", "where":[["type","==","vxlan"]], "columns":["name","options"]}]'
# Query interfaces with errors
python3 "$SCRIPT_PATH" /path/to/sosreport/ --query '["Open_vSwitch", {"op":"select", "table":"Interface", "where":[], "columns":["name","error"]}]'Analysis Output
The default mode analyzes:
| Analysis | Source File | Description |
|---|---|---|
| System Info | ovs-vsctl_-t_5_list_Open_vSwitch | OVS/DPDK version, system type, external IDs |
| Topology | ovs-vsctl_-t_5_show | Bridge overview with ports grouped by type |
| Bridge Details | ovs-vsctl_-t_5_list_bridge | Datapath type, fail mode, CT zones |
| Interfaces | ovs-vsctl_-t_5_list_interface | By type, pod interfaces with mapping |
| OpenFlow | ovs-ofctl_dump-flows_* | Flow counts, drops, top flows |
| Port Stats | ovs-ofctl_dump-ports_* | RX/TX drops and errors |
| Tunnels | ovs-appctl_tnl.ports.show_-v | Configured tunnel ports |
| Datapath Health | ovs-appctl_upcall.show | Flow table usage vs limit |
| OVS Stats | ovs-appctl_coverage.show | Internal counters (netlink, OVSDB, etc.) |
OpenFlow Analysis Features
| Feature | Description |
|---|---|
| Flow Count | Total flows per bridge (total, drop, with hits) |
| Drop Detection | Flows with actions=drop that have packet hits |
| Top Flows | Most active flows sorted by n_packets |
| Table Distribution | Flow counts per OpenFlow table |
| Port Drops | RX/TX drop counters per port |
| Port Errors | RX/TX error counters per port |
| Datapath Health | Flow table usage vs limit (from upcall.show) |
| OVS Stats | Internal statistics (netlink, OpenFlow, OVSDB transactions) |
Show full SKILL.md (332 more words)Show less
OVN Internal Tables (Ignore Drops in These)
When analyzing drop flows in OVN-managed bridges (br-int), ignore drops in table 44 and tables 64-87 as these are internal OVN mechanics, not security policy or real packet drops.
⚠️ Note: OVN and OVS are complex systems and table mappings can change between releases. Always verify drop analysis against the specific OVN version in use. When in doubt, check the OVN source code for your release.
| Table | Name | Purpose |
|---|---|---|
| 44 | CHK_LB_OUTPUT | Loopback prevention - drops packets that would loop back (high volume, normal) |
| 64 | SAVE_INPORT | Save ingress port for later |
| 65 | LOG_TO_PHY | Logical to physical mapping |
| 66 | MAC_BINDING | MAC binding lookups |
| 67 | MAC_LOOKUP | MAC address table lookups |
| 68-69 | CHK_LB_HAIRPIN | Load balancer hairpin checks |
| 70 | CT_SNAT_HAIRPIN | Conntrack SNAT hairpin |
| 71-72 | GET/LOOKUP_FDB | FDB (forwarding DB) lookups |
| 73-74 | CHK_IN_PORT_SEC | Ingress port security |
| 75 | CHK_OUT_PORT_SEC | Egress port security |
| 76-77 | ECMP_NH | ECMP next-hop handling |
| 78 | CHK_LB_AFFINITY | Load balancer affinity |
| 79 | MAC_CACHE_USE | MAC cache miss (high volume, normal) |
| 80 | CT_ZONE_LOOKUP | Conntrack zone lookup |
| 81-83 | CT_ORIG_*_LOAD | Conntrack original tuple loading |
| 84 | FLOOD_REMOTE_CHASSIS | Remote chassis flooding |
| 85 | CT_STATE_SAVE | Conntrack state save |
| 86 | CT_ORIG_PROTO_LOAD | Conntrack protocol loading |
| 87 | GET_REMOTE_FDB | Remote FDB lookup |
Relevant drop tables for troubleshooting:
- Table 9: Ingress ACLs - actual policy drops (look for
reg0=0x8000) - Table 0: Initial classification drops
- Tables < 64: Generally meaningful drops
Common Analysis Scenarios
1. Troubleshooting Packet Drops
# Quick analysis (default mode, no ovsdb-tool)
python3 "$SCRIPT_PATH" /path/to/sosreport/Look for:
- ACTIVE DROP FLOWS section showing flows dropping packets
- PORT STATISTICS showing ports with drops/errors
2. Checking DPDK Configuration
# Default mode shows DPDK info from text files
python3 "$SCRIPT_PATH" /path/to/sosreport/
# Or use database mode for custom queries
python3 "$SCRIPT_PATH" /path/to/sosreport/ --query '["Open_vSwitch", {"op":"select", "table":"Open_vSwitch", "where":[], "columns":["dpdk_initialized","other_config"]}]'3. Investigating Pod Connectivity
The interface analysis shows pod-to-OVS mapping:
- Interfaces with
external_idscontainingiface-id - Interface names ending with
_h(veth host side)
4. Datapath Health Check
The upcall stats show:
DATAPATH FLOW TABLE HEALTH
Current flows: 155 / 200,000 (0.1% used)
Average: 156, Max seen: 215
✓ Flow table healthyIf usage > 90%, flows are being evicted too aggressively.
Output Example
================================================================================
OVS ANALYSIS - sosreport-hostname-2024-01-15
================================================================================
Mode: Text file analysis (no ovsdb-tool required)
================================================================================
OVS SYSTEM INFORMATION
================================================================================
Field Value
------------------------- --------------------------------------------------
OVS Version "3.3.4-62.el9fdp"
DB Version "8.5.0"
System Type rhcos
System Version "4.16"
DPDK Initialized false
Datapath Types [netdev, system]
External IDs:
hostname: master2.example.com
ovn-encap-ip: 10.32.110.5
ovn-encap-type: geneve
================================================================================
OVS TOPOLOGY
================================================================================
System UUID: 7e9a3f70-86fa-4578-a849-4fd807a64a10
Total Bridges: 2
Bridge: br-ex
ports: 3
internal: br-ex
patch: patch-br-ex-to-br-int
system: nm-bond
Bridge: br-int
fail_mode: secure
datapath_type: system
ports: 12
geneve: 9 ports
internal: ovn-k8s-mp0, br-int
patch: patch-br-int-to-br-ex
================================================================================
OPENFLOW ANALYSIS
================================================================================
Bridge: br-int
----------------------------------------------------------------------
Total flows: 2,017
Flows with hits: 318
Drop flows: 150 (9 actively dropping)
⚠️ ACTIVE DROP FLOWS (9):
table=40, priority=0, packets=8,105
table=79, priority=100, packets=1,356
match: ip,reg14=0x2,metadata=0x5,dl_src=00:62:0b:ea:b5:e0
--------------------------------------------------------------------------------
DATAPATH FLOW TABLE HEALTH
--------------------------------------------------------------------------------
Current flows: 155 / 200,000 (0.1% used)
Average: 156, Max seen: 215
✓ Flow table healthyError Handling
| Error | Solution |
|---|---|
ovsdb-tool not found | Install openvswitch package OR use default mode (no --db) |
conf.db not found | Use default mode (analyzes text files instead) |
sos_commands/openvswitch not found | Ensure sosreport has OVS data collected |
See Also
- OVN Database Analysis - For OVN NB/SB databases
- sosreport openvswitch plugin - What sosreport collects
© 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
SKILL.md and 1 other file (scripts) in plugins/sosreport/skills/ovs-db-analysis of openshift-eng/ai-helpers.
- SKILL.md
- scripts/analyze_ovs_db.py
Open the folder on GitHubat commit a627176
Compare with similar skills
Ovs DB 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Ovs DB Analysis this skillopenshift-eng/ai-helpers | 120 | — | ~2.8k | Automated safety check: Notes | Apache-2.0 | |
| Stage ComposeOrkas-AI/Orkas-VideoStudio | 498 | — | ~4.2k | Automated safety check: Pass | MIT | |
| System Config Analysisopenshift-eng/ai-helpers | 120 | — | ~4k | Automated safety check: Pass | Apache-2.0 | |
| Resource Analysisopenshift-eng/ai-helpers | 120 | — | ~3.4k | Automated safety check: Pass | Apache-2.0 | |
| Network Analysisopenshift-eng/ai-helpers | 120 | — | ~3.7k | Automated safety check: Pass | Apache-2.0 | |
| Logs Analysisopenshift-eng/ai-helpers | 120 | — | ~2.6k | Automated safety check: Pass | Apache-2.0 |
Similar skills
System Config Analysis
openshift-eng/ai-helpers
Analyze system configuration data from sosreport archives, extracting OS details, installed packages, systemd service status, SELinux/AppArmor policies, and kernel parameters from the sosreport…
Resource Analysis
openshift-eng/ai-helpers
Analyze system resource usage data from sosreport archives, extracting memory statistics, CPU load averages, disk space utilization, and process information from the sosreport directory structure to…
Network Analysis
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…
Logs Analysis
openshift-eng/ai-helpers
Analyze system and application log data from sosreport archives, extracting error patterns, kernel panics, OOM events, service failures, and application crashes from journald logs and traditional…
More from openshift-eng/ai-helpers
All 118 skills in this repoInvestigate CI Reliability
openshift-eng/ai-helpers
Find and independently validate actionable reliability defects across OpenShift release jobs and presubmits, then export portable issue handoffs.
Address Review PR
openshift-eng/ai-helpers
Fetch and address all PR review comments — categorize by priority, make code changes, post replies, and push.
Categorize Activity Types
openshift-eng/ai-helpers
Categorize Jira issues into Red Hat Sankey Activity Type categories using MCP Jira tools.
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.
Must Gather Analyzer
openshift-eng/ai-helpers
Analyze OpenShift must-gather diagnostic data including cluster operators, pods, nodes, and network components.
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
Questions about Ovs DB Analysis
What does Ovs DB Analysis do?
Analyze Open vSwitch data from sosreport. An agent skill from openshift-eng/ai-helpers. Ovs DB Analysis is an agent skill from openshift-eng/ai-helpers.
How do I install Ovs DB Analysis in Claude Code?
Run `npx skills add openshift-eng/ai-helpers --skill ovs-db-analysis -a claude-code`. Or copy the skill folder (plugins/sosreport/skills/ovs-db-analysis in openshift-eng/ai-helpers) into .claude/skills/ovs-db-analysis in your project. Claude Code loads it when a task matches its description.
How do I install Ovs DB Analysis in Codex?
Run `npx skills add openshift-eng/ai-helpers --skill ovs-db-analysis -a codex`. Or copy the skill folder (plugins/sosreport/skills/ovs-db-analysis in openshift-eng/ai-helpers) into .agents/skills/ovs-db-analysis in your project. Codex loads it when a task matches its description.
Can I use Ovs DB 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 ovs-db-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/ovs-db-analysis, .gemini/skills/ovs-db-analysis, .github/skills/ovs-db-analysis and .opencode/skills/ovs-db-analysis in your project.
What does Ovs DB Analysis need to run?
Going by SKILL.md and its folder, Ovs DB Analysis needs Python for the scripts in its folder and the command-line tools its instructions call (python3, dnf and apt). Our summary lists: Python 3.
Does Ovs DB Analysis access the network?
SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.
Is Ovs DB Analysis safe to install?
Our automated static check of SKILL.md found notes only (runs commands with sudo), nothing it rates as a warning. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Ovs DB Analysis use?
Ovs DB 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 Ovs DB Analysis use?
About 2.8k tokens (SKILL.md is roughly 11k 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 Ovs DB Analysis?
Skills that share tags, products or a category with Ovs DB Analysis: Stage Compose (Orkas-AI/Orkas-VideoStudio, 498 stars), System Config Analysis (openshift-eng/ai-helpers, 120 stars), Resource Analysis (openshift-eng/ai-helpers, 120 stars) and Network Analysis (openshift-eng/ai-helpers, 120 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ovs DB 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.