Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Use when working with WizTelemetry Events extension for KubeSphere, including installation, configuration, and event query API
.claude/skills/kubesphere-whizard-events/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-02 | ✗→✓ | ▲ Improved | 46% | 0% |
| case-03 | ✗→✓ | ▲ Improved | 158% | 0% |
| case-04 | ✗→✓ | ▲ Improved | 12% | 0% |
| case-06 | ✗→✓ | ▲ Improved | 36% | 0% |
| case-07 | ✗→✓ | ▲ Improved | 31% | 0% |
WizTelemetry Events is an extension component in the KubeSphere Observability Platform for Kubernetes event collection, processing, and storage.
| Component | Description | Default Enabled | |-----------|-------------|-----------------| | kube-events-exporter | Kubernetes event collection and export | true |
REQUIRED: Complete all steps in order before generating InstallPlan.
⚠️ CRITICAL: DO NOT proceed until target clusters are determined.
Step 1.1: Get available clusters
bashkubectl get clusters -o jsonpath='{.items[*].metadata.name}'
Step 1.2: Determine target clusters
Ask user (if not specified):
Available clusters: host, dev
Which clusters do you want to deploy WizTelemetry Events to?MUST do this to get the latest version:
bashkubectl get extensionversions -l kubesphere.io/extension-ref=whizard-events -o jsonpath='{range .items[*]}{.spec.version}{"\n"}{end}' | sort -V | tail -1
This outputs the latest version (e.g., 1.4.0). Note this down - you'll use it in the InstallPlan.
⚠️ IMPORTANT: Complete prerequisite steps BEFORE this step.
Based on your selections:
⚠️ CRITICAL: InstallPlan metadata.name MUST be whizard-events. DO NOT use any other name.
⚠️ CRITICAL: config field is YAML format. You MUST:
⚠️ CRITICAL: All placeholders MUST be replaced with actual values. DO NOT leave them as placeholders.
yamlapiVersion: kubesphere.io/v1alpha1 kind: InstallPlan metadata: name: whizard-events spec: extension: name: whizard-events version: <VERSION> # From Step 2 enabled: true upgradeStrategy: Manual clusterScheduling: placement: clusters: - <TARGET_CLUSTERS>
Replace placeholders:
<VERSION>: From Step 2 (e.g., 1.4.0)<TARGET_CLUSTERS>: User-confirmed cluster namesNote: OpenSearch sink configuration (endpoints, auth) is provided by the vector extension. Make sure vector is installed and configured with OpenSearch before installing events.
yamlapiVersion: kubesphere.io/v1alpha1 kind: InstallPlan metadata: name: whizard-events namespace: kubesphere-system spec: extension: name: whizard-events version: <VERSION> # From Step 2 enabled: true upgradeStrategy: Manual config: | kube-events-exporter: sinks: opensearch: enabled: true index: prefix: "{{ .cluster }}-events" timestring: "%Y.%m.%d" ism_policy: enable: true min_index_age: "7d" clusterScheduling: placement: clusters: - <TARGET_CLUSTERS>
| Parameter | Type | Default | Description | |-----------|------|---------|-------------| | kube-events-exporter.sinks.opensearch.enabled | bool | true | Enable OpenSearch sink | | kube-events-exporter.sinks.opensearch.index.prefix | string | "{{ .cluster }}-events" | Index prefix | | kube-events-exporter.sinks.opensearch.index.timestring | string | "%Y.%m.%d" | Index time format |
| Parameter | Type | Default | Description | |-----------|------|---------|-------------| | kube-events-exporter.ism_policy.enable | bool | false | Enable Index State Management policy | | kube-events-exporter.ism_policy.min_index_age | string | "7d" | Minimum index retention period |
bashcurl -X GET "http://whizard-telemetry-apiserver.extension-whizard-telemetry.svc:80/kapis/logging.kubesphere.io/v1alpha2/events?operation=query&sort=desc&size=10&cluster=host" \ -H "X-Remote-User: admin"
Query Parameters:
| Parameter | Type | Default | Description | |-----------|------|---------|-------------| | operation | string | query | Operation type: query/statistics/histogram/export | | workspace_filter | string | | Comma-separated list of workspaces | | workspace_search | string | | Fuzzy match workspace names | | involved_object_namespace_filter | string | | Comma-separated list of namespaces (involvedObject.namespace) | | involved_object_namespace_search | string | | Fuzzy match namespace names | | involved_object_name_filter | string | | Comma-separated list of object names | | involved_object_name_search | string | | Fuzzy match object names | | involved_object_kind_filter | string | | Comma-separated list of kinds | | reason_filter | string | | Comma-separated list of reasons | | reason_search | string | | Fuzzy match reason | | message_search | string | | Fuzzy match message | | type_filter | string | | Event type: Warning/Normal | | start_time | string | | Start time (seconds since epoch) | | end_time | string | | End time (seconds since epoch) | | interval | string | 15m | Time interval for histogram | | sort | string | desc | Sort order: asc/desc | | from | int | 0 | Offset | | size | int | 10 | Number of results | | cluster | string | host | Cluster name |
bashkubectl get installplan whizard-events kubectl get extensionversions -l kubesphere.io/extension-ref=whizard-events
Uninstall from all clusters:
bashkubectl delete installplan whizard-events
Uninstall from specific cluster:
To remove WizTelemetry Events from a specific cluster, update the InstallPlan by removing that cluster from clusterScheduling.placement.clusters:
yamlapiVersion: kubesphere.io/v1alpha1 kind: InstallPlan metadata: name: whizard-events spec: extension: name: whizard-events version: <VERSION> enabled: true upgradeStrategy: Manual clusterScheduling: placement: clusters: - <REMAINING_CLUSTERS> # Remove the cluster you want to uninstall from
| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-01 | fail→fail | 9,090 | 5,381 | -41% | 1 | 1 | 0% | 1,600 | 2,103 | +31% | 0 | 0 | — |
case-02 | fail→pass | 16,154 | 7,468 | -54% | 1 | 1 | 0% | 1,641 | 2,398 | +46% | 0 | 0 | — |
case-03 | fail→pass | 8,033 | 45,372 | +465% | 1 | 1 | 0% | 1,396 | 3,598 | +158% | 0 | 0 | — |
case-04 | fail→pass | 15,294 | 3,272 | -79% | 1 | 1 | 0% | 2,148 | 2,396 | +12% | 0 | 0 | — |
case-05 | pass→pass | 5,093 | 2,406 | -53% | 1 | 1 | 0% | 845 | 2,164 | +156% | 0 | 0 | — |
case-06 | fail→pass | 8,381 | 1,352 | -84% | 1 | 1 | 0% | 1,471 | 1,995 | +36% | 0 | 0 | — |
case-07 | fail→pass | 10,992 | 3,530 | -68% | 1 | 1 | 0% | 1,914 | 2,513 | +31% | 0 | 0 | — |
case-08 | fail→pass | 17,576 | 3,306 | -81% | 1 | 1 | 0% | 1,077 | 2,506 | +133% | 0 | 0 | — |
case-09 | fail→pass | 9,124 | 3,714 | -59% | 1 | 1 | 0% | 1,525 | 2,541 | +67% | 0 | 0 | — |
case-10 | fail→pass | 8,907 | 3,760 | -58% | 1 | 1 | 0% | 1,503 | 2,422 | +61% | 0 | 0 | — |
case-11 | pass→pass | 9,068 | 2,344 | -74% | 1 | 1 | 0% | 1,368 | 2,229 | +63% | 0 | 0 | — |
case-12 | fail→pass | 6,195 | 2,160 | -65% | 1 | 1 | 0% | 988 | 2,167 | +119% | 0 | 0 | — |
case-13 | fail→pass | 21,338 | 1,618 | -92% | 1 | 1 | 0% | 1,962 | 2,076 | +6% | 0 | 0 | — |
case-14 | fail→pass | 6,931 | 4,986 | -28% | 1 | 1 | 0% | 1,177 | 2,693 | +129% | 0 | 0 | — |
case-15 | fail→pass | 8,247 | 3,710 | -55% | 1 | 1 | 0% | 1,508 | 2,387 | +58% | 0 | 0 | — |
case-16 | fail→pass | 12,472 | 3,333 | -73% | 1 | 1 | 0% | 2,128 | 2,450 | +15% | 0 | 0 | — |
case-17 | fail→pass | 5,618 | 2,910 | -48% | 1 | 1 | 0% | 977 | 2,315 | +137% | 0 | 0 | — |
case-18 | fail→pass | 9,221 | 2,465 | -73% | 1 | 1 | 0% | 749 | 2,252 | +201% | 0 | 0 | — |
case-19 | fail→pass | 17,626 | 2,668 | -85% | 1 | 1 | 0% | 1,267 | 2,255 | +78% | 0 | 0 | — |
case-20 | pass→pass | 2,772 | 1,896 | -32% | 1 | 1 | 0% | 466 | 2,102 | +351% | 0 | 0 | — |
case-21 | pass→pass | 13,561 | 8,382 | -38% | 1 | 1 | 0% | 2,683 | 3,369 | +26% | 0 | 0 | — |
case-22 | pass→pass | 14,680 | 7,954 | -46% | 1 | 1 | 0% | 2,235 | 3,353 | +50% | 0 | 0 | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted, and 19 counted toward the lift figure. The other 3 produced results that are not comparable between the two arms, so they are excluded from the headline rather than averaged into it. The headline lift of +73 percentage points is the difference between those two pass rates over the 19 comparable cases.
Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.
Other measured skills in the registry, with their headline benchmark lift.