RepoAI
Browse MCPs

Whizard Notification

94TrustedInstructions only

Alert routing and notification channel configuration for KubeSphere environments.

What it does

Whizard Notification manages the flow of alerts, events, and audit logs within a multi-tenant Kubernetes architecture. By installing this skill, your assistant gains the ability to parse complex routing logic and configuration structures associated with the platform's notification system.

It assists in mapping incoming signals to specific notification channels like email, Slack, or various enterprise messaging platforms. The skill focuses on the Custom Resource Definitions that govern silence periods, alert routing, and receiver credentials, ensuring alerts reach the intended recipients based on namespace or other labels.

When it earns its place

Reach for it when…

Apply this skill when setting up new notification channels, troubleshooting missing alerts, or defining complex routing rules for multi-tenant environments. It is specifically designed to help navigate the CRD structure of the notification manager and its associated secret selectors.

Look elsewhere when…

Do not rely on this skill for general Prometheus Alertmanager configuration outside of the KubeSphere-specific implementation. It is also unsuitable for managing external infrastructure logging pipelines that do not integrate directly with the notification manager's defined CRDs.

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 route alerts to Slack based on specific namespace labels?
  • Show me how to configure an email receiver for system notifications
  • Help me create a silence rule for my cluster monitoring
  • Where should I define the credentials for WeChat notification channels?

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

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

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

How skills and MCP servers differ →