Use when installing or configuring the WizTelemetry Data Pipeline (vector) extension for KubeSphere, which provides data collection, transformation, and routing for observability data including logs,
Install
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add kubesphere/kubesphere --skill vector -a cursor -y
Use when installing or configuring the WizTelemetry Data Pipeline (vector) extension for KubeSphere, which provides data collection, transformation, and routing for observability data including logs, auditing, events, and notifications
Questions
How do I install vector?
Download skills/vector/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
Where does vector live?
The publisher keeps it at https://github.com/kubesphere/kubesphere.
Which agents can use vector?
Claude, Cursor, and Codex can read a SKILL.md you add from the publisher's repository.
Use when installing or configuring the WizTelemetry Data Pipeline (vector) extension for KubeSphere, which provides data collection, transformation, and routing for observability data including logs, auditing, events, and notifications
name: vector
description: Use when installing or configuring the WizTelemetry Data Pipeline (vector) extension for KubeSphere, which provides data collection, transformation, and routing for observability data including logs, auditing, events, and notifications
WizTelemetry Data Pipeline (Vector)
Overview
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.
When to Use
Installing or configuring the WizTelemetry Data Pipeline extension
Setting up data collection for logs, auditing, events, and notifications
Configuring Vector sinks (OpenSearch)
Managing Vector agent components
Installation
Prerequisites
REQUIRED: Complete all steps in order before generating InstallPlan.
Step 1: Get Available Clusters and Confirm Target
⚠️ CRITICAL: DO NOT proceed until target clusters are determined.
Step 1.1: Get available clusters
kubectl get clusters -o jsonpath='{.items[*].metadata.name}'
Step 1.2: Determine target clusters
If user explicitly specified target clusters in the request → Use those clusters directly, proceed to Step 2
If user did NOT specify target clusters → Ask user to confirm which clusters to deploy to, then proceed to Step 2
Ask user (if not specified):
Available clusters: host, dev
Which clusters do you want to deploy Vector to?
Step 2: Get OpenSearch Endpoint and Credentials (MUST DO)
If user already provided OpenSearch endpoint and credentials in the request → Use those directly, proceed to Step 3
If user did NOT provide → You MUST ask user for OpenSearch endpoint and credentials
Ask user for (if not provided):
OpenSearch endpoint URL (required)
Example: http://<node-ip>:30920 or https://opensearch.example.com:9200
OpenSearch credentials (required)
Username (default: admin)
Password
DO NOT proceed to Step 3 until user provides both endpoint and credentials.
Step 3: Get Latest Vector Version (if not provided by user)
⚠️ DO NOT generate InstallPlan until all placeholders have real values.
Wait for Deployment
After applying InstallPlan, you MUST wait for deployment to complete:
# Wait for Vector pods to be ready (on each cluster)
kubectl wait --for=condition=Ready pods -n kubesphere-logging-system -l app.kubernetes.io/instance=vector --timeout=300s
# Verify deployment status
kubectl get pods -n kubesphere-logging-system -l app.kubernetes.io/instance=vector
# View extension installation status
kubectl get installplan vector
# View extension version
kubectl get extensionversions -l kubesphere.io/extension-ref=vector
Check Pod Status
# View all Vector pods
kubectl get pods -n kubesphere-logging-system -l app.kubernetes.io/name=vector
# View agent pods
kubectl get pods -n kubesphere-logging-system -l app.kubernetes.io/name=vector,app.kubernetes.io/component=agent