RepoAI
Browse MCPs

Whizard Events

94TrustedInstructions only

Management and API access for WizTelemetry Events on the KubeSphere platform.

What it does

Whizard Events enables your assistant to manage the lifecycle of Kubernetes event monitoring components within KubeSphere. It streamlines the deployment process by guiding the version selection, target cluster validation, and resource configuration required to keep the extension running correctly.

Beyond deployment, this skill interprets the internal architecture of event collection and processing. It assists in formatting configuration files and setting up query access for your stored event data, ensuring that your telemetry pipeline remains consistent with the underlying platform requirements.

When it earns its place

Reach for it when…

Apply this skill when you need to deploy or update the WizTelemetry Events extension across your KubeSphere clusters. It is intended for setting up the necessary configuration structures for OpenSearch integration and defining index life-cycle policies.

Look elsewhere when…

Do not use this skill to troubleshoot general OpenSearch database connectivity issues or to manage the underlying vector data pipeline, as those are external dependencies that require separate configuration management. It is not suitable for ad-hoc SQL-style queries on your event logs.

What to say to use it

You never invoke a skill directly — the assistant picks it up when your request matches what it covers. These are the kinds of things that do that.

  • install the latest version of WizTelemetry Events
  • help me configure an index policy for my cluster events
  • how do I deploy the event collection extension to my clusters
  • create an install plan for Whizard Events

Install it

Install for all your projects

Copy the skill directory into your personal skills folder. Claude picks it up on its own the next time your request matches what it does — there is nothing to enable.

bash
git clone --depth 1 --branch master https://github.com/kubesphere/kubesphere.git /tmp/kubesphere
mkdir -p ~/.claude/skills
cp -r /tmp/kubesphere/skills/whizard-events ~/.claude/skills/whizard-events

Install for one project only

Put it in the project's own skills folder instead, so it can be committed and shared with everyone working on that repository.

bash
cp -r /tmp/kubesphere/skills/whizard-events .claude/skills/whizard-events

If a skill of the same name exists in both places, the personal one wins.

Installing on Claude.ai or through the API instead? The full guide covers every surface.

Pair it with an MCP server

Whizard Events changes how the work is done. These servers change what Claude can reach while doing it.

How skills and MCP servers differ →