Kubeshark Installer
kubeshark/kubeshark
Installs and configures Kubeshark on a Kubernetes cluster, choosing between the quick CLI path and a Helm install with custom values.
Installs and configures KubeSphere's WizTelemetry Data Pipeline, built on Vector, which collects and routes logs, audit events, events and notifications to OpenSearch.
Install KubeSphere WizTelemetry Data Pipeline
$ npx skills add kubesphere/kubesphere --skill vector -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install kubesphere/kubesphere vector --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/kubesphere/kubesphere.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/vector .claude/skills/vector && 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 "vector" agent skill from https://github.com/kubesphere/kubesphere/tree/master/skills/vector into .claude/skills/vector/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vector", 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/kubesphere/kubesphere/tree/master/skills/vectorType 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 kubesphere/kubesphere --skill vector -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install kubesphere/kubesphere vector --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kubesphere/kubesphere.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/vector .agents/skills/vector && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vector" agent skill from https://github.com/kubesphere/kubesphere/tree/master/skills/vector into .agents/skills/vector/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vector", 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 kubesphere/kubesphere --skill vector -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install kubesphere/kubesphere vector --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kubesphere/kubesphere.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/vector .cursor/skills/vector && 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 "vector" agent skill from https://github.com/kubesphere/kubesphere/tree/master/skills/vector into .cursor/skills/vector/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vector", 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/kubesphere/kubesphere.git --path skills/vector--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 kubesphere/kubesphere --skill vector -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install kubesphere/kubesphere vector --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kubesphere/kubesphere.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/vector .gemini/skills/vector && 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 "vector" agent skill from https://github.com/kubesphere/kubesphere/tree/master/skills/vector into .gemini/skills/vector/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vector", 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 kubesphere/kubesphere vectorInstalls 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 kubesphere/kubesphere --skill vector -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/kubesphere/kubesphere.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/vector .github/skills/vector && 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 "vector" agent skill from https://github.com/kubesphere/kubesphere/tree/master/skills/vector into .github/skills/vector/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vector", 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 kubesphere/kubesphere --skill vector -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install kubesphere/kubesphere vector --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kubesphere/kubesphere.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/vector .opencode/skills/vector && 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 "vector" agent skill from https://github.com/kubesphere/kubesphere/tree/master/skills/vector into .opencode/skills/vector/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vector", 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
vector- GitHub stars
- 17k
- Token cost
- ~2.6k tokens
- SKILL.md length
- 691 words
- Files
- 1
- Skills in repo
- 32
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Installs and configures KubeSphere's WizTelemetry Data Pipeline, built on Vector, which collects and routes logs, audit events, events and notifications to OpenSearch.
- Works in 3 steps: Get Available Clusters and Confirm Target → Get OpenSearch Endpoint and Credentials… → Get Latest Vector Version (if not…
- Installing the WizTelemetry Data Pipeline before logging or auditing extensions
- SKILL.md covers Overview, When to Use, Installation and Configuration Parameters, plus 3 more sections
- Calls kubectl; needs OPENSEARCH_PASSWORD
What it does
This skill covers the WizTelemetry Data Pipeline extension for KubeSphere, which is based on the Vector tool and collects, transforms and routes observability data. Other WizTelemetry extensions for logging, auditing, events and notifications depend on it. The skill supports setting up collection for those data types, configuring Vector sinks with OpenSearch as the target, and managing the Vector agent components.
The install procedure is a strict sequence. First the agent lists the available clusters and confirms the targets with you unless you named them. Next it has to obtain the OpenSearch endpoint URL and credentials, a username that defaults to admin plus a password, and it does not continue until both are supplied. Then it queries the newest Vector extension version. Only after those steps does it write an InstallPlan, whose name must be exactly `vector`.
When your agent uses it
- Installing the WizTelemetry Data Pipeline before logging or auditing extensions
- Pointing Vector at an OpenSearch endpoint as its sink
- Managing the Vector agent components on selected clusters
Example prompts
- “Install the KubeSphere data pipeline extension on the host and dev clusters.”
- “Configure Vector to send collected logs to our OpenSearch endpoint.”
- “Which extensions depend on the WizTelemetry Data Pipeline?”
Requirements
- A reachable OpenSearch endpoint with its credentials
- kubectl access to a KubeSphere cluster
Workflow steps
3 steps, taken from the step headings in SKILL.md.
- Get Available Clusters and Confirm Target
- Get OpenSearch Endpoint and Credentials (MUST DO)
- Get Latest Vector Version (if not provided by user)
What it can do on your machine
Read from SKILL.md and the folder at commit 04a29b5. 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
Shell commands in SKILL.md call:
kubectl
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):
vector.dev
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
OPENSEARCH_PASSWORD
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
KubeSphere WizTelemetry Data Pipeline loads about 2.6k tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 691 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 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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 691 words (~2,634 tokens).
“WizTelemetry Data Pipeline is an extension based on vector (https://vector.dev/) that provides the ability to collect, transform, and route observability data. It is a core dependency for other WizTelemetry extensions like Logging, Auditing, Events, and Notification.”
- name
- vector
Files
Just SKILL.md in skills/vector of kubesphere/kubesphere.
Open the folder on GitHubat commit 04a29b5
Compare with similar skills
KubeSphere WizTelemetry Data Pipeline 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 |
|---|---|---|---|---|---|---|
| KubeSphere WizTelemetry Data Pipeline this skillkubesphere/kubesphere | 17k | — | ~2.6k | Automated safety check: Pass | Custom licence | |
| Kubeshark Installerkubeshark/kubeshark | 12k | — | ~3.6k | Automated safety check: Notes | Apache-2.0 | |
| Kubeshark KFL2 Filter Referencekubeshark/kubeshark | 12k | — | ~3.6k | Automated safety check: Pass | Apache-2.0 | |
| Kubernetes Network Root Cause Analysiskubeshark/kubeshark | 12k | — | ~5.3k | Automated safety check: Pass | Apache-2.0 | |
| Kubernetes Troubleshooting with Inspektor Gadgetinspektor-gadget/inspektor-gadget | 2.9k | — | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Logfire Infrastructurepydantic/skills | 140 | — | ~1.8k | Automated safety check: Pass | MIT |
Similar skills
Kubeshark KFL2 Filter Reference
kubeshark/kubeshark
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.
Kubernetes Network Root Cause Analysis
kubeshark/kubeshark
Investigates past Kubernetes incidents from Kubeshark traffic snapshots: takes captures, dissects API calls, extracts PCAPs and compares traffic over time.
Kubernetes Troubleshooting with Inspektor Gadget
inspektor-gadget/inspektor-gadget
Traces what the kernel is doing for a misbehaving pod using Inspektor Gadget's eBPF tools, tagged with namespace, pod, container and node, without changing workloads.
- Official
Logfire Infrastructure
pydantic/skills
Monitor hosts, Docker containers, Kubernetes clusters, database/queue/cache servers, and cloud-provider metrics with Pydantic Logfire — no application code required.
- Official
Eks Best Practices
aws-samples/appmod-blueprints
Advisory guidance for Amazon EKS architecture and configuration decisions — compute strategy, networking, security, reliability, cost, autoscaling, observability, multi-tenancy, and upgrade planning.
More from kubesphere/kubesphere
All 32 skills in this repoKubeSphere Multi-Tenant Management
kubesphere/kubesphere
Creates and queries KubeSphere users, workspaces and projects and assigns built-in roles, defaulting to least privilege and never deleting anything.
KubeSphere ServiceMesh Manager
kubesphere/kubesphere
Installs, checks and troubleshoots the KubeSphere ServiceMesh extension (Istio, Kiali, Jaeger), including grayscale release, sidecar injection, topology and tracing issues.
KubeEye Cluster Inspection
kubesphere/kubesphere
Deploys KubeEye on KubeSphere and writes InspectRule and InspectPlan resources to inspect cluster health, then retrieves the inspection reports.
KubeSphere NodeGroup Operations
kubesphere/kubesphere
Queries, creates, updates, binds and troubleshoots NodeGroup resources in the edgewize nodegroup project through a bundled authenticated API script.
WizTelemetry Platform Service
kubesphere/kubesphere
Installs and configures the WizTelemetry Platform Service extension for KubeSphere, the shared API server behind its observability extensions.
Frontend Forge Extension Operations
kubesphere/kubesphere
Runs the lifecycle of FrontendExtension resources in a Kubernetes cluster: create, rebuild, package, publish, unpublish, delete and debug stuck states.
Related
Works with
Categories
Questions about KubeSphere WizTelemetry Data Pipeline
What does KubeSphere WizTelemetry Data Pipeline do?
Installs and configures KubeSphere's WizTelemetry Data Pipeline, built on Vector, which collects and routes logs, audit events, events and notifications to OpenSearch. This skill covers the WizTelemetry Data Pipeline extension for KubeSphere, which is based on the Vector tool and collects, transforms and routes observability data. Other WizTelemetry extensions for logging, auditing, events and notifications depend on it.
When should I use KubeSphere WizTelemetry Data Pipeline?
KubeSphere WizTelemetry Data Pipeline fits situations like: installing the WizTelemetry Data Pipeline before logging or auditing extensions; pointing Vector at an OpenSearch endpoint as its sink; managing the Vector agent components on selected clusters.
How do I install KubeSphere WizTelemetry Data Pipeline in Claude Code?
Run `npx skills add kubesphere/kubesphere --skill vector -a claude-code`. Or copy the skill folder (skills/vector in kubesphere/kubesphere) into .claude/skills/vector in your project. Claude Code loads it when a task matches its description.
How do I install KubeSphere WizTelemetry Data Pipeline in Codex?
Run `npx skills add kubesphere/kubesphere --skill vector -a codex`. Or copy the skill folder (skills/vector in kubesphere/kubesphere) into .agents/skills/vector in your project. Codex loads it when a task matches its description.
Can I use KubeSphere WizTelemetry Data Pipeline 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 kubesphere/kubesphere --skill vector -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vector, .gemini/skills/vector, .github/skills/vector and .opencode/skills/vector in your project.
What does KubeSphere WizTelemetry Data Pipeline need to run?
Going by SKILL.md and its folder, KubeSphere WizTelemetry Data Pipeline needs the command-line tools its instructions call (kubectl) and credentials named OPENSEARCH_PASSWORD. Our summary lists: A reachable OpenSearch endpoint with its credentials; kubectl access to a KubeSphere cluster.
Does KubeSphere WizTelemetry Data Pipeline access the network?
SKILL.md names 1 domain. As links in the text: vector.dev. This is read from the text; nothing was executed.
Is KubeSphere WizTelemetry Data Pipeline 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 KubeSphere WizTelemetry Data Pipeline use?
KubeSphere WizTelemetry Data Pipeline has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does KubeSphere WizTelemetry Data Pipeline use?
About 2.6k 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 KubeSphere WizTelemetry Data Pipeline?
Skills that share tags, products or a category with KubeSphere WizTelemetry Data Pipeline: Kubeshark Installer (kubeshark/kubeshark, 12k stars), Kubeshark KFL2 Filter Reference (kubeshark/kubeshark, 12k stars), Kubernetes Network Root Cause Analysis (kubeshark/kubeshark, 12k stars) and Kubernetes Troubleshooting with Inspektor Gadget (inspektor-gadget/inspektor-gadget, 2.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains KubeSphere WizTelemetry Data Pipeline?
kubesphere (a GitHub organization) maintains it in kubesphere/kubesphere, which has 17,059 GitHub stars. The repository holds 32 skills in this directory. The repository was last updated on July 15, 2026.
Source: kubesphere/kubesphere on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.