RepoAI
Browse MCPs

Whizard Telemetry Ruler

94TrustedInstructions only

Alerting rule management and configuration for KubeSphere observability environments.

What it does

Whizard Telemetry Ruler acts as a bridge between KubeSphere data streams and your alerting infrastructure. By installing this skill, your assistant gains the ability to interpret technical requirements for monitoring cluster events, audit logs, and system metrics into the specific configurations required by the extension. It ensures that monitoring policies are defined correctly within the KubeSphere ecosystem.

This skill is designed for administrators managing observability pipelines who need to ensure that their alert triggers and notification sinks are properly aligned. It streamlines the creation and maintenance of rule groups by translating operational goals into the specific command structures and manifest formats required by the KubeSphere platform.

When it earns its place

Reach for it when…

Use this skill when you need to deploy the ruler component across clusters, establish new alerting criteria for Kubernetes events or audit logs, or verify that notification endpoints are correctly linked to your existing AlertManager proxy.

Look elsewhere when…

Do not use this for general KubeSphere cluster management tasks, such as provisioning node pools or handling storage classes, as this skill focuses strictly on the observability alerting layer. It is also unsuitable for troubleshooting network connectivity between pods unless the issue is directly related to a misconfigured alert notification sink.

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.

  • How do I set up alerting rules for K8s logs in KubeSphere?
  • Update my cluster alerting rules to include new audit events.
  • Help me configure the alert notification sink for my ruler installation.
  • What is the latest version of the ruler extension available for my clusters?

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

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

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

How skills and MCP servers differ →