RepoAI
Browse MCPs

Whizard Telemetry

94TrustedShips scripts

Backend infrastructure management for KubeSphere observability extensions.

What it does

Whizard Telemetry acts as the centralized API layer for KubeSphere observability modules. Installing this adds the ability to automatically generate the required configuration blocks for your cluster when you add logging, auditing, or event tracking components.

This assistant-managed routine streamlines the creation of deployment plans by querying your existing environment to identify which observability extensions are active. It ensures that your configuration for the telemetry APIServer remains synchronized with the specific services you have enabled, avoiding manual errors during installation or upgrades.

When it earns its place

Reach for it when…

Apply this when setting up or modifying the foundational telemetry services within a KubeSphere environment, particularly when you need to generate the configuration manifest for an InstallPlan after adding new observability features.

Look elsewhere when…

Do not use this for general cluster troubleshooting or when working with observability platforms outside the KubeSphere ecosystem. It is also unnecessary if you are performing a manual configuration of individual components without needing the centralized APIServer integration.

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.

  • Generate the configuration for Whizard Telemetry
  • How do I set up the telemetry APIServer for KubeSphere
  • Create an InstallPlan for my observability extensions
  • Prepare the config for Whizard Telemetry installation

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-telemetry ~/.claude/skills/whizard-telemetry

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-telemetry .claude/skills/whizard-telemetry

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 Telemetry changes how the work is done. These servers change what Claude can reach while doing it.

How skills and MCP servers differ →